[Extension]: Add SpecKit Companion v0.26.0 (catalog update)

Open Beginner friendly
  • Is something wrong?
#5,324 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github, python
Domain
release, tooling

Research direction

Find the extension catalog file that contains the existing SpecKit Companion entry and compare it with the proposed catalog entry in the issue. Update the entry to version 0.26.0 and verify the download URL, SHA-256, and metadata against the submission. Done when the catalog lists the submitted version and the repository’s catalog validation passes.

Written by the indexing model from the issue text.

Description

Extension ID

companion

Extension Name

SpecKit Companion

Version

0.26.0

Description

Records your spec-kit runs live: status, resume, and a health check for what actually happened.

Author

alfredoperez

Repository URL

https://github.com/alfredoperez/speckit-companion

Download URL

https://github.com/alfredoperez/speckit-companion/releases/download/speckit-ext-v0.26.0/companion-0.26.0.zip

License

MIT

Homepage (optional)

https://github.com/alfredoperez/speckit-companion/tree/main/apps/speckit-extension

Documentation URL (optional)

https://github.com/alfredoperez/speckit-companion/blob/main/apps/speckit-extension/README.md

Changelog URL (optional)

https://github.com/alfredoperez/speckit-companion/blob/main/apps/speckit-extension/CHANGELOG.md

Required Spec Kit Version

=1.2.5.dev0

Required Tools (optional)
- `python3` (optional)
Number of Commands

26

Number of Hooks (optional)

10

Tags

vscode, progress, living-specs, drift, hooks

Key Features
  • Every spec records what was proven — your request word for word, who made each decision, assumed and weakly tested requirements, the commit each check ran on, and a risk tier
  • Receipts for the pull request — each check is kept with its exit code, so a PR body can show what ran and what the agent only claimed
  • A clean converge completes the spec — converge records the tasks each pass added, and a pass that adds none finishes the spec
  • Works with stock Spec Kit 1.2.5 — new specs are spec.md, your template overrides and presets shape Companion runs, and plain /speckit.* commands stay exactly as shipped
  • Step times from the agent's own events — typing a step command records its start, and a step closes only when its document is really written
  • Safe in parallel and in monorepos — spec numbers are picked under a lock and follow feature_numbering, and the project is found the way Spec Kit finds it
  • The plan draws what a change touches — call paths, pinned code, states or screens are added only when the change needs them, and each is checked
  • Doctor and status — doctor flags missing Companion commands, a missing specify CLI and shared spec numbers; status prints where each spec stands
Testing Checklist
  • Extension installs successfully via download URL
  • All commands execute without errors
  • Documentation is complete and accurate
  • No security vulnerabilities identified
  • Tested on at least one real project
Submission Requirements
  • Valid extension.yml manifest included
  • README.md with installation and usage instructions
  • LICENSE file included
  • GitHub release created with version tag
  • All command files exist and are properly formatted
  • Extension ID follows naming conventions (lowercase-with-hyphens)
Testing Details

Tested on Darwin 27.0.0 with Spec Kit 1.3.2 (installed with uvx from the v1.3.2 tag).

  • Installed v0.26.0 from the release download into a fresh specify init --integration claude project; specify extension list shows SpecKit Companion v0.26.0.
  • Ran a real feature through specify, plan, tasks, implement and converge with Claude Code in a terminal (4m 30s) and from VS Code (7m 53s); both ended completed with a clean run record.
  • The extension's own suite passes (Python unit tests, shape parity, build check).
Example Usage
# Install (Spec Kit 1.2.5 or newer)
specify extension add companion --from https://github.com/alfredoperez/speckit-companion/releases/download/companion-latest/companion.zip

# Run the whole pipeline hands-off on a new feature
/speckit.companion.auto Add a dark mode toggle to settings that survives a reload

# Or step by step
/speckit.companion.specify Add a dark mode toggle to settings
/speckit.companion.plan
/speckit.companion.tasks
/speckit.companion.implement

# See where every spec stands, and check the install
/speckit.companion.status
/speckit.companion.doctor
Proposed Catalog Entry
{
  "companion": {
    "name": "SpecKit Companion",
    "id": "companion",
    "description": "Records your spec-kit runs live: status, resume, and a health check for what actually happened.",
    "author": "alfredoperez",
    "version": "0.26.0",
    "download_url": "https://github.com/alfredoperez/speckit-companion/releases/download/speckit-ext-v0.26.0/companion-0.26.0.zip",
    "sha256": "8bfbe27dbe2d67e525820f83340c053341836f108d2ff087c10fdc8295b07da9",
    "repository": "https://github.com/alfredoperez/speckit-companion",
    "homepage": "https://github.com/alfredoperez/speckit-companion/tree/main/apps/speckit-extension",
    "documentation": "https://github.com/alfredoperez/speckit-companion/blob/main/apps/speckit-extension/README.md",
    "changelog": "https://github.com/alfredoperez/speckit-companion/blob/main/apps/speckit-extension/CHANGELOG.md",
    "license": "MIT",
    "category": "process",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=1.2.5.dev0",
      "tools": [
        {
          "name": "python3",
          "required": false
        }
      ]
    },
    "provides": {
      "commands": 26,
      "hooks": 10
    },
    "tags": [
      "vscode",
      "progress",
      "living-specs",
      "drift",
      "hooks"
    ],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-06-11T00:00:00Z",
    "updated_at": "2026-11-09T00:00:00Z"
  }
}
Additional Context

Update from v0.24.0 (#4857) to v0.26.0. The extension now requires Spec Kit 1.2.5 or newer, the oldest CLI with every feature it uses.

Dominant language
Python
Stars
147k
Forks
13.2k
Avg merge
1d 6h
Merged PRs (30d)
199

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/spec-kit

All issues in github/spec-kit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.