gpd-audit-milestone

Audit research milestone completion against phase verifications and original research goals.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research projects spanning multiple phases accumulate unverified claims, inconsistent notation, and forgotten deferred analysis. This Skill audits whether a milestone actually achieved its definition of done before you archive it or move to publication. ## Core Features & Use Cases - Phase Verification Aggregation: Reads every VERIFICATION.md across milestone phases and consolidates critical gaps, open questions, and anti-patterns into one audit report. - Cross-Phase Consistency Checking: Spawns a consistency-checker subagent to validate notation, parameter values, approximations, and units across phases. - Requirements Coverage Scoring: Maps each requirement in REQUIREMENTS.md to its owning phase and reports satisfied, partial, or unsatisfied status. - Optional Mock Peer Review: Runs a referee agent that scores the milestone across 10 dimensions and writes REFEREE-REPORT.md plus a LaTeX companion. - Use Case: After completing five phases of a plasma turbulence study, run the audit to confirm analytical predictions match numerical results and all requirements are covered before writing the paper. ## Quick Start Ask the agent to audit the current milestone, optionally passing a version number, and it will produce a v{version}-MILESTONE-AUDIT.md report with pass, gaps_found, or open_questions status.

Frequently Asked Questions about gpd-audit-milestone

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

FAQPage Schema
How do I audit a research milestone in Get Physics Done?▼

Invoke the audit command with an optional version argument. The skill reads all phase VERIFICATION.md files, checks requirements coverage, runs a cross-phase consistency checker, and writes a v{version}-MILESTONE-AUDIT.md report with a pass, gaps_found, or open_questions status.

What does the milestone audit check for?▼

It checks research question coverage, derivation completeness, claim support, internal consistency across phases, limiting cases, dimensional consistency, error analysis, literature comparison, and catalogued open questions. Each requirement in REQUIREMENTS.md is scored as satisfied, partial, or unsatisfied.

What files are required before running a milestone audit?▼

The audit requires an active GPD project with .gpd/ROADMAP.md and .gpd/STATE.md, plus completed phases containing VERIFICATION.md files. A phase missing its VERIFICATION.md is flagged as an unverified phase, which blocks the audit.

What happens if the consistency checker agent fails to spawn?▼

The audit proceeds without cross-phase consistency checks and notes the skip in the audit report. Phase-level verification results still stand, and you are advised to run the convention validation command separately afterward.

Can the audit run a mock peer review of my research?▼

Yes, if referee_review is enabled in .gpd/config.json or you approve when prompted. A referee agent evaluates the milestone across 10 dimensions including correctness, novelty, and reproducibility, writing REFEREE-REPORT.md and a LaTeX companion.

What are the limitations of the milestone audit?▼

The audit only verifies what phases documented; it cannot detect errors never recorded in VERIFICATION.md or SUMMARY.md files. It also depends on the GPD CLI runtime and an initialized project, so it cannot audit work done outside the GPD workflow.