status-taxonomy.yml
Status: Shipped Generated from app @ 1b3d5a69d73473db077dfb44f4390b42cded6bd4 Regenerate: pnpm gen:reference
A team’s statuses (also called phases) live in content/status-taxonomy.yml. The file is optional: without it, a team gets the default statuses.
Statuses
Default statuses
| Id | Label | Role | Color | Icon |
|---|---|---|---|---|
planning | Planning | not_started | #64748b | CircleDashed |
todo | Todo | not_started | #94a3b8 | CircleDot |
in-progress | In progress | active | #0ea5e9 | Circle |
blocked | Blocked | blocked | #ef4444 | Ban |
review | Review | review | #8b5cf6 | Eye |
qa | QA | review | #f59e0b | ShieldCheck |
done | Done | done | #10b981 | CheckCircle2 |
status-taxonomy.yml
A top-level states: list. Each entry:
| Key | Type | Required | Default | What it does |
|---|---|---|---|---|
id | string | yes | — | Status id, used in frontmatter (status: in-progress). |
label | string | — | — | Name shown on the board. |
color | string | — | — | Hex color. Default: a neutral slate. |
icon | string | — | — | Lucide icon name. Default: the role's icon. |
order | integer | — | — | Column order. Missing values go after the highest one. |
role | StatusRole | — | active | What the status means to the app. Absent or unknown: active. |
delivered | boolean | — | — | Set false on a done-role status to mark it dropped (won't-do); velocity then leaves it out. |
Roles
The app keys its behavior off a status’s role, so you can rename, recolor, add or reorder statuses freely.
| Value | Default | Meaning |
|---|---|---|
not_started | — | Not begun yet. |
active | yes | Work in progress. The default for a status with no role. |
review | — | Waiting for review. |
done | — | Finished. Counts toward velocity unless delivered is false. |
blocked | — | Can't proceed. |
states:
- id: todo
label: To do
role: not_started
- id: in-progress
role: active
- id: design-review
label: Design review
role: review
color: "#8b5cf6"
- id: done
role: done
- id: wont-do
label: Won't do
role: done
delivered: false A broken file never breaks the app: CodeSense falls back to the defaults and shows a warning.
Nothing in CodeSense checks or blocks a status move, and no file defines agent work between statuses. To run tests or an agent when a story moves on, have the agent or a routine do it.
Generated from app @ 1b3d5a69d73473db077dfb44f4390b42cded6bd4 Regenerate: pnpm gen:reference
How we know this is accurate 2 sources
Checked against the app at 1b3d5a69d73473db077dfb44f4390b42cded6bd4.
Code
-
src-tauri/src/commands/status_taxonomy.rs -
src-tauri/src/commands/pipeline_scanner.rs