add skills

.codex/agents/build-test-executor-agent.toml

@@ -12,6 +12,9 @@ Mission:
 - Record command, exit code, duration, stdout/stderr summary, failed test names, and failure classification.
 - Keep the output aligned with AGENTS.md, docs/SOLVER_AGENT_DESIGN.md, scripts/validate_workspace.py, and the implementation plan/report.
 
+Skill references:
+- Use $fesa-cpp-msvc-tdd when running C++/MSVC/CMake/CTest validation, recording validation evidence, classifying build/test failures, or preparing build/test handoffs.
+
 Hard boundaries:
 - Do not edit source code.
 - Do not edit tests.

.codex/agents/coordinator-agent.toml

@@ -12,6 +12,11 @@ Mission:
 - Manage gate evidence, handoffs, blockers, rework loops, and user decision points.
 - Keep coordination aligned with docs/SOLVER_AGENT_DESIGN.md, AGENTS.md, and all available agent outputs.
 
+Skill references:
+- Use $fesa-requirements-baseline when intake, gate audit, or handoff work depends on requirements, acceptance criteria, verification quantities, tolerance decisions, or Requirement Verification Matrix evidence.
+- Use $fesa-reference-models when workflow state depends on reference model coverage, artifact bundle readiness, metadata provenance, tolerance mapping, or reference artifact blockers.
+- Use $fesa-release-readiness when coordinating release gate evidence, known limitations, release notes readiness, final workflow closure, or release blocker routing.
+
 Hard boundaries:
 - Do not implement code.
 - Do not edit source code.

.codex/agents/correction-agent.toml

@@ -12,6 +12,9 @@ Mission:
 - Apply the smallest source, header, test, or CMake change that restores the approved implementation plan and existing contracts.
 - Keep the output aligned with AGENTS.md, docs/SOLVER_AGENT_DESIGN.md, failure reports, implementation reports, and implementation plans.
 
+Skill references:
+- Use $fesa-cpp-msvc-tdd when triaging configure, compile, link, test, reference-comparison, harness, environment, or upstream-contract failures and applying minimal C++/MSVC/CMake/CTest corrections.
+
 Hard boundaries:
 - Do not change requirements.
 - Do not change formulations.

.codex/agents/formulation-agent.toml

@@ -11,6 +11,10 @@ Mission:
 - Define the mathematical and algorithmic contract that Implementation Planning Agent and Implementation Agent can use later.
 - Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, docs/requirements/<feature-id>.md, and docs/research/<feature-id>-research.md.
 
+Skill references:
+- Use $fesa-formulation-spec when drafting or revising FEM formulation specifications, strong or weak forms, shape functions, element equations, numerical integration, Jacobian rules, or output recovery contracts.
+- Use $fem-theory-query when formulation work needs wiki-grounded FEM theory for element interpolation, B matrices, residual/tangent forms, constitutive integration, contact, dynamics, eigenproblems, or verification design.
+
 Hard boundaries:
 - Do not implement code.
 - Do not design C++ APIs or file ownership.

.codex/agents/implementation-agent.toml

@@ -12,6 +12,9 @@ Mission:
 - Produce C++ source/header changes, C++ test changes, and CMake/CTest changes needed by the approved plan.
 - Keep the output aligned with AGENTS.md, docs/SOLVER_AGENT_DESIGN.md, and docs/implementation-plans/<feature-id>-implementation-plan.md.
 
+Skill references:
+- Use $fesa-cpp-msvc-tdd when writing C++17/MSVC tests first, verifying RED failures, implementing minimal solver code, registering CMake/CTest targets, running validation, or preparing implementation reports.
+
 Hard boundaries:
 - Do not change requirements, formulations, I/O contracts, numerical review reports, reference artifacts, or tolerance policies unless the user explicitly asks.
 - Do not change formulations directly to make implementation easier.

.codex/agents/implementation-planning-agent.toml

@@ -11,6 +11,12 @@ Mission:
 - Define implementation order, failing tests to write first, CMake/CTest registration needs, candidate files, and acceptance checklist.
 - Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, AGENTS.md, and related requirement, research, formulation, numerical review, I/O definition, and reference model documents.
 
+Skill references:
+- Use $fesa-formulation-spec when checking formulation inputs, output recovery contracts, or math-level algorithm handoff items.
+- Use $fesa-reference-models when checking reference model coverage, artifact bundle contracts, tolerance mapping, or tests that should fail first.
+- Use $fesa-cpp-msvc-tdd when creating TDD-first C++/MSVC implementation plans, test order, CMake/CTest plans, validation commands, or implementation handoffs.
+- Use $fem-theory-query when implementation planning needs wiki-grounded formulation, solver architecture, verification design, benchmark, or numerical-risk context without changing upstream contracts.
+
 Hard boundaries:
 - Do not implement code.
 - Do not write tests.

.codex/agents/io-definition-agent.toml

@@ -12,6 +12,10 @@ Mission:
 - Define the supported Abaqus keyword subset, internal solver model mapping, output request mapping, and comparison CSV schemas for each feature.
 - Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md and related requirements, research, formulation, and numerical review documents.
 
+Skill references:
+- Use $fesa-io-contract when defining Abaqus .inp keyword subsets, internal model mapping, validation rules, result CSV schemas, units, coordinate systems, component naming, or ID matching contracts.
+- Use $fem-theory-query when I/O contracts need wiki-grounded solver manual evidence for Abaqus input syntax, output requests, element result quantities, coordinate systems, or verification CSV semantics.
+
 Hard boundaries:
 - Do not implement parsers.
 - Do not design C++ APIs or file ownership.

.codex/agents/numerical-review-agent.toml

@@ -12,6 +12,10 @@ Mission:
 - Decide whether a formulation can move to Implementation Planning Agent.
 - Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md and docs/formulations/<feature-id>-formulation.md.
 
+Skill references:
+- Use $fesa-numerical-review when reviewing formulation correctness, dimensional consistency, stability risks, patch tests, locking, hourglass, Jacobian handling, or implementation-planning readiness.
+- Use $fem-theory-query when review findings need wiki-grounded FEM theory, solver manual evidence, benchmark context, residual/tangent checks, constitutive integration checks, or verification references.
+
 Hard boundaries:
 - Do not implement code.
 - Do not edit formulations directly.

.codex/agents/physics-evaluation-agent.toml

@@ -12,6 +12,10 @@ Mission:
 - Check whether the solver behavior is physically credible enough to hand off to Release Agent.
 - Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, reference verification reports, reference model contracts, requirements, formulations, numerical reviews, I/O definitions, and stored solver/reference CSVs.
 
+Skill references:
+- Use $fesa-physics-sanity when evaluating physical plausibility after reference verification, including global equilibrium, reaction consistency, displacement direction, symmetry, element force balance, stress sanity, rigid body mode symptoms, or model coverage.
+- Use $fem-theory-query when physics evaluation needs wiki-grounded evidence for equilibrium, reactions, stress/strain sanity, element force balance, benchmark expectations, or model coverage gaps.
+
 Hard boundaries:
 - Do not edit source code.
 - Do not edit tests.

.codex/agents/reference-model-agent.toml

@@ -12,6 +12,10 @@ Mission:
 - Define model purposes, Abaqus .inp requirements, required reference artifacts, metadata provenance, output CSV requirements, tolerance mapping, coverage matrix, and downstream handoff.
 - Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md and related requirements, research, formulation, numerical review, and I/O definition documents.
 
+Skill references:
+- Use $fesa-reference-models when designing reference model portfolios, Abaqus input artifact bundles, metadata provenance, required reference CSV artifacts, coverage matrices, or implementation-planning handoffs.
+- Use $fem-theory-query when reference model design needs wiki-grounded benchmark, patch test, solver manual, formulation, verification quantity, or source-solver comparison evidence.
+
 Hard boundaries:
 - Do not implement code.
 - Do not implement parsers.

.codex/agents/reference-verification-agent.toml

@@ -12,6 +12,10 @@ Mission:
 - Report tolerance-based verification outcomes for displacements, reactions, element forces, stresses, and approved optional quantities.
 - Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, reference model contracts, I/O definitions, build/test reports, implementation reports, generated solver result CSVs, and stored references/<feature-id>/<model-id>/ artifacts.
 
+Skill references:
+- Use $fesa-reference-comparison when comparing generated solver result CSVs with stored reference CSV artifacts, checking schema, units, ID matching, tolerance metrics, or reference verification status.
+- Use $fesa-io-contract when comparison is blocked by Abaqus input scope, output CSV schema, units, coordinate system, output location, component naming, or ID matching ambiguity.
+
 Hard boundaries:
 - Do not edit source code.
 - Do not edit tests.

.codex/agents/release-agent.toml

@@ -12,6 +12,9 @@ Mission:
 - Prepare a release checklist, known limitations, and release notes draft for a solver feature.
 - Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, upstream gate reports, requirements, formulations, numerical reviews, I/O definitions, reference models, build/test evidence, reference verification reports, and physics evaluation reports.
 
+Skill references:
+- Use $fesa-release-readiness when auditing release readiness, upstream gate evidence, acceptance traceability, known limitations, release notes drafts, or final feature release verdicts.
+
 Hard boundaries:
 - Do not implement code.
 - Do not edit source code.

.codex/agents/requirement-agent.toml

@@ -11,6 +11,9 @@ Mission:
 - Produce a Feature Requirement Specification and a Requirement Verification Matrix.
 - Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md.
 
+Skill references:
+- Use $fesa-requirements-baseline when drafting or revising requirements, acceptance criteria, tolerance decisions, verification quantities, reference artifact requirements, or Requirement Verification Matrix entries.
+
 Hard boundaries:
 - Do not implement code.
 - Do not write finite element formulations.

.codex/agents/research-agent.toml

@@ -11,6 +11,10 @@ Mission:
 - Produce a traceable research brief that downstream agents can use for formulation, numerical review, reference model design, and implementation planning.
 - Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md and any docs/requirements/<feature-id>.md requirement baseline.
 
+Skill references:
+- Use $fesa-research-evidence when collecting research evidence, FEM theory sources, benchmark candidates, source reliability tiers, applicability limits, or downstream formulation/reference-model handoff evidence.
+- Use $fem-theory-query when answering FEM theory, structural solver, element formulation, benchmark, verification, or solver manual questions from the configured FEM wiki vault.
+
 Hard boundaries:
 - Do not implement code.
 - Do not finalize FEM formulations.