Skip to main content
command CX Codex

speckit.companion.after-specify — Claude Code and Codex command

speckit.companion.after-specify — a command for Claude Code and Codex that writes the current spec-kit step to .spec-context.json for the Companion GUI. Runs from the repository root after the specify stage completes.

MIT ★ 110 updated 2026-11-03

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/speckit.companion.after-specify.md
Open on GitHub

What speckit.companion.after-specify does

The command executes the Python script write-context.py with parameters --hook finish --step specify. If Python 3 is not available, the step is not recorded, but execution continues without interruption.

Use it in spec-kit workflows where you need to preserve state between development phases. The .spec-context.json file acts as memory for the Companion GUI, letting it track progress and project context across steps.

What it helps with

  • record the completion of the specify stage in context
  • sync spec-kit state with Companion GUI
  • preserve the current development step for subsequent commands

Example prompts for the agent

  • After finishing the specification step, run speckit.companion.after-specify from the repository root
  • Execute the command to mark the transition from specify to the next phase
  • Use it in automation after each spec-kit block completes

How to install speckit.companion.after-specify

Manually: put the files in place

.claude/commands/speckit.companion.after-specify.md

Call it with /speckit.companion.after-specify. For all projects use ~/.claude/commands/

Questions about speckit.companion.after-specify

How do I install speckit.companion.after-specify in Claude Code?

Create the file .claude/commands/speckit.companion.after-specify.md in your project root with the command description and path to the script.

What does speckit.companion.after-specify do?

It writes the current spec-kit step (finish/specify) to .spec-context.json, which Companion GUI uses to track progress through the workflow.

What happens if Python 3 is not installed?

The command skips recording the step but does not fail; you can proceed without errors.

Source text

speckit.companion.after-specify.md · MIT
---
description: "Capture the current spec-kit step into .spec-context.json for the Companion GUI"
---

# Capture Specify Finish

Run this from the repository root to record that specify finished; if `python3` is missing, say the step was not recorded and carry on.

```bash
python3 .specify/extensions/companion/scripts/write-context.py --hook finish --step specify
```

© alfredoperez · MIT · alfredoperez/speckit-companion

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set83

The whole set →
speckit.companion.classify speckit.companion.classify evaluates task scope from spec.md to classify changes as simple, normal, or oversized. Companion workflows use this signal to adapt the execution pipeline. CX Codex +1 ★ 110repo stars speckit-git-validate speckit-git-validate is a Claude Code skill that checks the current Git branch name and searches specs/ for its matching spec folder in spec-kit projects. CX Codex +1 ★ 110repo stars speckit.companion.after-plan speckit.companion.after-plan writes a plan finish marker to .spec-context.json for the Companion GUI to track agent workflow stages. CX Codex +1 ★ 110repo stars speckit.companion.after-converge speckit.companion.after-converge logs converge completion into .spec-context.json for Companion GUI. It tells the companion interface that the step finished. CX Codex +1 ★ 110repo stars speckit.companion.after-implement speckit.companion.after-implement — a command that writes implement step progress from tasks.md into .spec-context.json for the Companion GUI. CX Codex +1 ★ 110repo stars speckit.companion.after-tasks speckit.companion.after-tasks records task completion in .spec-context.json for Companion GUI. Intended to run from the repository root right after completing tasks. CX Codex +1 ★ 110repo stars speckit.companion.before-step The speckit.companion.before-step command records a spec-kit step’s start in .spec-context.json for the Companion GUI. Run it before specify, plan, tasks, or implement. CX Codex +1 ★ 110repo stars speckit.companion.living-coverage speckit.companion.living-coverage — a command that reports which living-spec requirements have mapped tests and which remain uncovered. It runs read-only and never halts your workflow. CX Codex +1 ★ 110repo stars

Project sponsors

Companies that keep this analytics open