name: feater description: Small feature implementation (1-5 files). Light planning, direct implementation, no heavy orchestration. No design brainstorm, no subagents, no plugin check gate.
Implement a small, well-scoped feature without the overhead of a full orchestrator. Direct work, light planning, quick delivery.
$ARGUMENTS
Before starting, verify this is actually a small feature:
git status
git log --oneline -3
Read the relevant existing code to understand the context.
Escalate to /ship-feature if:
Downgrade — load $HOME/.claude/agents/hotfixer.md if:
Print a one-line scope confirmation:
FEAT: <feature name> — ~<N> files, <brief approach>
Follow $HOME/.claude/lib/design-gate.md:
ui-ux-pro-max inactive → ask user to activate.Quick mental model, not a formal plan document:
Print the plan as a compact checklist:
PLAN:
[ ] <file> — <what to do>
[ ] <file> — <what to do>
[ ] <test file> — <test to add>
No gate — proceed directly unless the approach is ambiguous. If ambiguous: ask the user one focused question, then proceed.
Work through the plan:
Run the full relevant test suite:
# detect and run tests, lint, type-check
If a dev server is relevant, mention what the user should check visually.
Quick self-review: scan your diff for obvious issues:
git diff --stat
git diff
Commit using conventional format:
feat(<scope>): <what was added>
<brief description of the feature>
Co-Authored-By: Claude <noreply@anthropic.com>
If the feature touched multiple concerns (e.g., feature + config +
test), consider splitting into 2-3 atomic commits — load
$HOME/.claude/agents/commit-changer.md and follow its grouping logic.
Print summary:
FEAT COMPLETE
FEATURE : <name>
FILE(S) : <created/modified files>
TEST(S) : <added tests>
VERIFIED : <what was checked>
Load $HOME/.claude/agents/doc-syncer.md.
Execute in automatic mode:
auto-mode scope: <list of files modified during this session>
A small feature may or may not involve a design choice. Scan the work for:
BDR-XXX in .claude/memory/decisions.md with alternatives considered.LRN-XXX in .claude/memory/learnings.md.Present the candidates grouped:
CAPITALIZE — proposé
[decisions.md] BDR-XXX — <titre> (optionnel)
[learnings.md] LRN-XXX — <pattern> (optionnel)
Valider ? (all / <IDs> / edit / skip)
Always append a 1-line entry to today's heading in .claude/memory/journal.md.
If no substantive capture candidate → skip with CAPITALIZE: rien à logger.
/ship-feature./ship-feature)./feat + follow-up task.