task

1# Task Progress Tracking
2 
3Record development progress on a durable task: phase, progress, next step,
4blockers, and validation evidence.
5 
6Requires the optional task command. Use `npx ai-devkit@latest` for task and
7agent commands. Before recording task events, run a real read probe:
8 
9```bash
10npx ai-devkit@latest task list --json
11# or, when a task name is known:
12npx ai-devkit@latest task list --name <task-name> --json
13```
14 
15Only treat task tracing as available when the read probe exits 0. If it fails,
16continue without task logging and include the failed command plus stderr/stdout
17summary in the final report. Do not block the user's work just because optional
18task tracing is unavailable or unusable.
19 
20## Core idea
21 
22- **One task per work item.** Create it once; advance its `phase` field as work
23  moves through the lifecycle or debug workflow.
24- **`<id>` can be a task name.** Every command below accepts the task name in
25  place of a task id, resolving to the latest non-terminal task. Prefer
26  `<task-name>` so agents do not track task ids.
27- **Choose stable names.** For lifecycle work, use the feature key as the task
28  name. For debugging or review work, choose a short kebab-case task name.
29- **Emit at checkpoints, not streaming.** Phase transitions, task toggles,
30  immediate next-step changes, fresh evidence, blockers discovered/resolved. A
31  handful of calls per session.
32- **Sequence mutations.** Never run task mutation commands in parallel for the
33…