Multi-Agent Parallel TDD Development

Execute an implementation plan by dispatching multiple subagents in parallel, each following test-driven development, then hand off to the ss-code-review skill for one comprehensive review pass once every task passes its tests.

Core architecture: the orchestrator (you) never writes code. You read the plan, dispatch subagents, track progress, and collect results. All code is written by implementer subagents.

Fresh-context assumption: each implementer subagent starts with no chat history. Give it the authoritative plan path plus exact task number/heading, concise scene-setting context, applicable spec paths, interfaces/dependencies, cwd, scope boundary, and verification commands. The implementer reads only that task and its referenced material from the repository instead of receiving a duplicated full-task payload.

Inputs

This skill expects one of:

• a path to a plan file already broken into tasks (produced by the ss-plan skill);
• a link to an external requirement or design document (wiki page, ticket, PRD);
• a plain-language description of the requirement.

If none of these is supplied, ask the user for one before proceeding.

Iron Rules