gsd-progress

To track project progress and route next actions, aggregate recent work, current status, and upcoming milestones. The system then uses routing logic with edge-case handling to decide whether to execute an existing plan or generate a new one for your software development workflow.

The best way to summarize sprint progress is to collect recent work and surface relevant context to support informed decision-making. This approach preserves routing logic to intelligently determine whether to continue executing an existing plan or create the next one.

Action routing works by evaluating contextual project summaries against predefined routes. It decides whether to execute an existing plan or generate a new one, preserving routing logic through multiple routes and handling edge cases to ensure correct next actions.

Yes, you can use progress tracking for team planning sessions. It provisions relevant context before continuing work, aggregates recent milestones into a concise view, and routes to the next action, making it suitable for contextual awareness requirements.

You should create a new project plan instead of executing an existing one when progress aggregation and contextual awareness indicate the current trajectory is invalid. The routing logic evaluates project status and handles edge cases to determine if a new plan is necessary.

No, gsd-progress does not require any dependencies to summarize project status. It independently collects recent work and upcoming milestones, then applies internal routing logic to determine the next action without external components.