Implement
Execute plan from explore, tracked via beads.
Flags
- •
--fresh: Clear context first (EnterPlanMode → summarize progress → user approves → continue)
Steps
- •Find plan:
- •arg →
bd show <arg> - •no arg →
bd list --status in_progress(resume existing) - •still nothing →
bd ready(pick next unblocked) - •No issue? → "Nothing to do. Run /explore first"
- •arg →
- •If --fresh: EnterPlanMode, summarize completed/remaining from notes, get approval
- •Mark in_progress:
bd update <id> --status in_progress - •CHECK FOR OPEN QUESTIONS in plan:
- •If notes has unresolved questions → resolve via
AskUserQuestionFIRST
- •If notes has unresolved questions → resolve via
- •FOR EACH TASK (MANDATORY subagent dispatch):
code
a. Task tool → implementer subagent (paste full task text) - Implementer MUST use TDD: failing test → minimal code → pass b. Task tool → spec reviewer subagent → if issues: fix → re-review c. Task tool → quality reviewer subagent → if issues: fix → re-review d. Update beads notes with progress
- •NEVER implement tasks yourself - ALWAYS dispatch via Task tool
- •If task fails → use Skill tool to invoke
debugging - •TDD is mandatory unless explicitly building throwaway prototype
- •EARLY VERIFICATION: After FIRST task, run build/check to catch design flaws
- •Update notes after each task:
bd update <id> --notes "COMPLETED: X. NEXT: Y" - •Context getting stale? → suggest
/implement --freshto user - •Final →
bd close <id>+ use Skill tool to invokefinishing-branch
Subagent Prompts
- •subagent-driven-development/
implementer-prompt.md - •subagent-driven-development/
spec-reviewer-prompt.md - •subagent-driven-development/
code-quality-reviewer-prompt.md
Key: paste full task text + context into prompt. Don't make subagent read files.