genkovich/sdd
9 subagents
Subagent
analystClean-context multi-perspective reviewer of an SDD feature's candidate approaches. Use during specify's ideation pass (hard depth) to pressure-test the three strategic approaches from three lenses —…criticClean-context coherence critic for SDD artifacts (a spec or a SAD). Use after a Socratic pass to detect cross-section drift, coherence damage from user edits, structural gaps, and constraint/ quality…devils-advocateClean-context adversary for SDD. Two modes, named by the dispatch prompt. (A) Ambiguity hunt over a written spec — used by clarify to find where two competent engineers would reasonably build…explorerRead-only brownfield scout for SDD. Use when a skill (design, data-model) needs the existing codebase mapped before it designs against it — module boundaries, the patterns already in use, where…implementerMakes a failing SDD test pass — the GREEN + REFACTOR + GATE steps of test-driven development. Use after test-author has produced a red test for a task.researcherClean-context competitive + adjacent-solution researcher for an SDD feature idea. Use during specify's ideation pass (medium/hard depth) to find how the market and adjacent products already solve…reviewerRead-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or…strategistClean-context generator of the three strategic approaches for an SDD feature idea. Use during specify's ideation pass (hard depth) to lay out genuinely different ways to solve the problem —…test-authorWrites the failing test FIRST for an SDD task — the RED step of test-driven development. Use when the implement engine needs a test that encodes a task's acceptance criteria before any production…