gpd-quick

Execute small ad-hoc research tasks with atomic commits and state tracking.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-quick-michaelsengineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpd-quick
Source: https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics/tree/main/.agents/skills/gpd-quick
Command: npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-quick-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Small research tasks like quick derivations, dimensional checks, or numerical spot-checks often get done informally and leave no traceable record. This Skill runs them through a lightweight GPD workflow that keeps atomic commits and STATE.md tracking while skipping heavyweight research, plan-checking, and verification agents. ## Core Features & Use Cases - Quick Task Workflow: Prompts for a task description, initializes a numbered directory under .gpd/quick/, spawns a planner and executor, and commits results atomically. - State Tracking: Records completion via structured gpd state commands so STATE.md and state.json stay in sync without touching ROADMAP.md. - Use Case: A physics researcher needs to verify the dimensional consistency of a cross-section formula mid-phase. The Skill creates .gpd/quick/003-dim-check/, generates a plan and summary, and commits the artifacts with a durable decision record. ## Quick Start Ask the assistant to run a quick GPD task, for example: run a quick dimensional analysis check on the dispersion relation in equation 3.14.

Frequently Asked Questions about gpd-quick

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

FAQPage Schema
How do I run a quick research task with GPD?▼

Invoke the quick workflow and provide a task description when prompted. The Skill initializes a numbered directory under .gpd/quick/, spawns a planner to write a plan, then an executor to complete the work and commit the artifacts atomically.

When should I use quick mode versus the full GPD workflow?▼

Use quick mode for single-step tasks like dimensional checks, factor verification, or numerical spot-checks. Use the full plan-phase and execute-phase workflow for multi-step derivations, numerical pipelines, or work that must be traceable to requirement IDs.

Does gpd-quick require an initialized project?▼

Yes, quick mode requires an existing .gpd directory created by the new-project workflow. It does not require ROADMAP.md, so quick tasks can run mid-phase alongside planned work.

What happens if the planner or executor agent fails?▼

The workflow checks whether the plan file or git commits were produced before treating a subagent as failed. If nothing was produced, it offers to retry the agent, execute the steps in the main context, or abort.

Does quick mode update ROADMAP.md or STATE.md?▼

Quick tasks do not update ROADMAP.md. They record completion through gpd state add-decision and a Last Activity update, keeping STATE.md and state.json in sync without custom markdown sections.