What problem does it solve? Turning an approved technical design (TRD) into working, tested code requires coordinating developers, enforcing TDD discipline, managing Git branches, and tracking slice-by-slice progress — this Skill orchestrates that entire implementation stage of a spec-driven development pipeline so nothing is skipped or repeated. ## Core Features & Use Cases - TDD Implementation Orchestration: Invokes backend-developer and/or frontend-developer agents (in parallel for full-stack features, with worktree isolation) to implement code and tests following the TRD, with an approved plan before any code is written. - Vertical Slice Management: Reads the TRD task decomposition table, proposes the next pending slice, verifies the previous slice's PR is merged, and enforces one branch/PR per slice on GitHub Flow. - Review-Finding Resume Flow: When code review, QA, security, or SRE reject a slice, resumes the same implementing agent with the findings instead of restarting from scratch, dosing context to the size of the fix. - Governance Gates: Requires GitHub issues per task, blocks provider swaps without an ADR, forbids self-approval as a substitute for independent review, and logs per-track timing to timing-log.md. - Use Case: After your architect approves specs/user-auth/trd.md, run this Skill to implement the first vertical slice: it creates the branch, runs backend and frontend agents in parallel with TDD, confirms full test coverage, opens the PR, and hands off to code review. ## Quick Start Run /sdd-implement with the slug of a spec whose TRD is approved to implement its next pending slice via TDD on a new branch.
