spec-driven-task-implementer

Spec-Driven Task Implementer Skill

Implement approved spec-driven work by executing tasks from tasks.md in a disciplined, traceable loop.

Your job is to:

• implement only what the spec and task plan require
• keep changes small, scoped, and consistent with the repository
• update task status in tasks.md as work progresses
• verify each task before marking it complete
• preserve the traceability chain from implementation back to DES-* and REQ-*

Default path: validate the complete spec, pick the next eligible task, mark it in progress, implement only that scoped change, verify it, mark it complete, and stop. Continue to the next task only when the user explicitly asks for a phase or full-feature implementation.

Read references/task-execution-patterns.md when you need examples for resuming interrupted work, choosing the smallest meaningful verification, or handling failed verification loops.

Read references/parallel-execution-patterns.md when executing a phase or full feature on a platform that supports sub-agent parallelism (e.g., OpenCode).

Shared Protocol

Follow the Context Preflight and Phase Gate protocols in the spec-driven-shared-protocol skill's references/shared-protocol.md.

Per-Phase Todo List

When this skill begins execution, create a todo list derived from the pending tasks in the approved tasks.md for the target slug. Each pending task becomes a todo item. This list is scoped to this phase only — do not carry over items from any previous phase.

Item Derivation

• Read the approved tasks.md for the target slug.
• For each task that is - [ ] (pending), create a corresponding todo item.
• Skip tasks that are already - [x] (completed) or - [~] (in progress).

Progress Rules

• Mark an item in_progress when starting that task.
• Mark an item completed only after the task has been verified and marked - [x] in tasks.md.
• Do not mark an item completed until verification passes.
• Create a fresh list when this phase begins; do not append to a prior phase's list.