Skip to main content

Overview

The progress 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

  1. Loads project state from STATE.md and ROADMAP.md
  2. Analyzes recent work - Last completed phases, quick tasks, commits
  3. Checks current position - Active phase, checkpoints, incomplete plans
  4. Evaluates next steps - What work is ready or needed
  5. Routes intelligently - Executes plan, creates plan, or offers options
  6. 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.md

Route B: Resume from Checkpoint

Condition: .continue-here.md exists

Route C: Plan Next Phase

Condition: Current phase complete, next phase in roadmap

Route D: Create Next Milestone

Condition: All roadmap phases complete

Route E: Offer Options

Condition: Ambiguous state or multiple valid paths

Route F: Project Complete

Condition: All work done, no todos, clean state

Usage Examples

Mid-project with ready plan

Output:

Phase complete, plan next

Output:

Resume from checkpoint

Output:

Multiple options available

Output:

Project complete

Output:

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