| name | spec-flow:spec-status |
| description | Analyze current spec completion status and provide detailed progress report. Use when checking progress, identifying blockers, or planning what to work on next. More detailed than the /spec-flow:status command. |
| allowed-tools | Read, Glob |
Spec Status Analysis
Provide comprehensive project status based on spec and task files.
When Claude Should Use This Skill
- User asks "what's the status" or "how far along are we"
- User asks "what should I work on next"
- User asks "what's blocking progress"
- At the start of a new session to orient
- When resuming work after a break
Workflow
1. Gather Data
Read all spec files:
.claude/spec/SPEC.md
.claude/spec/tasks/*.md
.claude/steering/decisions.md (for recent context)
2. Calculate Metrics
Per Task File:
- Count tasks by status (Pending, In Progress, Complete, Blocked)
- Calculate completion percentage
- Identify blocked tasks and blockers
- Note in-progress tasks
Overall:
- Weight by milestone priority (MVP > v1.0 > later)
- Aggregate completion percentage
- Count total tasks across all milestones
3. Analyze Progress
Velocity indicators:
- Tasks completed in recent sessions (from git history or decisions.md)
- Average time per task (if tracked)
Risk indicators:
- Tasks blocked for extended time
- Milestones with 0% progress
- Tasks without clear acceptance criteria
Health indicators:
- Requirements without task coverage
- Tasks without file paths specified
- Overdue milestones (if ETAs set)
4. Generate Recommendations
What to work on next:
- In-progress tasks (finish what's started)
- Unblock blocked tasks (if possible)
- Highest priority pending task
What needs attention:
- Underspecified tasks
- Missing task files for milestones
- Requirements without coverage
5. Output Format
# Project Status: {name}
## Summary
**Overall Progress**: {X}% complete
**Current Phase**: {milestone name}
**Active Task**: {task name or "None"}
## Milestones
| Milestone | Progress | Tasks | Blocked |
|-----------|----------|-------|---------|
| MVP | 60% | 3/5 | 0 |
| v1.0 | 0% | 0/8 | 1 |
## Current Focus
### In Progress
- **{Task Name}** in `tasks/{file}.md`
- Status: {N}/{M} acceptance criteria complete
- Files: {list of files being modified}
- Blockers: None
### Blocked
- **{Task Name}** - Reason: {why it's blocked}
- Depends on: {what needs to happen}
## Recent Activity
From steering/decisions.md:
- {date}: {decision or completion}
- {date}: {decision or completion}
## Recommendations
### Immediate
1. **Continue**: {In-progress task} - {why}
2. **Unblock**: {Blocked task} - {how}
### Next Up
1. {Next task} - {brief description}
2. {Following task} - {brief description}
### Needs Attention
- {Issue requiring human input}
## Coverage Analysis
### Requirements → Tasks
| Requirement | Covered By |
|-------------|------------|
| REQ-001 | tasks/auth.md #1, #2 |
| REQ-002 | tasks/auth.md #3 |
| REQ-003 | Not covered |
### Uncovered Requirements
- [REQ-003] {description} - No task defined
Adaptive Behavior
If project just started (< 20% complete):
- Focus on spec completeness
- Recommend running spec-create if gaps found
- Suggest task breakdown for first milestone
If project mid-flight (20-80% complete):
- Focus on blockers and velocity
- Recommend completing in-progress before starting new
- Highlight scope creep if new requirements added
If project nearly done (> 80% complete):
- Focus on remaining tasks
- Highlight any acceptance criteria not met
- Suggest milestone completion checklist
Example Analysis
# Project Status: tt (Time Tracker)
## Summary
**Overall Progress**: 40% complete
**Current Phase**: MVP
**Active Task**: Storage Layer
## Milestones
| Milestone | Progress | Tasks | Blocked |
|-----------|----------|-------|---------|
| MVP | 40% | 2/5 | 0 |
## Current Focus
### In Progress
- **Storage Layer** in `tasks/core.md`
- Status: 2/4 acceptance criteria complete
- Files: `internal/store/store.go`
- Blockers: None
### Completed
- Data Model (task 1)
## Recommendations
### Immediate
1. **Continue**: Storage Layer - 2 criteria remaining (atomic save, dir creation)
### Next Up
1. Start Command - depends on storage being complete
2. Stop Command - can start after Start Command
### Needs Attention
- None - project is on track