Menu
Fast-track feature <name> - create + setup + implement in one step
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Revise the current feature worktree after code review — decide accept/revert/modify
Show Aigon commands
Close feature <ID> [agent] [--adopt] - merges branch, cleans up, optionally adopts from losers
Create feature <name> - creates spec in inbox
Evaluate feature <ID> - code review or comparison
Prioritise feature <name> - assigns ID, moves to backlog
| name | aigon-feature-now |
| description | Fast-track feature <name> - create + setup + implement in one step |
Fast-track a feature from idea to implementation in one step. Works in two modes:
01-inbox/), runs prioritise → setup (Drive) → implementIf no feature name is provided:
List all files in ./docs/specs/features/01-inbox/ matching feature-*.md.
Compare the provided name/slug against the inbox filenames (partial match is fine — e.g. "ralph" matches feature-ralph-wiggum.md).
If multiple inbox features match, present the matches and ask the user to pick one.
The feature already has a spec in the inbox. Prioritise it, set up Drive mode, and implement.
Before starting, explore the codebase to understand the existing architecture, patterns, and code relevant to this feature. Read the existing spec to understand what's planned.
aigon feature-prioritise <inbox-name>
This assigns an ID and prioritises the feature to backlog. Note the assigned ID from the output.
aigon feature-start <ID>
This records the in-progress lifecycle state, refreshes the generated view, creates the branch, and creates the implementation log.
Continue from Step 4: Implement below, using the assigned ID.
No inbox match — create from scratch using the CLI.
Before running the command, explore the codebase to understand the existing architecture, patterns, and code relevant to this feature. Consider:
aigon feature-now $ARGUMENTS
This will:
03-in-progress/ with an assigned IDfeature-NN-slug)Note the feature ID and exact file paths from the output.
Read the exact spec path printed by the CLI (Spec: ...).
Do not guess the filename from the raw argument text; aigon feature-now slugifies names and may trim punctuation/spacing.
Rewrite the spec sections with content informed by your codebase exploration and the conversation context:
Commit the spec:
docs: write spec for feature NN
Continue from Step 4: Implement below.
Skip plan mode — implement directly.
Create tasks from the acceptance criteria to give the user visibility into progress.
Implement the feature according to the spec. Commit with conventional commits (feat:, fix:, chore:).
Generate a Manual Testing Checklist: re-read the spec Acceptance Criteria and write a numbered list of concrete, human-executable steps to verify each criterion. Present the checklist in your response before stopping.
Signal that implementation is complete:
aigon agent-status implementation-complete
Write and commit the log before calling aigon agent-status implementation-complete. Run aigon feature-do {{ARG1_SYNTAX}} once from the checkout where you implement — the CLI prints your mode.
./docs/specs/features/logs/feature-{{ARG1_SYNTAX}}-*-log.md targeting 200–400 words, then commit it.…-<agent>-… worktree folder): no log — do not create docs/specs/features/logs/ files. Go to Step 5 (aigon agent-status implementation-complete).Override defaults with "logging_level": "fleet-only" | "always" | "never" in .aigon/config.json (Codex inlines prompts from cwd at launch and follows the same rules).
Tell the user:
"Implementation complete — code is on the branch, ready for review. You can ask me to make changes, or close the feature when satisfied."
STAY in the session. The user may review and request changes. If they do, make the changes and commit. Do NOT run or suggest feature-close.
This implementation session is complete.