work-implement

Reference the US-XXX or TK-XXX identifier and the Skill loads the user-story-tasks flow: it creates the feature branch, presents the Ready task queue, then implements one task per turn using Red-Green-Refactor. Tests are written before production code and scoped to affected files only.

Reference a TC-XXX or FT-XXX and the Skill translates each Ready, non-manual test case into an automated test faithful to its preconditions, steps, and expected results. The test name includes the TC identifier for traceability, and coverage gaps are recorded in progress.md.

Yes, when the scope includes multiple units and the implementation policy resolves confirmByUnit to never, or the user explicitly requests it. The Skill then runs independent units in subagents with git worktrees, up to the configured maxParallel limit, merging sequentially.

No. It only runs tests, lint, typecheck, and build scoped to the files or package affected by the unit, plus one e2e run at closure. The full repository test battery is the exclusive responsibility of the quality-check skill during integration or PR creation.

The Skill applies a per-problem attempt limit from the escalation policy. When attempts are exhausted without a new hypothesis, it stops, presents a blocking report, and asks the user how to proceed. It never disables tests or relaxes assertions to force a pass.

Do not use it for work still in Draft status, for writing new functionality from a feature artifact (features only yield test automation), or for editing specifications. Specification changes belong to the planning skills work-define, work-plan, or test-define.