Implement Tasks

Validate scope with the current coordinator and direct tools. Prepare one concrete preview through shared/references/model-preview.md before worker dispatch. Reuse an exact combined task and model approval or the parent's immutable snapshot; do not present another model selection for an unchanged plan.

Model IDs, effort support, and task defaults come only from shared/model-routing.json. Resolve the relevant route before preview or approval; preserve the exact saved route during dispatch, retry, and resume. For a new future plan, resolve its coordinator and each task through the batch preview in shared/references/task-shaped-model-routing.md. Record each task's risk evidence. Keep current and selected future coordinator values separate; host selection is required before future startup when they differ or are unknown. Existing approved plans keep their exact routes.

Turn an approved queue into a verified change. Be a thin conductor: own model selection, scheduling, integration, and delivery. implement-and-review owns task implementation and focused evidence. The bound review policy selects task review or one final feature review.

The feature sequence is interview-me → to-prd → to-tasks → implement-tasks. Receive the approved PRD and canonical task queue under .ai-workflow/work/<feature-slug>/. For one bounded, specified change with clear acceptance and no unresolved product, security, public contract, data ownership, or dependency decisions, use the existing standalone implement-and-review path. It keeps exact model approval and independent review without creating a feature PRD or task graph. Missing material decisions return to the appropriate earlier stage.

Use shared/references/workflow-measurement.md for the feature measurement record and capture API. Keep each stage's execution ledger and immutable plan intact. Capture stage-start for implement-tasks before preparation, any actual model approval wait, reserved repair calls, and stage-end after integration and required checks. Reused combined approval adds no new wait. Reuse the feature measurement path and bind remaining known identity fields once. Import completed separate stage ledgers with stage-ledger before terminal capture; the local implementation ledger is counted directly. Declare worker coverage only when local and required imported records cover all calls.