gpd-error-propagation

Propagate uncertainties through multi-step physics derivations and generate an ERROR-BUDGET.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track and budget uncertainties across multi-step physics derivations, enabling reliable error bars for final results.

Core Features & Use Cases

  • Trace the full derivation chain from inputs to a target quantity within GPD projects, identifying where uncertainties originate.
  • Classify and catalog uncertainty sources (input, numerical, approximation, model, and correlation) and build a transparent error budget.
  • Generate a formal ERROR-BUDGET.md and update project state with propagated uncertainties for reproducibility.

Quick Start

Run gpd-error-propagation to generate an error budget for a target quantity across the project’s derivation chain.

Frequently Asked Questions about gpd-error-propagation

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

FAQPage Schema
How do I propagate uncertainties through a multi-step physics derivation?

To propagate uncertainties through a multi-step physics derivation, trace the derivation chain from inputs to the target quantity, identify uncertainty sources, compute sensitivities, and generate a formal error budget tracking correlated inputs across dependency trees.

How do I calculate sensitivities for correlated inputs in an error budget?

You calculate sensitivities for correlated inputs using analytical or numerical methods, quantifying how intermediate results and approximations interact across dependency trees to produce a validated error budget for your target quantity.

Can I track uncertainty sources across state-tracked project workflows?

Yes, you can track uncertainty sources across state-tracked project workflows by classifying inputs, numerical factors, and correlations, then updating the project state with propagated uncertainties for full reproducibility.

Do I need a phase-based workflow to generate an error budget for a target quantity?

A phase-based workflow is supported for generating an error budget, applying to state-tracked projects where intermediate results and correlated inputs must be quantified across derivation dependency trees to validate final target quantities.

What are the limitations of tracking approximation uncertainties across dependency trees?

Limitations include the complexity of accurately classifying and quantifying approximation and model uncertainties across deep dependency trees, requiring careful state management to ensure intermediate results remain validated throughout the derivation chain.