implement-task

Task implementation from a specification requires claiming the task, reading context, writing code with incremental commits, adding test coverage, and finishing with a completion summary. This approach ensures traceable progress and verifiable results throughout the worktree.

Spec-driven task execution turns a specification into working code phase-by-phase within a worktree. It requires citing spec requirements for implementation decisions and flagging assumptions, ensuring disciplined, front-loaded development with explicit acceptance criteria.

Yes, this task implementation process requires a written specification to cite for implementation decisions and mandates test coverage for verification. It applies to tasks needing incremental commits and phase-by-phase work within a version control worktree.

The best way to ensure traceability is a disciplined process that explicitly requires citing spec requirements for every implementation decision and flagging any assumptions. This front-loaded approach guarantees alignment between the working code and the original specification.

You should avoid phase-by-phase task implementation in a worktree for tasks that do not require incremental commits, test coverage, or a formal specification. This process is designed for disciplined, structured work rather than rapid prototyping without verifiable results.