gsd-progress

To check project milestone status and decide the next action, you need a tool that aggregates recent activity and evaluates routing logic. This skill summarizes progress and applies Routes A through F to recommend whether to execute an existing plan or create a new one.

The best way to prevent context drift during sprint reviews is to summarize recent work and route next steps systematically. This skill reads your workflow context file to maintain continuity and determines the next actionable step for ongoing projects.

To route work to execute an existing plan or create the next phase plan, you evaluate current plans using preserved routing logic. This skill applies Routes A through F to intelligently route your next development wave based on milestone status.

Yes, you need a workflow context file to check project progress effectively. This skill requires access to the context file to preserve routing logic, handle edge cases, and maintain continuity across review and execution cycles.

Yes, you can use this for individual project milestones during status reviews. It applies to milestone status checks, planning, and execution decision workflows, producing a concise project snapshot for situational awareness.

Automated project status checks require preservation of routing logic and edge-case handling to function correctly. Without a properly maintained workflow context file, the skill cannot determine Routes A through F or accurately summarize recent changes.