task-implementer

Task implementation translates task documents into executable code while preserving traceability to requirements and design contracts. It enforces test-first development and atomic commits, ensuring every line of code links back to a requirement, ADR, or invariant.

Test-first development with atomic commits means writing failing tests before implementation and committing one task at a time. This approach ensures exact change sets that are reversible and traceable to specifications like UC, ADR, INV, or REQ.

You execute a SWEBOK-aligned pipeline by running the per-task implementer workflow for a specific task using a command like /sdd:task-implementer --task TASK-F0-003. It reads task documents, plan artifacts, and referenced specs to determine dependencies and update progress.

Yes, task implementation operates within a phase-aware workflow that reads task, plan, and referenced specs to determine dependencies. It updates task checkboxes in the TASK-FASE-{N}.md document as tasks progress through implementation.

Strict adherence to contracts and invariants is enforced by reading task documents, plan artifacts, and referenced specifications before implementation. This ensures the generated code maintains traceability and complies with defined design contracts throughout the process.

Atomic commits for task implementation may not suit projects lacking formal task documents or defined design contracts. The workflow relies on existing plan artifacts and referenced specs to maintain traceability and enforce test-first development effectively.