Agent skill
step3
ONLY when user explicitly types /step3. Never auto-trigger on execute, run, or implement.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/step3
SKILL.md
/step3 - Execute Plan via Subagents
Execute _step2_plan.md by dispatching phases to subagents. Main thread orchestrates only.
Designed for fresh session — no prior context needed. _step2_plan.md contains everything.
Execution model: All-or-nothing. A git checkpoint is created before any phase runs. If anything fails, the user resets to the checkpoint — no partial recovery, no resume.
Orchestrator Rules
Main thread is a lightweight dispatcher:
- Reads _step2_plan.md ONCE at start
- Stores only: phase numbers, dependencies, parallel groups, titles
- Dispatches subagents via Task tool (general-purpose)
- Reports 1-line progress per phase
Main thread NEVER:
- Executes tasks directly
- Reads files beyond _step2_plan.md
- Accumulates subagent details in its own context
Execution Flow
1. CHECKPOINT
- Run: git add -A && git commit -m "checkpoint before run" && git push
- Store the commit hash (git rev-parse HEAD)
- This commits everything including _step2_plan.md — the safety net
2. LOAD
- Read _step2_plan.md, verify marker <!-- @plan: /step2 ... -->
- Parse phases overview table (deps, groups, titles)
3. EXECUTE LOOP
While phases remain:
a. Find ready phases (deps satisfied, not done)
b. Batch by parallel group:
- All ready in same group → ONE message with MULTIPLE Task calls (parallel)
- NEVER mix different groups in parallel
c. Dispatch subagent(s) — one Task call per phase
d. On ANY failure: STOP, jump to FAILURE
e. Log: "✓ Phase N: [title]"
4. ON SUCCESS
- Delete _step2_plan.md
- Run: git add -A && git commit -m "run complete: [Goal field from _step2_plan.md]" && git push
- Store the final commit hash
- Report: "Run complete. N/N phases succeeded. Committed & pushed: <short-hash>"
5. ON FAILURE — see Failure Protocol below
Failure Detection
A phase has failed when:
- The Task tool itself errors (agent crash, timeout)
- The subagent explicitly reports it could not complete a task
Failure Protocol
On any failure:
╔══════════════════════════════════════════════════════════════════╗
║ PLAN FAILED — RESET TO CHECKPOINT RECOMMENDED ║
║ ║
║ Checkpoint: <hash> (committed at start of this session) ║
║ ║
║ To recover: ║
║ git reset --hard <hash> ║
║ git push --force ║
║ ║
║ This discards ALL changes from this run and restores ║
║ the codebase with _step2_plan.md intact for a clean re-run. ║
╠══════════════════════════════════════════════════════════════════╣
║ Failed: Phase N — [error summary] ║
║ Completed before failure: Phases X, Y, Z ║
║ Not started: Phases A, B, C ║
╚══════════════════════════════════════════════════════════════════╝
Do NOT suggest partial recovery, resuming, or fixing in place. Propose the reset. If the user wants to keep partial changes, that's their call.
Subagent Dispatch
Each subagent receives ONLY:
First parallel group — full context:
# Context
Goal: [1-2 sentences from _step2_plan.md Goal field]
Rationale: [from _step2_plan.md Rationale section]
Working directory: [absolute path]
# Your Assignment: Phase N
[EXACT phase section copied from _step2_plan.md]
# Instructions
1. Read the Reference files FIRST — understand patterns before writing code
2. Execute all tasks in order
3. RESPECT Guardrails — these are hard constraints, not suggestions
4. Stay within Modifies scope — do not touch files outside it
5. On failure: stop immediately, return error details
6. Return 1-2 sentence summary of what was done
Later parallel groups — lighter context:
# Context
Goal: [1-2 sentences from _step2_plan.md Goal field]
Working directory: [absolute path]
Follow patterns in CLAUDE.md and Reference files.
# Dependencies
[Verbatim dependency notes from _step2_plan.md, e.g.:]
- Depends: 2 (creates lib/core.py)
# Your Assignment: Phase N
[EXACT phase section copied from _step2_plan.md]
# Instructions
1. Read the Reference files FIRST — understand patterns before writing code
2. Execute all tasks in order
3. RESPECT Guardrails — these are hard constraints, not suggestions
4. Stay within Modifies scope — do not touch files outside it
5. On failure: stop immediately, return error details
6. Return 1-2 sentence summary of what was done
Progress Output
/step3
Checkpoint created: abc1234
Loading _step2_plan.md... N phases, M parallel groups
Group A:
✓ Phase 1: [title]
Group B (parallel):
✓ Phase 2: [title]
✓ Phase 3: [title]
Group C:
✓ Phase 4: [title]
Run complete. N/N phases succeeded. Committed & pushed: abc1235
Constraints
- NEVER use EnterPlanMode. This skill IS the execution framework. Plan mode hijacks the dispatch loop.
- NEVER modify _step2_plan.md during execution
- NEVER execute tasks directly — always delegate via Task tool
- Minimal orchestrator context — 1 line per completed phase
- Same parallel group only — never cross-group parallel
- Fail-fast: stop on first failure, recommend checkpoint reset
- On success: delete _step2_plan.md, commit and push
- All-or-nothing: no resume, no partial recovery
- Gate: checkpoint before dispatch. NEVER dispatch any subagent until the checkpoint commit hash has been created and stored. Without the checkpoint, failure recovery is impossible. No checkpoint = do not proceed.
- Gate: cleanup before farewell. On success, NEVER report completion until
_step2_plan.mdhas been deleted and the final commit+push is confirmed. Missing either = skill failed.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?