GitHub 火线榜

GitHub 火线榜 · 仓库档案

alfredoperez/speckit-companion

VS Code extension for spec-driven development — manage specs, workflows, and steering docs for AI CLI tools (Claude Code, Gemini CLI, Copilot CLI) (简介来自仓库自身文档。)

HTML#ai-tools#claude-code#developer-tools

数据截至 10月30日alfredoperez

最好成绩

#291

被忽视榜 · 活跃却无人问津

100

累计 Star

26

Fork 总数

1

近 30 天在榜天数

许可证: MIT最近 push: 10月19日Open Issues(含 PR): 3自 2026-10-25 起采集;未知 = 尚未采集到

项目文档

SpecKit Companion

Build Status VS Code GitHub Release License

SpecKit Companion is a VS Code extension for developers who build with an AI assistant and Spec Kit. It lists every spec in your project, opens each one as a page you can read and comment on, follows a run while it happens, and keeps a record of what the AI did and why. Your specs stay plain markdown in your repo, with the run record in a file beside each one, so nothing passes through a server of ours.

A guided tour of the Overview: the one sentence the run answers to, per-phase timing, the approach and the corner of the codebase it changed, how the change was sized, the living specs it loaded before drafting, the expectations fence, each verified check with the command it ran, decisions with the alternatives they rejected, and the requirement to task to test coverage table

Install

Search for SpecKit Companion in the Extensions view, or run:

code --install-extension alfredoperez.speckit-companion

It's on Open VSX too.

The Spec Kit extension (optional)

This second install runs inside Spec Kit and records each run, which is what the Overview above, the Resume button and living specs are built from. Add it from your project root:

specify extension add companion --from https://github.com/alfredoperez/speckit-companion/releases/download/companion-latest/companion.zip --force

That command needs a Spec Kit CLI that has extensions. The install page has the full walkthrough and what to do when a step fails.

First run

  1. Open your project folder in VS Code.
  2. Click the SpecKit icon in the activity bar.
  3. Pick your AI assistant when it asks.
  4. Click + in the Specs view, or run SpecKit: New Spec from the command palette, and describe what you want built.

The Quickstart follows one spec from there to done.

What you get

  • A sidebar for every spec. Specs are grouped by where they stand, with the status of each document and the assistant each one was last sent to. Viewer and sidebar

    The Specs sidebar: specs grouped by lifecycle with per-document progress marks, filter and sort, and the living-specs and steering views beneath

  • Specs you can read. Requirements are labeled rows, acceptance scenarios read as Given, When, Then, and tasks sit under their phases.

    A spec rendered as a structured page: title-leading header, requirements as labeled rows, the pipeline rail, and on-page navigation

  • A plan that draws itself. Call paths, a lifecycle, a screen and annotated code each draw as a card in the plan. Plan blocks

    A Call paths card in a plan: the functions a change reaches drawn as a tree, each row with its file and line

  • Review comments on any line. Comment on a spec the way you review a pull request, then click Refine and your assistant edits the spec from your comments. Review with comments

    Inline review comments on a spec: two pending comments and one already applied, each pinned under the line it annotates

  • A run you can watch. One button always offers the next step, tasks tick over while implement runs, and the finished run opens on its Overview. The steps and the Overview

    A run moving through the pipeline: the rail unlocks phase by phase, the next-step button follows it, tasks tick over live during implement, and the run overview lands with per-phase timing

  • A pipeline you can change. The Workflow Builder draws the steps your project runs and lets you attach your own work before or after any of them. Workflow Builder

    The Workflow Builder board: the specify, plan, tasks and implement steps as four columns, each with its phases and nodes, and the hooks this project attached listed under before and after with a companion.yml mark.

Also in the extension: living specs that stay current per capability, panes for bugs and ideas, and custom workflows.

Supported assistants

Companion sends each step to the assistant you choose: a CLI in a terminal, such as Claude Code, Gemini CLI, GitHub Copilot CLI or Codex CLI, or the chat panel of your editor. The full list is under Settings.

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
Spec Kit The engine half: records each step so every surface can show progress and resume. Install
GitHub Copilot app A live spec board in the app's side panel. Copilot app
Claude Code The followed spec's run above your prompt and in a pane. Claude Code

Docs

The docs live at speckit-companion.dev/docs, with commands and settings in the reference. In this repo: Contributing and the Changelog.

Telemetry

The extension sends anonymous usage telemetry, never prompt content, paths or names, and sends nothing when speckit.telemetry or VS Code's own telemetry setting is off. Details: Telemetry.

Support and credits

SpecKit Companion is free and open source. If it saves you time, you can support it through GitHub Sponsors. It started from kiro-for-cc.

License

MIT

当前上榜

  • 291

    被忽视榜 · 活跃却无人问津

    100 星 · 26 fork · 累计 Star(升序)

    被忽视 →

近 30 天势头

累计 Star 走势

名次走势

把上榜徽章放进你的 README · alfredoperez/speckit-companion[![把上榜徽章放进你的 README](https://git.vaiox.xyz/api/badge/alfredoperez/speckit-companion.svg)](https://git.vaiox.xyz/zh/repo/alfredoperez/speckit-companion)

Badge · 任何仓库都可以挂 —— 未上榜的仓库显示灰章,上完榜会自动点亮。

<a href="https://git.vaiox.xyz/zh/repo/alfredoperez/speckit-companion"><img src="https://git.vaiox.xyz/api/badge/alfredoperez/speckit-companion.svg" alt="把上榜徽章放进你的 README" height="20"></a>

← 回到榜单

GitHub 火线榜往日榜发现联系我们 · Contact