add-id-conventionlisted

# ID & Branch Naming Convention <!-- uses: - skill: add-doc-schemas - command: /add.build - command: /add.new - command: /add.plan - command: /add.review - script: build-setup.sh - script: done.sh - script: get-branch-metadata.sh - script: next-id.sh - script: qa-evidence.sh - script: status.sh --> ## Overview Scripts enforce this format; commands that diverge (e.g., letter-first `H0001` instead of `0001H`) produce branches that `done.sh` cannot parse. ## When to Use - Before allocating a new ID via `status.sh next-id` - Before `/add.new` records `branch:` in about.md frontmatter, and before `/add.build`'s `build-setup.sh` runs `git checkout -b` for feature/hotfix/refactor/chore/docs branches - Before writing `id:` in a doc frontmatter - When writing `{{doc:ID}}` references ## When NOT to Use - Scripts that already implement the convention (`next-id.sh`, `get-branch-metadata.sh`, `build-setup.sh`) — they are the authority, not this doc - Unrelated IDs (e.g., `CHG[NNNN]` for changelogs — different namespace, no letter suffix) - Provider-specific issue trackers (Jira/Linear) — they own their own ID schemes ## Canonical Format ``` [NNNN][L] ``` - `[NNNN]` — 4-digit zero-padded decimal (`0001`, `0042`, `1337`) - `[L]` — single uppercase letter suffix identifying the work type ### Letter suffixes | Letter | Type | |--------|------| | `F` | feature | | `H` | hotfix | | `R` | refactor | | `C` | chore | | `D` | docs | | `P` | perf | | `T` | test | Must match the regex in