to-tasks
Installation
SKILL.md
To Tasks
Turn one approved PRD into an executable queue. Each slice fits one focused implement-and-review run and has a checkable acceptance contract. You draft the queue yourself with repository tools. One already accepted task with a complete contract goes straight to implement-and-review; do not manufacture a PRD and queue for it.
Read .ai-workflow/work/<feature-slug>/prd.md; a status other than approved goes back to to-prd. Write tasks.md and one T<N>-<slug>/brief.md per task, as shared/references/work-state.md lays out and references/task-contract.md details. Approval promotes those same files.
Draft the slices
- Read the relevant code and find the repository commands that can verify each slice. Never invent a command.
- Cut vertical slices: each is one observable path through the layers it needs, ideally a tracer bullet that verifies on its own. Put a behavior-preserving prefactor first only when it removes a shared blocker, and name the characterization test or suite that protects it. A codebase-wide mechanical change uses expand, migrate, and contract slices.
- Assign stable IDs
T1,T2, …. IDs never change, because approval refers to them: a split gets a new ID, a deletion leaves a gap, and reordering keeps IDs. Dependencies name IDs; no self-blockers or cycles. Mark a sliceHITLonly when a human decision or authorization truly remains; otherwiseAFK. - Write each slice's contract:
- The end-to-end behavior, without file paths.
- Verified commands and observable acceptance behavior. For stateful work, the meaningful failure sequences, and which adapters need realistic stored-value or integration checks. A non-feature slice may state
Test expectation: none; <reason>. Never delete, skip, weaken, or mock away a check to make the contract pass; a wrong contract goes back before approval. - Design: assess shared design, security, interface, and acceptance decisions once across the queue (
shared/references/workflow-stage-routing.md) and cite them by decision ID in each task that relies on them. Rundesign-gateonly on an unresolved or changed boundary. Every published slice has aproceedverdict and no open decision. security-gatewith its matched trigger. Atest-lensconclusion only when it settled a real test-design choice.- Rollback, review focus, product blockers, and write conflicts, kept separate. Name the owner of each shared contract and what releases its consumers. Serialize slices that share a migration, contract, security surface, or likely write scope unless a merge plan says otherwise. Do not invent a foundation phase just to create parallel work.
- For a new feature, mark each task
criticalor deferred for feature mode. A task is critical when it carries high risk, a shared contract, or adeepsecurity level. Each task names its focused regression checks and the contract tests its dependents rely on. - Check the queue yourself: every dependency exists, there is no cycle, owned paths overlap only under a merge plan, and every task's gates read
proceedwith no open decision.