gpd-debug

Diagnose physics calculation errors through parallel subagent investigation with persistent debug sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Physics calculations fail in subtle ways—sign errors, missing factors of 2, convention mismatches, numerical instabilities—that are hard to isolate and expensive to investigate in a single context window. This Skill orchestrates systematic root-cause diagnosis using dedicated investigation agents while keeping the main conversation lean. ## Core Features & Use Cases - Quick Triage Pattern Matching: Matches discrepancy signatures (factor of 2, sign flip, wrong power law, divergence) against a table of common physics error causes before full investigation. - Parallel Investigation Agents: Spawns one gpd-debugger subagent per issue with symptoms pre-filled, each with fresh context for reading derivations and testing hypotheses. - Persistent Debug Sessions: Writes investigation state to .gpd/debug/ session files so debugging survives context resets and supports checkpoint-based continuation. - Batch and Interactive Modes: Processes all gaps from VERIFICATION.md in parallel when called by verify-work, or runs a single interactive investigation loop with the user. - Use Case: A researcher's simulation shows energy drifting 1% over 1000 timesteps. The Skill gathers symptoms, spawns a debugger agent that identifies a forward Euler integrator replacing the symplectic Verlet scheme, and records the root cause in VERIFICATION.md for targeted fix planning. ## Quick Start Ask the AI to debug your physics issue by describing the expected result, the actual result, and how the discrepancy behaves, for example: "Debug why my energy conservation check drifts by 1% over 1000 timesteps."

Frequently Asked Questions about gpd-debug

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

FAQPage Schema
How do I debug a physics calculation that gives the wrong result?▼

Describe the expected result, the actual result, and the discrepancy character (constant factor, sign flip, wrong power law, divergence). The Skill matches the signature against common error patterns, then spawns an investigation agent to find the root cause.

How does systematic physics debugging differ from software debugging?▼

Software bugs are deterministic, but physics errors can be regime-dependent: a sign error that matters only in one limit, a factor of 2 from symmetrization, or a numerical instability mimicking a phase transition. The investigation follows a hierarchy from dimensional analysis to bisection.

Can I debug multiple verification failures at once?▼

Yes. In batch mode, the Skill parses all gaps from VERIFICATION.md and spawns one investigation agent per gap in parallel. Each agent returns a root cause, and the gaps are updated with artifacts, missing items, and physics impact.

What happens if the investigation does not find a root cause?▼

The gap is marked as needing expert review with a summary of what was ruled out. You can continue investigating with more context, simplify the problem to a minimal reproducing case, or proceed with remaining diagnoses.

Does debugging state survive context window resets?▼

Yes. Each investigation writes its state to a session file under .gpd/debug/. Continuation agents read this file to inherit prior hypotheses and evidence, so long investigations can resume after checkpoints or resets.