to-tasks
To Tasks
Draft with the current coordinator and direct repository tools. This work needs no full model preview or extra worker. Before dispatching a design or security worker, use shared/references/model-preview.md once for the required routes. Nested work uses the parent's immutable approved snapshot.
Turn one approved PRD into an executable queue. Each slice is small enough for one focused implementation run and has a checkable acceptance contract.
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 to-tasks before drafting, the actual queue approval wait, and stage-end after promotion. A combined task and model response is one observed wait. Bind the required-check identity when fixed; unknown values remain absent.
Boundary
Receive .ai-workflow/work/<feature-slug>/prd.md with status approved. Write each canonical tasks/T<N>-<slug>.md once with status draft. Keep tasks-draft.md as the compact approval and dependency index. Approval promotes these same files to ready-for-agent; it does not create a second contract copy. Read references/task-contract.md for the task fields, index, approval binding, and legacy queues.
Read shared/references/workflow-stage-routing.md before drafting. Assess shared design, security, interface, and acceptance decisions once. When tasks reuse these decisions, follow shared/references/planning-reuse.md to check source revisions and render complete gate records from shared conclusions and task differences. Each slice still classifies its own design risks and security triggers. Apply design-gate only to unresolved or changed boundaries; matching settled decisions need no repeated lens pass. A published slice has the canonical gate result from shared/references/gate-result.md, including findings and review focus, with verdict: proceed and decision_required: none. Use test-lens only for a real test design decision, such as an integration boundary, mock boundary, concurrency case, or brittle existing test.
Do not call individual design lenses directly, a panel, a runner, or models-consensus. A decision_required result or an unanswered material requirement returns to the user before task approval. If the user explicitly wants extra opinions, direct them to invoke models-consensus; its own workflow presents the proposed seats for user approval before it runs.
Default to task-only approval for a planning request. When the request includes execution, offer one combined task and model approval using the concrete preview. If the user requests combined task and model approval, prepare the concrete execution preview through implement-tasks before asking for one response that covers both decisions. Task-only approval never becomes model approval. Delivery and council authority remain separate.