Skip to main content
command CX Codex

speckit.companion.after-implement — Claude Code command: what it does

speckit.companion.after-implement — a command that writes implement step progress from tasks.md into .spec-context.json for the Companion GUI.

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-implement.md
Open on GitHub

What speckit.companion.after-implement does

The command runs a Python script, write-context.py, which syncs task completion status from tasks.md into .spec-context.json. This lets Speckit Companion GUI display progress.

The script lives in .specify/extensions/companion/scripts/. If python3 is not in PATH, the command reports the step was not recorded and continues without error.

Run the command from the repository root after finishing the implement step — the agent logs that tasks are complete and updates context for the GUI.

What it helps with

  • sync task progress from tasks.md into a context file
  • update implement step status for the Companion interface
  • record completion state without halting if Python is missing

Example prompts for the agent

  • Record that implement is finished
  • Update .spec-context.json after implement
  • Log task progress to context

How to install speckit.companion.after-implement

Manually: put the files in place

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

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

Questions about speckit.companion.after-implement

How to install speckit.companion.after-implement in Claude Code?

Place the command file at .claude/commands/speckit.companion.after-implement.md in the repository root.

What does speckit.companion.after-implement do?

The command runs a script that writes implement step status from tasks.md into .spec-context.json for display in Speckit Companion GUI.

What happens if python3 is not installed?

The command reports the step was not recorded and continues without error — the script does not stop the agent.

Source text

speckit.companion.after-implement.md · MIT
---
description: "Record implement progress from tasks.md in .spec-context.json for the Companion GUI"
---

# Capture Implement Finish

Run this from the repository root to sync implement progress from tasks.md; 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 implement
```

© 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-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-specify 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. 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 bench-sync bench-sync — a command for Claude Code and Codex that bakes benchmark cells and measures the current spec-kit and Companion extension versions. Use it to track how performance changes as tools are updated. CX Codex +1 ★ 110repo stars

Project sponsors

Companies that keep this analytics open