Synopsis
aigon feature-prioritise <feature-name or letter>Shortcuts
/afp(slash command) ·aigon afp(CLI)
Description
feature-prioritise graduates an already allocated F<ID> feature from the inbox to the backlog. It resolves depends_on declarations to canonical IDs, checks for circular dependencies, and records the lifecycle transition; it does not assign or rekey the feature ID.
The name argument accepts partial matches — if you type dark, Aigon finds any inbox spec whose filename contains that string. If multiple match, it lists them and asks you to pick.
Always use this CLI command — never manually move or rename spec files. The CLI handles ID assignment, workflow state migration, and git housekeeping atomically.
What it does
- Finds the matching spec in
docs/specs/features/01-inbox/ - Assigns the next available numeric ID
- Renames the file to
feature-<ID>-<slug>.md - Resolves
depends_ondeclarations to canonical numeric IDs - Validates that no circular dependencies exist
- Migrates any existing slug-keyed workflow state to the numeric key
- Moves the spec to
02-backlog/and commits the change
Examples
# Prioritise by partial name
aigon feature-prioritise dark-mode
# Prioritise interactively — list all inbox specs
aigon feature-prioritiseNext steps
After prioritising, choose your mode:
# Drive mode (branch in current repo)
aigon feature-start <ID>
# Drive worktree (isolated, parallel development)
aigon feature-start <ID> cc
# Fleet mode (multiple agents compete)
aigon feature-start <ID> cc ag cxRelated
feature-create— create the inbox spec (run before prioritise)feature-start— create the workspace (run after prioritise)feature-rename— rename an inbox spec before it has been prioritised
Last updated on