[Feature]: speckit-status - provide brief status report on project flow across all stages of development
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 65/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- python
- Área
- cli, developer-experience
Línea de trabajo
Look at the spec-kit CLI commands in the codebase, likely under a commands or cli module. Understand how spec states (specify, plan, tasks, implement) are tracked. The new command should read this state and output a structured checklist. Start by running existing commands like /speckit-specify to see their output and state storage. Check for existing tests for CLI commands to follow the pattern.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem Statement
I do some work with spec-kit, maybe run /speckit-specify, then /speckit-plan, but then leave the session. Later I come back and don't remember where I left off. It would be great to quickly get a status to know where to start next. This should be defined so other agents doing automation of spec-kit can consume and learn where to resume work.
Proposed Solution
I would imagine a nice checklist, perhaps with hierarchy of multiple "specs" and their list of phases or stages and which have been completed with a [X] and not completed with a [ ] preceding each line.
- Constitution created
- 001-feature-a
- Spec
- Plan
- Tasks
- Implement
Alternatives Considered
Internet research says there are other extensions that do this, but this should be native with spec-kit, it is the one that owns the process and all state, so should provide it and should be AI-consumption first, not human first.
Component
Specify CLI (initialization, commands)
AI Agent (if applicable)
None
Use Cases
Human teams or Agentic systems doing work with spec-kit where work sessions stop and start across days or hours and status where left off needs to be checked to determine next steps to resume work.
Acceptance Criteria
No response
Additional Context
No response
AI Disclosure
N/A
- Lenguaje dominante
- Python
- Estrellas
- 138k
- Forks
- 12.4k
- Merge medio
- 3 d 2 h
- PR fusionados (30 d)
- 169
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/spec-kit
-
enhancement needs-triage triage-can-wait
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
preset-submission triage-must-have validation-passed
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
extension-submission triage-must-have validation-passed
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
extension-submission triage-can-wait validation-passed
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
[Feature]: 给 slug 添加默认值 Abiertoenhancement needs-triage triage-can-wait
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Todos los issues de github/spec-kit
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
stephrobert/dsoxlab#238 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
sublimehq/package_control#1780 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
nwg-piotr/nwg-displays#145 ·