メニュー
Systematically isolate, reproduce, and resolve task execution failures. Activates when the user invokes /systematic-debug or asks momentum to run the systematic-debug recipe.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Begin a new implementation phase. Activates when the user invokes /start-phase or asks momentum to run the start-phase recipe.
Work with concurrent workstreams (Rule 15). Activates when the session involves multiple active branches, cross-lane coordination, or when starting work that should not live on the current branch.
Record a new backlog item (bug, feature, tech debt, or enhancement) when you discover work that needs tracking. Activates when the session identifies unplanned work that should be tracked in the backlog.
Check spec structure health of the momentum project. Activates when the user runs `/validate`, asks for a health check, or when spec changes need verification before phase completion.
>-
Drive a single repo through its phase as part of a swarm. Activates when spawned by the conductor (the user's primary session) with a spawn directive. State lives in files; the conductor reads board.json between turns. Loads on the swarm-supervisor invocation only — not invoked directly by the user.
| name | systematic-debug |
| description | Systematically isolate, reproduce, and resolve task execution failures. Activates when the user invokes /systematic-debug or asks momentum to run the systematic-debug recipe. |
Systematically isolate, reproduce, and resolve task execution failures.
This recipe enforces the 3-strikes systematic debugging/retry budget defined under the Autonomous Execution Contract. If validation fails for a task, execute the strikes sequentially:
[x] and proceed.[x] and proceed. Clean up any temporary scratch scripts.specs/status.md (to check active context)specs/phases/phase-N-*/overview.md (to re-read goals and deliverables)specs/phases/phase-N-*/plan.md (to review architectural choices)