Repository navigation
[Feature]: speckit-status - provide brief status report on project flow across all stages of development #4705
Description
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
Activity
[-][Feature]: spec-kit-status - provide brief status report on project flow across all stages of development[/-][+][Feature]: speckit-status - provide brief status report on project flow across all stages of development[/+]mnriem commentedon Sep 23, 2026
Thanks for the proposal. Spec Kit’s workflow is operator-directed: the operator chooses and invokes each command. There is no standing requirement for an agent to read a project-wide status report or decide what to run next. The proposed checklist is therefore a way for the operator to see where work stands.
The community Status Report extension already provides a view across features, task progress, and a suggested next action. Could you clarify what the operator cannot get from that report? A concrete example of the missing information would help us assess the request without assuming that status reporting must be built into core.