subagent-driven-development

Subagent-Driven Development

Execute a plan with one fresh implementer per task, a task-scoped review after each implementation, and one whole-branch review at the end.

This workflow requires isolated worker dispatch. If the host cannot dispatch subagents, use executing-plans instead.

Core principle: Fresh implementer + spec and quality review + scoped fixes + final review.

Narration: Between tool calls, use at most one short line. The ledger and tool results carry the durable record.

Continuous execution: Run every task without asking whether to continue. Stop only for an unresolved blocker, ambiguity that prevents safe progress, or completed work.

When to Use

Use this workflow when all are true:

• A decision-complete implementation plan exists.
• Tasks are independent enough for one implementer at a time.
• Work stays in the current session.
• The host supports isolated workers.

Use executing-plans for a parallel session. Return to planning when tasks are tightly coupled or the plan is incomplete.

Setup

1. Verify an isolated workspace with using-git-worktrees. Work on main or master only with explicit user consent.

2. Invoke this skill's scripts through Bash on every platform because packaging may not preserve executable bits. On Windows, use Git Bash.

3. Resolve the plan workspace:

   bash <skill-dir>/scripts/sdd-workspace PLAN_FILE
   

   The command prints <repo-root>/.skillquiver/sdd/<plan-basename>-<path-hash>/. This git-ignored directory owns every artifact for this plan: ledger, briefs, reports, and review packages. Never reuse another plan's directory.

4. Inspect <workspace>/progress.md:

   • If its first line names this plan, treat every Task <N>: complete line as authoritative and resume at the first incomplete task.
   • If a task ends with a fix-round entry, resume at the next round.
   • If the ledger names another plan, or exists at the obsolete .superpowers/sdd/progress.md, leave it intact and create this plan's ledger.

5. Create a missing ledger with # SDD ledger — plan: <plan file path> as its first line.

6. Read the plan once, record its context and Global Constraints, and create one todo per task.

7. Before Task 1, scan the complete plan for contradictions between tasks, Global Constraints, and the review rubric. Present all conflicts in one batched question beside the binding plan text. Proceed immediately when the scan is clean.