kevinveenbirkenbachandClaude Opus 4.8
43d23ef696
Move the operator cheatsheet's copy-paste prompts into per-workflow i8- skills that each route to their authoritative procedure doc, and reduce the cheatsheet to a table index plus a usage paragraph, enforced by a new lint. Add skills for develop, test, quality, refactor, the debug and requirement flows, and commit / pull-request / push-trigger-pull; rename the iteration skills to i8-iterate-* and rename the index to i8-help. Wire the active-listening, dialectic, and robot skills into the flows for clarification, uncertain root causes, and autonomous execution. Drop the Infinito-specific agent aliases (alias.md, INFINITO_ALIAS_MD, the make alias agent section, and the two alias tests); terminal aliases stay. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
962 B
name, description
| name | description |
|---|---|
| i8-requirement-create | Write a new requirement file. Infinito.Nexus specific. |
Follow the instructions from AGENTS.md, then create a new requirement for the given topic by following the
procedure in docs/contributing/requirements.md (relative to the Infinito.Nexus repository root)
exactly. That document is the source of truth; this skill only routes you
there. Begin by clarifying every open requirement with the active-listening skill (escalating any root-cause or design question you are not ~99% sure of to the dialectic skill), then work under the robot skill. Before every redeploy you MUST run make compose-exec and make compose-inner-run against the live stack and fully fix and inspect every failure in the container. A new deploy iteration MUST NOT start until every error is resolved and the fix has been empirically verified in-container. The iteration is finished only when every role is green end to end.