tasks

Implementation tasks are generated from a design spec by delegating context to a task-planner agent, which produces a reviewable tasks.md artifact containing POC-first, value-slice execution steps with explicit verification requirements.

A POC-first task generation workflow structures implementation around a mandatory proof-of-concept milestone, producing a full phase breakdown that gates progress and minimizes drift or hallucinated artifacts before full execution.

Two-stage task review works by running parallel spec-compliance and code-quality reviews to gate progress, storing verdicts in a state file, and stopping execution at an explicit approval gate to prevent silent passes.

Yes, an active spec containing both design.md and requirements must exist and be snapshotted before task generation, ensuring the workflow operates on an approved, deterministic baseline.

The best way to ensure verification evidence is to enforce deterministic coordination constraints that require tasks to be value-slice and executable, stopping at an explicit approval gate until compliance and quality reviews are passed.

Automated task generation should not be used when an active spec is missing, when design.md or requirements files do not exist, or when the workflow cannot be snapshotted to establish a deterministic baseline.