speckit.companion.status — Claude Code command: spec status
speckit.companion.status — a command for Claude Code and Codex reads .spec-context.json and reports the active spec’s step, status, decisions, and next action. It is read-only.
MIT ★ 110 updated 2026-11-10
.claude/commands/speckit.companion.status.mdWhat speckit.companion.status does
From the repository root, it calls python3 .specify/extensions/companion/scripts/status-context.py --plain and prints the script output as the status report.
The report covers the active spec’s current step, its status, recorded decisions, and the next action. Add --feature-dir specs/<NNN>-<slug> when a specific spec was named. The command skips the report when python3 is unavailable, so that runtime is required.
What it helps with
- check which step the active spec has reached
- read the spec status and recorded decisions
- see the next action for the current spec
- inspect a spec under
specs/<NNN>-<slug>
Example prompts for the agent
- Run
/speckit-companion-statusand show the active spec status. - Use
/speckit-companion-statusfor the spec inspecs/<NNN>-<slug>. - Report the current step, decisions, and next action for the active spec.
How to install speckit.companion.status
Manually: put the files in place
.claude/commands/speckit.companion.status.mdCall it with /speckit.companion.status. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/speckit.companion.status.mdCall it with /prompts:speckit.companion.status. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/speckit.companion.status.prompt.mdManually: put the files in place
.gemini/commands/speckit.companion.status.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about speckit.companion.status
How do I install speckit.companion.status in Claude Code?
Save the command file at .claude/commands/speckit.companion.status.md.
What does speckit.companion.status do?
It reads .spec-context.json through the companion status script and reports the current step, status, recorded decisions, and next action. The context file stays unchanged.
What does this command need to run?
Run it from the repository root with python3 available. Add --feature-dir specs/<NNN>-<slug> for a named spec. When python3 is missing, the status report is skipped.
Source text
speckit.companion.status.md · MIT
--- description: "Report where the active spec stands — current step, status, recorded decisions, and the next action — from .spec-context.json" --- # Spec Status Print where the active spec stands: the current step, its status, the decisions recorded so far, and the next action. A script reads the run record and writes the answer, so it reads the same every time. **Read-only**: this command never writes `.spec-context.json`. <!-- speckit-companion:part command-spelling --> ## Name every command the way this project registers it Commands are named in dot form throughout this body, `speckit.companion.plan`, because that is their canonical id, and without a leading slash, because the spelling a host actually registers is not always this one. Claude Code installs `/speckit-companion-plan`. Look at how the commands are installed in this project, under the agent's own commands or skills directory, and use that spelling every time you name one to the developer or dispatch one yourself. A dotted name typed into a host that registered dashes resolves to nothing at all. <!-- /speckit-companion:part command-spelling --> ## Execution Run this from the repository root and print its output exactly as it comes, in a code block. Add nothing: no summary, no reading of the record yourself, no next-step advice beyond what it prints. ```bash python3 .specify/extensions/companion/scripts/status-context.py --plain ``` Add `--feature-dir specs/<NNN>-<slug>` when the user named a spec. If `python3` is missing, print `[companion] python3 not found; status skipped.` and stop.
© alfredoperez · MIT · alfredoperez/speckit-companion