features — Claude Code command: build a user-POV feature map
Seeds and maintains a feature map written from the user's point of view in .flow/features/, committed alongside the code.
MIT ★ 730 updated 2026-10-29
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-nextWhat features does
Type /features and the project gets a map of what the product does for the person using it. Entries sit in .flow/features/ and are committed with the repo. The command stays manual: disable-model-invocation: true stops the model from calling it by itself.
There is little inside the command. It forwards its arguments to the flow-next-features skill word for word, and that skill does the rest: it detects the mode, handles an autonomy refusal, and prints a FEATURES_VERDICT= line at the end. Pass --init and the map is rebuilt even when one already exists.
Copying the command file by itself gets you nowhere, since every step runs in the skill. Install the flow-next plugin instead. On Codex the command file goes to ~/.codex/prompts/features.md.
What it helps with
- seed a feature map for a fresh repository
- bring the map up to date after a large rework
- rebuild the map from scratch with
--init - keep a user-facing feature list under version control
- capture a
FEATURES_VERDICT=line at the end of a run
Example prompts for the agent
- Run
/featuresto draft a user-facing feature map in.flow/features/. /features --init— start the map over from the current code.- Run
/featuresagain once the new screen ships and update the map.
How to install features
1Plugin marketplace
/plugin marketplace add gmickel/flow-next/plugin install flow-next@flow-next2Manually: put the files in place
.claude/commands/features.mdCall it with /features. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/features.mdCall it with /prompts:features. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/features.prompt.mdManually: put the files in place
.gemini/commands/features.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about features
How do I install features in Claude Code?
Add the marketplace with /plugin marketplace add gmickel/flow-next, then run /plugin install flow-next@flow-next. The command file lands at .claude/commands/features.md.
What does the features command do?
It seeds or maintains the user-POV feature map in .flow/features/, and those files are committed with the project.
Does features run without the flow-next plugin?
No. The command only passes its arguments to the flow-next-features skill, which performs the mode detection and writes the map. Install flow-next to get that skill.
Source text
features.md · MIT
--- name: features description: Seed or maintain the committed user-POV feature map at `.flow/features/` argument-hint: "[--init]" disable-model-invocation: true --- # IMPORTANT: This command MUST invoke the skill `flow-next-features` The ONLY purpose of this command is to call the `flow-next-features` skill. You MUST use that skill now. **Arguments:** $ARGUMENTS Pass the arguments to the skill verbatim. The skill handles autonomy refusal, state-resolved mode detection (seed when `.flow/features/` is absent or `--init` is passed; maintain when the map is present), seed/maintain execution, and the terminal `FEATURES_VERDICT=` line.
© Gordon Mickel · MIT · gmickel/flow-next