gpd-progress

Summarize GPD project progress and route to the next action.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-progress-michaelsengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-progress
Source: https://github.com/MichaelsEngineering/get-physics-done-test/tree/main/.agents/skills/gpd-progress
Command: npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-progress-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides situational awareness of Get Physics Done (GPD) research progress by summarizing recent work, decisions, and blockers, and routing to the next action (execute or plan).

Core Features & Use Cases

  • Provides a compact and rich status snapshot that combines phase status, recent summaries, and contextual insights.
  • Routes to the appropriate GPD commands to continue the workflow (execute or plan) based on current state.
  • Helps researchers maintain momentum by surfacing blockers and recommended next steps.

Quick Start

Check the current GPD project progress and route to the next action in the workflow.

Frequently Asked Questions about gpd-progress

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

FAQPage Schema
How do I track research project progress and identify blockers?

Tracking research project progress involves summarizing recent work, decisions, and blockers, then routing to the next action. It reads current progress state and presents a structured recommendation with conditional guidance to maintain momentum.

What is the best way to summarize context and route to the next workflow action?

Summarizing context and routing workflow actions requires evaluating current state to guide the next step. It provides a status snapshot combining phase status, recent summaries, and contextual insights to route to execute or plan.

How do I get a brief or full status report of my current planning context?

Getting a brief or full status report of your planning context involves generating a compact snapshot. It supports brief and full reports that highlight current priorities and blockers to provide situational awareness.

Does this progress tracking approach require specific CLI dependencies?

This progress tracking approach requires no external dependencies to function. It operates independently to read progress state and present structured recommendations based on the current workflow context.

When should I not use automated progress summaries for research planning?

Automated progress summaries for research planning should be avoided when manual contextual awareness is preferred or when your workflow lacks distinct execute and plan phases. It relies on existing state data to surface blockers and route actions.