FESADev/.codex/skills/fesa-research-evidence/SKILL.md

name, description

name	description
fesa-research-evidence	Use when collecting FESA solver research evidence, FEM theory sources, benchmarks, source reliability, and applicability limits for a feature before formulation or reference model design.

FESA Research Evidence

Use this skill to collect source-backed evidence for solver features while separating verified facts from inference.

Inputs

Read these first:

• AGENTS.md
• docs/SOLVER_AGENT_DESIGN.md
• docs/<feature-id>/requirements.md
• User-supplied books, papers, manuals, or benchmark constraints

Workflow

1. Extract research questions from the requirements and open issues.
2. Build a Source Inventory with Source Reliability Tier for manuals, standards, books, papers, and benchmark repositories.
3. Summarize FEM theory needed for the feature without finalizing implementation math.
4. Identify Candidate Benchmarks, patch tests, analytical checks, MMS/MES candidates, and public examples.
5. Record Verification Relevance for displacement, reaction, element force, stress, strain, energy, or residual checks.
6. Record Applicability Limits: element type, material model, deformation assumptions, loading, boundary conditions, and known exclusions.
7. Separate verified facts from inference. Mark unsupported claims as inference or open questions.

Output Contract

Produce or revise docs/<feature-id>/research.md with:

• Metadata and source requirement path
• Research Questions
• Source Inventory and Source Reliability Tier
• Theory Summary
• Candidate Benchmarks
• Verification Relevance
• Applicability Limits
• Downstream Handoff

Boundaries

• Do not implement code.
• Do not finalize FEM formulations.
• Do not design C++ APIs or file ownership.
• Do not run Abaqus, Nastran, or any reference solver.
• Do not generate or modify Abaqus reference CSV files.
• Do not approve release readiness.

Quality Gate

• Every key claim has a source, reliability tier, or explicit inference label.
• Benchmark candidates include what quantity they can verify and what they cannot verify.
• Missing source evidence is carried forward as an open issue.
• No reference value, tolerance, or compatibility claim is invented.
• Benchmark/reference evidence identifies exact candidate artifacts, target quantities, applicability limits, and unresolved acceptance questions for Numerical Review.

Handoff

Return docs/<feature-id>/research.md, status, evidence summary, and blockers to Coordinator Agent. Route formulation evidence to Formulation Agent and benchmark/reference evidence, artifact candidates, and source limits to Numerical Review Agent through Coordinator Agent.