speckit-companion · alfredoperez, copilot-canvas — GitHub Copilot plugin: install
The speckit-companion GitHub Copilot plugin displays Spec Kit progress for each project spec. Open its documents or start the next stage from the board beside the chat.
MIT ★ 110 updated 2026-10-19
copilot plugin install speckit-companion@awesome-copilotWhat speckit-companion does
The plugin puts a live spec board beside the chat. Each entry shows the specify, plan, tasks and implement stages, its documents, task progress and run history. A button sends the next stage’s command to the chat, and the board refreshes as the agent works.
It supports stock Spec Kit and SpecKit Companion, and does not require VS Code. The board leaves spec documents untouched. In a stock project, it records the start and finish of each step in .spec-context.json; its own run instructions go under .speckit-companion/prompts/. Each new Copilot session starts in a fresh worktree without node_modules, so an implement step that runs tests installs dependencies first.
The board may get clipped after the panel is narrowed. Close and reopen the canvas to restore its layout.
What it helps with
- track each repository spec through its pipeline
- read a spec’s documents beside the chat
- start the next pipeline stage from its card
- view task progress and run history
Example prompts for the agent
- Open the SpecKit Companion board in a new Copilot session.
- Show the documents and current stage for this spec.
- Start the next stage for this spec.
How to install speckit-companion
Command from the source
copilot plugin install speckit-companion@awesome-copilotStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about speckit-companion
How do I install speckit-companion in GitHub Copilot?
Run copilot plugin install speckit-companion@awesome-copilot.
What does speckit-companion do?
It displays a Spec Kit board with each spec’s documents, pipeline stages, task progress and run history. A card button sends the next stage’s command into chat.
What does speckit-companion need to run?
It needs the GitHub Copilot app and a project using stock Spec Kit or SpecKit Companion. VS Code is not required.
Source text
copilot-canvas · MIT
# SpecKit Companion spec board for the GitHub Copilot app A live board of every spec in your repo, next to the chat in the GitHub Copilot app. It's for people who run [Spec Kit](https://github.com/github/spec-kit) with Copilot: you see where each spec stands, read its documents, and run the next step from a button. It works with stock Spec Kit and with [SpecKit Companion](https://speckit-companion.dev), and you don't need VS Code. The clip below is a recreation of one run, sped up. The board is the real one, and the window and chat around it stand in for the Copilot app.  ## Install The board is a [canvas extension](https://docs.github.com/en/copilot/how-tos/github-copilot-app/working-with-canvas-extensions). Copy this folder into your user folder and it shows up in every new session: ```bash git clone https://github.com/alfredoperez/speckit-companion cp -R speckit-companion/apps/copilot-canvas/com.github.copilot/extensions/speckit-companion ~/.copilot/extensions/speckit-companion ``` ## First run Open your project in the Copilot app, start a **new** session, and ask: **Open the SpecKit Companion canvas**. It's also in the session's **+** menu, under **Canvas** → **SpecKit Companion**. Open a spec to read its documents, and press the button on the card under the pipeline to run the next step. The button sends one command into the chat, and the board updates as the agent writes.  ## Share it with your team Copy the folder into the project and commit it: ```bash cp -R speckit-companion/apps/copilot-canvas/com.github.copilot/extensions/speckit-companion <project>/.github/extensions/speckit-companion ``` A project copy is code, so the app keeps it off until you accept it. Since Copilot app 1.1.26: 1. Merge the copy to your default branch. 2. Choose **Review repository content** on the notice the app shows, then **Accept for new sessions**. 3. Start a new session and open the canvas. A session that was open when you accepted never gets the board. After any change under `.github/extensions/`, new sessions lose it until you accept again. ## What the board writes The board never writes a spec document. It writes two things: - Its own run instructions under `.speckit-companion/prompts/`, with a `.gitignore` beside them so they stay out of your commits. - In a stock project, the start and finish of each step it sent, in the spec's `.spec-context.json`. Where Companion is installed the board does not write that file. The commands it sends do. ## Known limits - **The board is clipped after you narrow the panel.** The Copilot app does not resize the panel's page, so the board can't reflow. Close the canvas and open it again after resizing. - **Each session runs in a fresh worktree** cut from your default branch. It has no `node_modules`, so an implement step that runs tests installs the dependencies first. Companion's commands have to be committed files too, not symlinks from a `--dev` install. <!-- other-products:start --> ## SpecKit Companion runs in four places | Where | What it is | Start here | |---|---|---| | VS Code | The extension: a sidebar, a spec viewer and the Overview of every run. | [Install](https://speckit-companion.dev/docs/install) | | Spec Kit | The engine half: records each step so every surface can show progress and resume. | [Install](https://speckit-companion.dev/docs/install) | | GitHub Copilot app | A live spec board in the app's side panel. | [Copilot app](https://speckit-companion.dev/docs/copilot-app) | | Claude Code | The followed spec's run above your prompt and in a pane. | [Claude Code](https://speckit-companion.dev/docs/claude-code) | <!-- other-products:end --> ## Docs [Guide](https://speckit-companion.dev/docs/copilot-app) · [Changelog](https://speckit-companion.dev/changelog/) · [Develop](https://github.com/alfredoperez/speckit-companion/blob/main/apps/copilot-canvas/docs/develop.md) · MIT licensed.
© Alfredo Perez · MIT · alfredoperez/speckit-companion
Similar plugins
All plugins for Agent setup: memory, context, orchestration →speckit-companion by other authors comes first.