pipeline-implement

name	pipeline-implement
description	Use after tasks.yaml and thin task contracts exist to implement the dependency-ordered task graph and mark tasks done only after verification passes.

Pipeline Implement

Stage 4: tasks -> implementation.

Execute .pipeline/<feature>/tasks.yaml. Work in dependency order. Use parallel agents only when the active tool supports them and the tasks are truly independent; otherwise run sequentially.

Process

1. Read tasks.yaml and all pending task contracts.
2. Compute the next wave: pending tasks whose dependencies are done.
3. For each task:
   • Read its contract fully.
   • Inspect only the repo context needed for its anchors and areas.
   • Implement the expected changes.
   • Add or update tests.
   • Run the task verify commands.
   • Mark the task done only if verification passes.
4. Stop and mark blocked when the task contract is wrong, underspecified, or cannot be made green without changing decisions from spec.md or plan.md.
5. After all tasks are done, run final_gate from tasks.yaml.

Handoff

Assembled implementation with green task gates -> pipeline-review-and-plan.