gpd-quick

Execute ad-hoc physics tasks with atomic commits and durable Git-like state tracking via GPD quick workflow.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --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/get-physics-done-test/tree/main/.agents/skills/gpd-quick
Command: npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-quick-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute quick, ad-hoc physics tasks within the Get Physics Done (GPD) framework, ensuring atomic commits and durable state while skipping optional agents for speed.

Core Features & Use Cases

  • Atomic quick tasks: plan, execute, and commit a single focused task with durable state updates.
  • Dimensional checks, quick derivations, and literature lookups for fast validation in early-stage research.
  • Isolated quick task workspace under .gpd/quick/ for reproducible results.

Quick Start

Describe the task you want solved and initiate the quick workflow to generate a plan, execute the task atomically, and commit the results.

Frequently Asked Questions about gpd-quick

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

FAQPage Schema
How do I run quick physics derivations and dimensional checks in a fast-paced research workflow?

Quick physics derivations and dimensional checks are handled by the GPD quick workflow, which plans, executes, and atomically commits focused tasks while maintaining durable state in an isolated .gpd/quick workspace.

What is the best way to ensure ad-hoc physics tasks maintain state tracking and reproducibility?

Ad-hoc physics tasks maintain state tracking through atomic commits and durable state anchoring within an initialized GPD project, using a project contract to guide planning and execution for reproducible results.

Do I need an initialized GPD project directory before running quick research tasks?

Yes, an initialized GPD project with a .gpd directory is required. The quick workflow uses state anchoring and project contracts within this directory to guide planning and execution.

Can I execute literature lookups and sanity checks without invoking optional agents?

Yes, the quick workflow skips optional agents for speed, focusing on atomic task execution for literature lookups and sanity checks while still enforcing state tracking and durable commits.

How does the GPD quick workflow differ from standard physics task execution methods?

The GPD quick workflow distinguishes itself by isolating quick tasks under .gpd/quick and skipping optional agents to prioritize speed, while standard approaches may lack enforced atomic commits and durable state tracking.

When should I avoid using the quick task workflow for physics research?

You should avoid the quick workflow for physics research when a task requires multi-step, non-atomic execution or lacks a defined project contract, as this workflow prioritizes single focused tasks with immediate state anchoring.