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

Abierto Apto para principiantes
  • ¿Algo no está bien?
#5,422 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
68/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, python
Área
release, tooling

Línea de trabajo

Lee la entrada propuesta del catálogo y compárala con la entrada existente del catálogo de Spec Kit para SpecKit Companion, especialmente con la entrada v0.26.0 a la que hace referencia el issue #5324. Actualiza los metadatos del catálogo a v0.27.0 y elimina la etiqueta retirada living-specs; verifica que la entrada coincida con el manifiesto y los detalles de la release del issue.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
149k
Forks
13.4k
Merge medio
1 d 5 h
PR fusionados (30 d)
223

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/spec-kit

Todos los issues de github/spec-kit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.