sdd

<!-- rig-generated --> # sdd+ — Subagent-Driven Development Wraps `superpowers:subagent-driven-development`. Requires superpowers to be installed. Use `tdd+` instead when tasks are tightly coupled or the plan is small — subagent execution costs more tokens and pays off on independent, parallelizable tasks. ## Typed Dispatch Override This project ships typed agent definitions in `.claude/agents/`. Where the delegated superpowers skill instructs `Task tool with general-purpose type`, instead dispatch the typed agent and pass only the per-task payload — the role content lives in the agent definition: - Implementation → `Agent(subagent_type="implementer", prompt=<full task text from plan + scene-setting context + working directory>)` - Spec compliance review → `Agent(subagent_type="spec-reviewer", prompt=<task requirements + implementer's report>)` - Code quality review → `Agent(subagent_type="code-reviewer", prompt=<DESCRIPTION + PLAN_OR_REQUIREMENTS + BASE_SHA + HEAD_SHA>)` If a typed agent is unavailable (definition deleted), fall back to a general-purpose subagent using the superpowers prompt template for that role. ## Plan Handoff: Subagent-driven (superpowers 6.4.1 #2258/#2318) Since 6.4.1, the superpowers plan handoff offers two execution approaches — Subagent-driven and Native (inline: the session implements every task itself) — and recommends one for the plan with a reason. When the delegated skill asks, answer **Subagent-driven**: this overlay's typed per-task d...