SpecKit Companion plugin
A VS Code extension for Spec Kit that renders specs as pages, follows each run and keeps a record of the assistant's decisions.
- 105 ★ on the repository
- Last commit
Extended access
Why this level
- Runs the chosen assistant through terminal commands, and the assistant edits project files.
- Sends anonymous telemetry until it is switched off.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/speckit-companionDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs the chosen assistant through terminal commands, and the assistant edits project files.
- Sends anonymous telemetry until it is switched off.
This is third-party code. Review the repository files before installing.
What it does
SpecKit Companion, a VS Code extension for building with Spec Kit and an AI assistant, groups project specs in a sidebar by stage. Each spec opens as a page with requirements, Given-When-Then scenarios and tasks. Line comments work like a pull request review, and the Refine button sends them to the assistant for edits. During `implement` tasks tick over live, and a finished run opens an overview with phase timing, decisions and requirement-to-test coverage. Steps go to the assistant you choose: Claude Code, Gemini CLI, GitHub Copilot CLI, Codex CLI or the editor chat. Specs stay as markdown files in your repository.
Who it is for. Developers on Spec Kit who juggle several specs in VS Code and want to see the assistant's progress instead of a terminal log.
Good fit when
- A project has several specs and you want a list with the status of each document.
- A spec is reviewed with line comments and the assistant edits the text from them.
- An `implement` run takes long and you want to watch the tasks on screen.
- After the assistant finishes you need to see which decisions it made and which alternatives it rejected.
Not a fit when
- The project does not use Spec Kit: the extension is built around its pipeline.
- The editor is different and no separate version exists for your environment.
- Telemetry is not acceptable: the extension sends anonymous statistics, switched off with the `speckit.telemetry` setting.
Example request
Show the project specs grouped by stage and open the overview of the latest implement run.Limitations
The extension needs Spec Kit and the assistant you choose. Run recording, the resume button and living specs appear only after the second install, the Spec Kit extension `companion`, and its command needs a Spec Kit CLI that supports extensions. Anonymous telemetry contains no prompts, paths or names and is switched off with `speckit.telemetry` or VS Code telemetry. Request costs come from the chosen assistant; Companion pays for none of them.
How to disable. Remove the extension in the VS Code Extensions view. The Spec Kit extension `companion` is removed with the Spec Kit CLI, and run records next to the specs are deleted by hand.
FAQ
Where are run records stored?
Next to the spec in your repository. There is no separate server and specs stay plain markdown.
Which assistants work?
Claude Code, Gemini CLI, GitHub Copilot CLI, Codex CLI and the editor chat. The full list is in the extension settings.
Is the second install required?
The VS Code extension works without it. The run overview, the resume button and living specs are built from records made by the Spec Kit extension.
Which editors are supported?
The main version runs in VS Code and is also on Open VSX. Separate versions exist for the GitHub Copilot app and for Claude Code.
What does the Workflow Builder show?
The project pipeline steps as columns and your own tasks attached before or after any step.
Discussion
No questions or reviews yet.
Related
PluginsGitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Spec Kit skills for Claude Code, Codex, Cursor, Copilot and OpenCode: specify, plan, tasks, implement, baseline of existing code
Spec Kitty
spec-kitty
A CLI for spec-driven development: a chain of spec, plan, tasks, next, review, accept, merge. Version 4 is still a release candidate
A CLI, MCP server and skill for spec-driven development: short markdown specs, a task board and search that an agent can read.
A plugin with three skills for large development work: project analysis, phased tasks tracked as GitHub Issues, parallel agents and code review
A bridge hands tasks from Spec Kit to Superpowers discipline: Spec Kit writes what to build, Superpowers enforces how.
README in short
The README describes a VS Code extension and a Spec Kit add-on that records each step. It shows the sidebar, the spec page, plan blocks, comments and the pipeline builder. Four surfaces are listed: VS Code, Spec Kit, the GitHub Copilot app and Claude Code.