gpd-validate-conventions

Validate physics convention locks across completed phases for drift.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure that physics convention locks are consistently applied across all completed phases by detecting drift and surfacing actionable fixes.

Core Features & Use Cases

  • Cross-phase convention validation against a central lock to prevent drift between phases.
  • Automated scanning of phase summaries and state.json to surface inconsistencies and guide resolution.
  • Actionable guidance for locking resolved conventions and re-executing affected phases in a reproducible workflow.

Quick Start

Run the validate-conventions workflow to audit the current state and surface any convention drift with concrete remediation steps.

Frequently Asked Questions about gpd-validate-conventions

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

FAQPage Schema
How do I detect physics convention drift across completed project phases?

Detect convention drift by running an automated validation scan that compares phase artifacts against a central convention lock. The scan performs cross-phase comparisons to surface inconsistencies and outputs actionable findings classified as CRITICAL or WARNING.

What is cross-phase convention validation and when do I need it?

Cross-phase convention validation is the process of checking that physics conventions remain consistently applied throughout a project lifecycle. You need it when multiple completed phases must adhere to a single source of truth to prevent mathematical or physical inconsistencies.

How do I lock resolved physics conventions and re-execute affected phases?

Lock resolved conventions by following the actionable remediation guidance provided after a validation scan detects drift. Once the central lock is updated, you can re-execute affected phases in a reproducible automated workflow to ensure total alignment.

Can I automate state loading and phase scanning to check convention consistency?

Yes, automated state loading and phase scanning are core features of the validation workflow. The process automatically loads state.json and scans phase summaries to identify inconsistencies without manual intervention.

What is the best way to maintain a single source of truth for physics conventions?

Maintain a single source of truth by using an automated validation workflow that checks a central convention lock against all phase artifacts. This detects drift early and provides concrete remediation steps to resolve any deviations.

Why does my physics convention validation keep showing WARNING findings?

Convention validation surfaces WARNING findings when cross-phase comparisons detect minor inconsistencies between phase artifacts and the central convention lock. Review the actionable guidance attached to each finding to resolve the drift and lock the updated conventions.