Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/8BitTacoSupreme/flowstate/llms.txt

Use this file to discover all available pages before exploring further.

flowstate run prints the native Claude Code session command for executing a specific GSD phase. It does not execute the phase directly — GSD slash commands only work inside active Claude Code sessions, so flowstate run gives you the exact command to paste into your terminal. It shares the same underlying launch_command() function as flowstate launch gsd <phase> but displays a different header.

​
Synopsis

flowstate run <phase> [OPTIONS]

​
Arguments

​
phase
integer
required
The GSD phase number to run (e.g. 1, 2, 3). Corresponds to a phase defined in .planning/ROADMAP.md.

​
Options

​
--dry-run
flag
Simulate execution. The command is printed as usual, but the underlying state is flagged as dry-run mode.
​
--root PATH
string
default:"."
Project root directory. Used when resolving the absolute path printed in the launch command.
​
--model TEXT
string
Claude model preference, stored in state for subsequent pipeline calls (e.g. sonnet, opus, haiku).
​
--budget FLOAT
number
Maximum spend per bridge call in USD. Stored in state preferences.
​
--effort TEXT
string
Effort level hint for the claude CLI (e.g. low, medium, high). Stored in state preferences.

​
How it works

flowstate run <phase> calls the same launch_command("gsd", phase, root) function as flowstate launch gsd <phase>. The printed command always follows this pattern: 
cd /absolute/path/to/project && claude
  → /gsd:plan-phase <phase>
Copy the output, run the cd ... && claude portion in your terminal, and then type the /gsd:plan-phase <phase> slash command when the Claude Code session opens.

​
Example

Print the command for Phase 1: 
flowstate run 1

Phase 1 — Native Execution

GSD phases run natively inside Claude Code sessions.
Use the following command:

  cd /path/to/project && claude
  → /gsd:plan-phase 1
Print the Phase 2 command from a different project root: 
flowstate run 2 --root ~/projects/my-app

​
Notes

  • flowstate run <phase> and flowstate launch gsd <phase> both call the same underlying launch_command("gsd", phase, root) function but display different headers. Prefer flowstate launch gsd <phase> when also working with research and strategy launch commands.
  • GSD must be installed with its skills available in your Claude Code environment. See flowstate status to check tool detection.
  • State preferences passed via --model, --budget, and --effort are persisted to flowstate.json and will be used on the next flowstate init run.

Build docs developers (and LLMs) love

Get started for freeTalk to us