원클릭으로
aigon-feature-now
Fast-track feature <name> - create + setup + implement in one step
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Fast-track feature <name> - create + setup + implement in one step
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Record or show a feature author handoff
Create feature <name> - creates spec in inbox
Revise feature spec after pending spec reviews — decide and acknowledge in one pass
Record or show a research author handoff
Create research <name> - creates topic in inbox
Revise research spec after pending spec reviews — decide and acknowledge in one pass
| 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:).
Signal that implementation is complete:
aigon agent-status implementation-complete
No implementation log (instructions rigor: light). Do not create docs/specs/features/logs/feature-{{ARG1_SYNTAX}}-*-log.md.
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.