speckit.companion.mark-complete — Claude Code command: mark spec done
speckit.companion.mark-complete marks the active spec as completed via write-context.py. Handy when you want to close a spec by hand instead of running a full converge.
MIT ★ 110 updated 2026-11-03
.claude/commands/speckit.companion.mark-complete.mdWhat speckit.companion.mark-complete does
The command runs python3 .specify/extensions/companion/scripts/write-context.py --mark-complete --by ai from the repository root. That writes the completed status into the active spec's context. A clean converge already does this after implementation, so the command exists for manual marking.
It needs python3 on PATH. If the interpreter is absent, the command reports that the spec was not marked and keeps going. Nothing breaks, but the status stays unchanged.
Installation is a file placement. For Claude Code, put it at .claude/commands/speckit.companion.mark-complete.md. Codex uses ~/.codex/prompts/speckit.companion.mark-complete.md.
What it helps with
- mark a spec completed without another converge
- write the completed status to the active spec context
- close a spec right after implementation
- sync state after manual edits
Example prompts for the agent
- /speckit.companion.mark-complete
- Mark the spec completed with
/speckit.companion.mark-complete
How to install speckit.companion.mark-complete
Manually: put the files in place
.claude/commands/speckit.companion.mark-complete.mdCall it with /speckit.companion.mark-complete. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/speckit.companion.mark-complete.mdCall it with /prompts:speckit.companion.mark-complete. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/speckit.companion.mark-complete.prompt.mdManually: put the files in place
.gemini/commands/speckit.companion.mark-complete.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about speckit.companion.mark-complete
How do I install speckit.companion.mark-complete in Claude Code?
Place the command file at .claude/commands/speckit.companion.mark-complete.md inside your project repository. It then becomes available as /speckit.companion.mark-complete.
What does this command do?
It runs write-context.py with the --mark-complete flag to write the completed status into the active spec's context. A clean converge normally does this itself, so the command covers manual marking.
What happens if python3 is missing?
The command says the spec was not marked and carries on. The status stays unchanged, so you'll want python3 installed beforehand.
Source text
speckit.companion.mark-complete.md · MIT
--- description: "Mark the active spec completed by hand (writes status: completed)" --- # Mark Spec Complete Run this from the repository root to mark a spec that finished implement as completed (a clean converge already does it on its own); if `python3` is missing, say the spec was not marked and carry on. ```bash python3 .specify/extensions/companion/scripts/write-context.py --mark-complete --by ai ```
© alfredoperez · MIT · alfredoperez/speckit-companion