gpd-validate-conventions

Validate physics convention consistency across all completed project phases.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --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/sentinel-multiscale-field-dynamics/tree/main/.agents/skills/gpd-validate-conventions
Command: npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-validate-conventions-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In multi-phase physics projects, conventions like metric signature, Fourier transform definitions, and unit systems can silently drift between phases, invalidating downstream results. This Skill detects sign errors, notation drift, and convention lock violations before they propagate. ## Core Features & Use Cases - Convention Lock Drift Detection: Compares the machine-readable convention lock in state.json against the human-readable CONVENTIONS.md and flags disagreements as critical issues. - Cross-Phase Consistency Scanning: Extracts convention declarations from every completed phase SUMMARY.md and cross-references them against the project-level lock, classifying findings as CRITICAL, WARNING, or INFO. - Automated Conflict Resolution: Spawns consistency-checker and notation-coordinator subagents to validate conventions deeply and resolve critical conflicts with conversion tables. - Use Case: After completing several phases of a quantum field theory project, run this Skill to confirm that the metric signature and Fourier convention used in Phase 3 match those locked in Phase 1, catching a sign flip before it corrupts later calculations. ## Quick Start Ask the AI to validate conventions across all phases, or pass a phase number such as 3 to limit the validation scope to that phase only.

Frequently Asked Questions about gpd-validate-conventions

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

FAQPage Schema
How do I check convention consistency across project phases?▼

Run the validate-conventions workflow with no arguments to scan all completed phases, or pass a phase number to limit scope. It loads the convention lock from state.json, scans phase SUMMARY.md files, and reports mismatches by severity.

What physics conventions does convention validation check?▼

It checks metric signature, Fourier transform convention including factors of 2*pi, unit systems such as natural units with hbar=1 and c=1, sign conventions, coupling constant definitions, and normalization conventions for wavefunctions and propagators.

What happens when a critical convention mismatch is found?▼

Critical issues like metric signature or sign mismatches are flagged prominently, and a notation-coordinator subagent is spawned to determine the correct convention, generate conversion tables, update CONVENTIONS.md, and list affected phases needing re-execution.

Can convention validation run without a convention lock?▼

No. If no conventions are locked in state.json, the workflow reports this and suggests running the execute-phase workflow first, which locks conventions before parallel execution. The lock is the authoritative source of truth.

What if the consistency checker subagent fails to spawn?▼

The workflow falls back to static analysis from the convention lock drift check, phase scan, and cross-reference steps. It notes in the report that deep consistency verification was skipped and suggests rerunning validation later.