Menu
Track a backlog item — bug, feature, tech debt, or enhancement. Activates when the user invokes /track or asks momentum to run the track recipe.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | track |
| description | Track a backlog item — bug, feature, tech debt, or enhancement. Activates when the user invokes /track or asks momentum to run the track recipe. |
Track a backlog item — bug, feature, tech debt, or enhancement.
Read specs/backlog/backlog.md to find next available ID
Determine item type:
BUG-NNNFEAT-NNNTD-NNNENH-NNNAdd row to appropriate table in specs/backlog/backlog.md:
openunscheduled— for one-liners, [→](details/{ID}.md) if a detail file is createdDecide: one-liner or detail file?
One-liner (no detail file needed):
Detail file required (specs/backlog/details/{ID}.md):
If a detail file is needed, create it now with: context, options considered, open questions.
If P0, also update Critical Items table in specs/status.md
Commit:
git add specs/backlog/
git commit -m "docs(backlog): add {ID} - {short title}"
/track operates on the current repo's specs/backlog/. The ecosystem
layer (Phase 9) does NOT aggregate backlogs across member repos in
Tier 1 — each repo's backlog stays authoritative for its own work. If
an item's scope genuinely spans repos, file it in the repo that owns
the most surface area and add a one-line cross-link from the others.
For cross-repo features as a whole (vs. individual backlog items), use
/initiative create <slug> — see the /ecosystem and /initiative
command recipes.
Begin a new implementation phase. Activates when the user invokes /start-phase or asks momentum to run the start-phase recipe.
Work with concurrent workstreams (Rule 15). Activates when the session involves multiple active branches, cross-lane coordination, or when starting work that should not live on the current branch.
Record a new backlog item (bug, feature, tech debt, or enhancement) when you discover work that needs tracking. Activates when the session identifies unplanned work that should be tracked in the backlog.
Check spec structure health of the momentum project. Activates when the user runs `/validate`, asks for a health check, or when spec changes need verification before phase completion.
>-
Drive a single repo through its phase as part of a swarm. Activates when spawned by the conductor (the user's primary session) with a spawn directive. State lives in files; the conductor reads board.json between turns. Loads on the swarm-supervisor invocation only — not invoked directly by the user.