Files
FESADev/.codex/skills/fem-physics-review/SKILL.md
T
2026-09-05 15:14:21 +09:00

2.4 KiB

name, description
name description
fem-physics-review Use when validated structural FEM results need an independent physical-plausibility review before release-readiness evaluation.

FEM Physics Review

Determine whether numerically passing results also satisfy the documented physical behavior of the modeled problem.

Inputs

  • Requirements, formulation, numerical review, reference model, and I/O contract
  • Passing implementation-owned build/test and comparison evidence required by the feature
  • Solver outputs and approved reference artifacts, read-only

Workflow

  1. Confirm prerequisite evidence is passing, current, and tied to the same feature_id and contract revision.
  2. Evaluate only documented expectations: global equilibrium, reactions, deformation direction/mode, symmetry or zeros, internal-force balance, stress/strain signs and coordinates, conservation, residuals, energy, and family-specific behavior.
  3. Check coverage is sufficient for the claimed feature scope; distinguish a solver defect from formulation, I/O, acceptance-model, or evidence gaps.
  4. Report findings before the verdict and route each failure to its owning stage.

Read the applicable analysis-family guidance. Use evidence and handoff for the verdict and workflow and decision authority for missing physical expectations.

Output

Follow Feature document management: read the Coordinator's feature context, keep main reports concise, and link necessary owned details in the same feature folder.

Create or revise docs/<feature-id>/physics-evaluation.md with evidence identity, checks and expected relations, observed results, failure classification, coverage assessment, verdict, residual risks, and handoff.

Evidence

Each check states its governing relation or approved expectation, data source, units/coordinates, calculation, tolerance source where applicable, and pass/fail result. Explain why a check is inapplicable rather than silently omitting it.

Boundary

Do not edit code, tests, requirements, formulations, I/O contracts, reference models, reference artifacts, or tolerances. Do not invent extra acceptance gates, approve numerical comparison, run external solvers, or approve release. A physics pass means ready for release-readiness audit only.