Overview
Theprogress command checks project progress, summarizes recent work and upcoming tasks, then intelligently routes you to the next actionβeither executing an existing plan or creating the next one. It provides situational awareness before continuing work.
Syntax
How It Works
- Loads project state from STATE.md and ROADMAP.md
- Analyzes recent work - Last completed phases, quick tasks, commits
- Checks current position - Active phase, checkpoints, incomplete plans
- Evaluates next steps - What work is ready or needed
- Routes intelligently - Executes plan, creates plan, or offers options
- Preserves routing logic - Implements Routes A-F from workflow
Routing Logic
The progress command uses six intelligent routing paths:Route A: Execute Existing Plan
Condition: Phase has PLAN.md but no SUMMARY.mdRoute B: Resume from Checkpoint
Condition:.continue-here.md exists
Route C: Plan Next Phase
Condition: Current phase complete, next phase in roadmapRoute D: Create Next Milestone
Condition: All roadmap phases completeRoute E: Offer Options
Condition: Ambiguous state or multiple valid pathsRoute F: Project Complete
Condition: All work done, no todos, clean stateUsage Examples
Mid-project with ready plan
Phase complete, plan next
Resume from checkpoint
Multiple options available
Project complete
What Gets Analyzed
Project Metrics
- Total phases vs completed
- Milestone progress
- Project start date and duration
- Commit frequency
Recent Activity
- Last 3 completed phases
- Last 5 quick tasks
- Recent commits with messages
- Last discussion or planning session
Current State
- Active phase identification
- Checkpoint detection
- Incomplete plans (PLAN without SUMMARY)
- Health issues (via implicit health check)
Upcoming Work
- Next phase in roadmap
- Pending todos count by area
- Active debug sessions
- Blockers or dependencies
Edge Case Handling
No STATE.md
Corrupted STATE.md
Ambiguous next phase
Integration with Other Commands
Before planning
After resuming
During active work
Files Read
.planning/STATE.md- Project state.planning/ROADMAP.md- Phase definitions.planning/CONTEXT.md- Decisions and context.planning/phases/**/PLAN.md- Phase plans.planning/phases/**/SUMMARY.md- Completion records.planning/phases/**/.continue-here.md- Checkpoints.planning/quick/*.md- Quick tasks.planning/todos/**/*.md- Pending todos.planning/debug/*.md- Debug sessions.git/logs/HEAD- Recent commits
When to Use
Perfect for
- Starting your work session
- After completing a phase
- When unsure what to do next
- Before planning sessions
- After long breaks
- Sprint planning
- Status check-ins
Pairs well with
/gsd:resume-workβ/gsd:progress(detailed status)/gsd:progressβ/gsd:execute(ready to work)/gsd:progressβ/gsd:plan-phase(plan next)/gsd:progressβ/gsd:check-todos(review todos)
Success Criteria
- β Project state loaded
- β Recent work summarized
- β Current position identified
- β Next steps evaluated
- β Intelligent routing applied (Routes A-F)
- β User knows exactly what to do next
Related Commands
resume-work- High-level restorationhealth- Validate project stateexecute- Execute phase planplan-phase- Plan next phasecheck-todos- Review pending todos