task-generation

Task Generation Guide

Task Format (REQUIRED)

Every task MUST strictly follow this format:

- [ ] T### [P?] [US#|OBJ#?] {(FR|TR|OR|RR)-###?} [COMPLETES (FR|TR|OR|RR)-###?] Description with file path [after:T###?] [← T###:Symbol?] [→ exports: Symbol?] [VERIFY: <command>]?*

[VERIFY: <command>] is optional and repeatable (zero or more; typically 0–3). It appends after → exports: (and after [COMPLETES ...]). The command text runs from [VERIFY: to the next ] and MUST NOT contain a literal ] — move such checks into a verify script and reference it when needed.

Format Components

1. Checkbox: Always - [ ] (markdown checkbox)
2. Task ID: Sequential (T001, T002...) in execution order
3. [P] marker: Only if parallelizable (different files, no dependencies)
4. [US#|OBJ#] label: Required for delivery phases only
   • Product specs use [US#] for user story phases
   • Technical and operational specs use [OBJ#] for objective phases
   • Setup/Foundational phases: NO work-item label
   • Polish phase: NO story label
5. {(FR|TR|OR|RR)-###} tag: Links task to the requirement(s) it implements
   • Use {FR-001} or {TR-001} for a single requirement, {FR-001,FR-003} for multiple
   • Required for tasks that directly implement a requirement
   • Setup/infrastructure tasks with no direct requirement mapping may omit this tag
6. Description: Clear action with exact file path
7. after:T### clause (optional): Explicit task-level dependency when a task depends on artifacts from a different phase or a non-adjacent task within the same phase. Omit when sequential T### ordering within a phase already implies the dependency.
8. ← T###:Symbol import hint (optional): Lists specific symbols consumed from another task's output file, by source task ID. Use when data-model.md, contracts/, or the Requirement Coverage Map Function(s)/Symbol(s) column provide enough detail to name the symbols. Omit for leaf tasks with no cross-file coupling.
9. → exports: Symbol(params) export hint (optional): Lists the 1–3 most important symbols this task's file will export, with key parameter or field hints. Source from data-model.md entities, contracts/ schemas, or the Requirement Coverage Map Function(s)/Symbol(s) column. Omit when no downstream task depends on this file.
10. [COMPLETES (FR|TR|OR|RR)-###] marker (optional): Placed on the last task implementing a requirement that spans 3+ tasks. Signals the implementing agent to verify the full requirement chain at this task's completion.
11. [VERIFY: <command>] annotation (optional, repeatable): A machine-checkable acceptance assertion the Developer MUST run from the repo root before marking the task [X]. Non-zero exit (for commands) or no match (for grep patterns) is FAILURE — the task stays [ ] and routes into the error-recovery loop. Emit when a deterministic check is derivable: prefer a plan.md ## Testing Strategy test command scoped to the task's file/requirement; else a grep for a → exports: symbol declaration; else a build/typecheck command targeting the task's file. Omit when no deterministic check is derivable. Commands MUST NOT contain a literal ].