TaskTracker

Task

Parse tasks.md into structured task objects with status metadata.

Inputs

Feature directory containing tasks.md.

Execution Rules

Preserve order, infer status consistently, fail closed on malformed task candidates, and return machine-readable output only.

Output Format

Return a single JSON array of parsed task objects for valid input. Return one JSON error object for invalid input.

1. Read FEATURE_DIR/tasks.md. If missing or empty → return [].
2. Run node scripts/parse-tasks.mjs "FEATURE_DIR/tasks.md" from the repository root and parse its JSON output. This parser recognizes these two accepted forms:

• Standard task: - [ |X|x] T### [P?] [US#|OBJ#?] {(FR|TR|OR|RR)-###?} [COMPLETES req?] Description [after:T###?] [← T###:Symbol?] [→ exports: Symbol?] [VERIFY: <command>]?*
• QC bug task: - [ |X|x] T### [BUG:severity] [RECURRING?] [ESCALATED?] [DEFERRED?] {(FR|TR|OR|RR)-###?} [category?] Description
• Checkbox: [ ]=pending, [X]/[x]=completed
• ID: T###
• Optional [P] → parallel=true
• Optional [US#]/[OBJ#] → workItem, story, objective
• Optional [BUG:CRITICAL|ERROR|WARNING] → bugSeverity
• Optional modifier tags [RECURRING], [ESCALATED], [DEFERRED] → modifiers array and deferred boolean
• Optional [category] after requirement tags on bug tasks → bugCategory
  • Optional {FR-###}, {TR-###}, {OR-###}, {RR-###} (comma-separated) → requirements array
  • Extract filePath from the task description when a path is present
  • Optional [COMPLETES (FR|TR|OR|RR)-###] → completesRequirement string (e.g. "FR-003")
  • Optional after:T### (comma-separated for multiple) → dependencies array (e.g. ["T005", "T008"])
    • Optional ← T###:Symbol,Symbol → imports array of {"sourceTask": "T###", "filePath": "src/example.ts", "symbols": ["Symbol"]} objects when the source task can be resolved from the parsed task list
    • Optional ← plan:AcceptanceTestStubs → imports entry of {"sourceTask": "plan", "filePath": null, "symbols": ["AcceptanceTestStubs"]} marking this as an acceptance test stub task; the Developer reads the ## Acceptance Test Stubs section from plan.md directly (no task ID to resolve, filePath stays null)
  • Optional → exports: Symbol(params),Symbol → exports array of symbol strings
  • Optional [VERIFY: <command>] (repeatable; zero or more) → verify array of command strings. The command MUST be non-empty and MUST NOT contain a literal ]. Commands run from the repo root.
  • Remaining text (after removing parsed annotations) → description
• Current heading → phase
  • After parsing all tasks, resolve dependencies and imports[].filePath by matching referenced task IDs to parsed tasks in the same tasks.md
• Include completed tasks. Ignore non-task prose, headings, and checkbox lines whose first token is not task-like. Preserve order.
• A checkbox line with a task-like first token (T...) is a task candidate. Invalid checkbox state, T### ID, requirement, dependency, import, export, or VERIFY annotation is a parse error, never an ignored line.

1. If parser output has valid: false, a non-empty errors array, invalid JSON, or a non-zero exit, return exactly {"tasks": [...], "parseErrors": [{"line": 12, "code": "invalid-task-id", "message": "invalid task ID T12; expected T###", "source": "- [ ] T12 ..."}]} using the parser's partial tasks and errors. Do not return a bare array or continue with partial parsing.
2. For valid parser output, return only its tasks value as the stable single JSON array: