gsd-progress

Summarize project progress and route to the next action with deterministic logic.

Updated Jan 28, 2025
One-click install
npx skills add https://github.com/aslaii/dotfiles --skill gsd-progress-aslaii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-progress
Source: https://github.com/aslaii/dotfiles/tree/main/claude/skills/gsd-progress
Command: npx skills add https://github.com/aslaii/dotfiles --skill gsd-progress-aslaii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Check project progress, summarize recent work and what's ahead, then intelligently route to the next action (execute or plan), with an optional forensic audit after the standard report.

Core Features & Use Cases

  • Progress summarization: generate a concise view of recent work and upcoming milestones.
  • Action routing: decide whether to execute an existing plan or formulate a new one based on context.
  • Forensic auditing: optional --forensic mode appends a 6-check integrity audit to the report for validation and traceability.
  • Context preservation: loads relevant workflow files from the CLAUDE setup to provide situational awareness before action.

Quick Start

Summarize current progress and generate the next actionable step.

Frequently Asked Questions about gsd-progress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize software engineering progress and route the next development action?

To summarize software engineering progress and route the next action, this Skill generates a concise view of recent work and upcoming milestones, then uses deterministic routing logic to decide whether to execute an existing plan or formulate a new one.

What is forensic auditing in software development workflows?

Forensic auditing in software development workflows is an optional integrity validation process that appends a 6-check audit to a progress report, ensuring traceability and validation for recent engineering actions.

How does deterministic routing logic decide between planning and executing tasks?

Deterministic routing logic decides between planning and executing tasks by evaluating loaded workflow context files, assessing current project progress, and directing the team to either execute an existing plan or formulate a new one based on situational awareness.

Can I use this progress routing Skill for team check-ins and plan-execute cycles?

Yes, you can use this progress routing Skill for team check-ins and plan-execute cycles. It is specifically designed to apply to software development workflows, summarizing recent work and routing the next actionable step.

What is the best way to preserve context before routing next actions in a project?

The best way to preserve context before routing next actions is to load relevant workflow files from the CLAUDE setup, which provides the necessary situational awareness before intelligently deciding the next development step.

When should I not use automated progress summarization for engineering workflows?

You should not use automated progress summarization when you lack established workflow files for context loading, as the routing logic relies on situational awareness from existing plans to determine the next action accurately.