/neuroflow:phase¶
Show the current project phase and optionally switch to a different one.
/phase gives you a quick status overview — what phase you're in, what phases have been worked on, and when the last session was. It also lets you switch phase from a menu if you want to jump to a different part of the pipeline.
When to use it¶
- You want to quickly check where you are in the project
- You want to switch from one phase to another
- You're orienting yourself at the start of a session (though
/neuroflowdoes this too)
What it does¶
- Reads
project_config.mdto get the current active phase and the phases recommended at setup - Checks which phase subfolders exist in
.neuroflow/and when the last session was - Prints the phase map —
◉current,●visited,→recommended,○not started — followed by upcoming deadlines fromtimeline.md, a one-line living-paper status (only with/paper --autoon), any long runs not yet reviewed, and your personality mode - For the current phase, lists its expected inputs and outputs (
[x]present,[ ]missing — information only, never a gate) and the commands that usually come next - Asks whether to switch, as a menu: move with the arrow keys and press Enter, or click an option. "Stay in the current phase" comes first, then the next recommended phases; Other lets you type any phase.
- If you pick a different phase, it changes
active_phaseinproject_config.md— that one value — logs the switch, and suggests the new phase's command.
With the neuroflow mod active, the mod answers /neuroflow:phase itself: the same map with a picker that opens holding the keyboard, each phase by its name, marked ◉ ● → ○ as above, with its state in words — Down or Enter opens the list, the arrow keys move, a letter jumps to the phases that start with it, Enter switches after a yes and Esc closes (or a click) — and the switch is written by code. /neuroflow:phase data-analyze switches at once, with no picker. Without the mod, Claude asks the same question with Claude Code's question menu.
The switch never edits .claude/CLAUDE.md: its neuroflow block is static and points at project_config.md, so nothing goes stale.
Example session¶
Phase map — Last session: 2026-03-08
● ideation
● experiment
● data
◉ data-preprocess ← current
→ data-analyze ← recommended
→ paper ← recommended
○ preregistration
...
Personality mode: 🔍 Critic (critic, team default)
Next: /neuroflow:data-analyze
Switch phase?
▸ Stay in data-preprocess
data-analyze
paper
Other…
You: (arrow down, Enter) data-analyze
Claude: ✅ Active phase updated to: data-analyze
Run /neuroflow:data-analyze to continue.
Files read and written¶
| Direction | Files |
|---|---|
| Reads | .neuroflow/project_config.md, .neuroflow/flow.md, .neuroflow/sessions/, .neuroflow/timeline.md, .neuroflow/paper/ (only with /paper --auto on), .neuroflow/*/runs.md, ~/.neuroflow/user.yaml, ~/.neuroflow/local-projects.json (flowie sync) |
| Writes | only when you switch: active_phase in project_config.md, a session line, a reasoning/general.jsonl entry, and your flowie project registry (if linked); for a team project, the card in the hive after you confirm the push (with the mod, the picker puts /neuroflow:phase --sync in the prompt for this) |
Related commands¶
/neuroflow— full project status + session start/sentinel— audit project for consistency issues