What problem does it solve?
Coordinating the code implementation phase of a story pipeline is error-prone: tasks must be executed in TDD mode, backend and frontend work must be routed to the right agents, and failures need controlled retry or rollback without corrupting the working branch. This Skill standardizes that implementation stage.
Core Features & Use Cases
- Agent Routing by tech_type: Routes implementation to backend-developer, frontend-developer, or a serial two-round fullstack flow based on meta.yaml.
- TDD Implementation via speckit: Invokes /speckit.implement against tasks.md so all tasks are completed test-first with code-scope whitelist enforcement.
- Controlled Retry and Rollback: Supports in-place round retries (up to 3) and attempt-level re-entry with path-scoped git checkout to the baseline commit, excluding the work directory.
- Use Case: A confirmed story with spec.md, plan.md, and tasks.md is implemented by dispatching the backend developer first, then the frontend developer against the plan's API contract, with phase advancing to implemented only after tests pass.
Quick Start
Run the implement stage for the current story using the existing spec.md, plan.md, and tasks.md in the work directory.