Invocation
/feature
/feature 3
/feature "team invitations"Use $feature for the same skill in Codex.
What happens
- Select the next unchecked build-plan item or the requested item.
- If a genuinely new capability does not match the plan, check for near-duplicates and propose a feature-sized plan addition.
- After you approve the plan change, update the build plan, update the project plan only when necessary, and refresh the project overview.
- Size the feature and split it if it contains independent outcomes.
- Write scope, exclusions, contracts, build steps, testing, and observable done-when criteria.
- Red-team the draft for missing paths, oversized steps, scope creep, and vague proof.
- Stop for review before application code changes.
Reads and writes
| Reads | Writes | Never does |
|---|---|---|
| Build plan, project overview, standards, prototypes | context/current-feature.md; plans and overview only for an approved new-feature addition |
Application code, commits, merges |
For an unplanned bug or small change, use /fix. New-feature intake is for a product capability that belongs on the living roadmap.
Visual features
If prototypes/ exists, the spec links the relevant mockups and makes porting the shared theme tokens the first implementation step. A visual target should not be reconstructed from prose when a real reference exists.