Menu
Inspect workflow artifacts and recommend the single best next skill. Use when unsure what to run next.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
| name | 06-next |
| description | Inspect workflow artifacts and recommend the single best next skill. Use when unsure what to run next. |
Use this skill when the user wants to know what to run next in the Compound Engineering workflow, or wants a full status report of the current project state.
workflow_state tool to scan repo artifacts before making a recommendation.session_history tool to check recent executions and avoid already-completed steps.When the user asks "what should I do next?", "continue", or runs /skill:06-next:
workflow_state with the repo rootworkflow_state.context first — apply context-first priority chain from references/recommendation-logic.md (health → blocker → recommendNewSession → nextStage → mismatch → fallback)When the user asks "show status", "what's the current state", or uses --verbose:
workflow_state with the repo rootsession_history with latest operationworkflow_state.context in the status reportSee references/recommendation-logic.md for full recommendation rules and skill list.
Quick reference:
| Artifact | Path |
|---|---|
| Brainstorm | docs/brainstorms/ |
| Plan | docs/plans/ |
| Solution | docs/solutions/ |
| Runtime | .context/compound-engineering/ |
Available skills: 01-brainstorm, 02-plan, 03-work, 04-review, 05-learn, 07-worktree
Fallback: If workflow_state is unavailable, use bash ls/find to check directories, then read recent artifacts.
Before finishing this skill, apply the completion checklist in shared pipeline instructions.
Baseado na classificação ocupacional SOC
Discover requirements through structured multi-round dialog. Use when the request is ambiguous, needs discovery, or describes a new idea/product.
Review code changes across five axes with evidence-first findings. Use after implementation is complete and before committing.
Turn requirements into an execution-ready plan with TDD-gated implementation units. Use when a brainstorm artifact exists and is ready for planning.
Execute plan units with TDD enforcement and checkpoint resume. Use when a plan path is ready for implementation.
Capture solved problems as searchable solution artifacts. Use after a workflow loop completes or a non-trivial problem is solved.
Create and manage git worktrees for isolated feature development. Use when starting a feature that needs branch isolation.
