[Feature]: speckit-status - provide brief status report on project flow across all stages of development
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Facilidade para iniciantes
- 65/100
- Tipo de issue
- Funcionalidade
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- python
- Domínio
- cli, developer-experience
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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
- Linguagem predominante
- Python
- Estrelas
- 138k
- Forks
- 12.4k
- Merge médio
- 3d 2h
- PRs com merge (30d)
- 169
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de github/spec-kit
-
enhancement needs-triage triage-can-wait
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
-
preset-submission triage-must-have validation-passed
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
-
extension-submission triage-must-have validation-passed
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
-
extension-submission triage-can-wait validation-passed
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
-
[Feature]: 给 slug 添加默认值 Abertaenhancement needs-triage triage-can-wait
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
Todas as issues de github/spec-kit
Issues semelhantes
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
stephrobert/dsoxlab#238 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
sublimehq/package_control#1780 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
nwg-piotr/nwg-displays#145 ·