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

Aberta Para iniciantes
  • Algo errado?
#5,422 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
68/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
github, python
Domínio
release, tooling

Direção de pesquisa

Leia a entrada proposta do catálogo e compare-a com a entrada existente do catálogo do Spec Kit para o SpecKit Companion, especialmente com a entrada v0.26.0 referenciada na issue #5324. Atualize os metadados do catálogo para v0.27.0 e remova a tag living-specs, que foi desativada; verifique se a entrada corresponde ao manifesto e aos detalhes da release informados na issue.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Extension ID

companion

Extension Name

SpecKit Companion

Version

0.27.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.27.0/companion-0.27.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

19

Number of Hooks (optional)

10

Tags

vscode, progress, hooks

Key Features
  • Hands-off runs on Spec Kit's workflow engine — specify workflow run speckit-companion routes on the recorded size, and each review gate resumes headless
  • Hands-off runs cost less — fewer bookkeeping calls and fewer instructions, closing the gap to stock on harder work
  • Size is decided before the spec — a change you understand, with nothing risky in it, goes straight to implement
  • A test task for every requirement — each is checked through the screen or API in the condition it names
  • Corner cuts recorded as concerns — a skipped test, a suppression, an empty stub or a lower coverage bar is kept with its file and line, never blocking
  • Specs finish at Completed — a run no longer stops at Implemented when converge adds work
  • Living specs retired — each change keeps one folder, and doctor flags leftover living-spec settings
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.4.1.dev0.

  • Upgraded a project to v0.27.0 from the published release zip; the retired living-spec skills were removed.
  • Ran a real feature hands-off with Claude Code in a terminal (auto on "starred todos"): it was sized simple and ended completed in one session, 25 turns, with a clean run record.
  • The extension's own suite passes (Python unit tests and shape parity).
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 on Spec Kit's workflow engine, with review gates
specify workflow run speckit-companion --input spec="Add a dark mode toggle"

# 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.27.0",
    "download_url": "https://github.com/alfredoperez/speckit-companion/releases/download/speckit-ext-v0.27.0/companion-0.27.0.zip",
    "sha256": "e8e2a62a55e030ec261ee5e3d475effb1b869a4f7abba5b4cd7e155f2133615b",
    "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": 19,
      "hooks": 10
    },
    "tags": [
      "vscode",
      "progress",
      "hooks"
    ],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-06-11T00:00:00Z",
    "updated_at": "2026-11-13T00:00:00Z"
  }
}
Additional Context

Update from v0.26.0 (#5324) to v0.27.0. Living specs are retired in this release, so the tags follow the manifest and drop living-specs.

Linguagem predominante
Python
Estrelas
149k
Forks
13.4k
Merge médio
1d 5h
PRs com merge (30d)
223

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de github/spec-kit

Todas as issues de github/spec-kit

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.