AbaqusSubroutineDev/.codex/skills/abaqus-subroutine-research/SKILL.md

name, description

name	description
abaqus-subroutine-research	Use when collecting Abaqus User Subroutine research evidence from official Abaqus manuals, books, papers, benchmark sources, and source reliability notes before formulation, interface definition, or test model design.

Abaqus Subroutine Research

Use this skill to collect source-backed Research evidence for Abaqus User Subroutine work while separating verified facts from inference.

REQUIRED SUB-SKILL: Use fem-theory-query for finite element theory, formulation, solver behavior, benchmark, or numerical verification knowledge.

Inputs

Read first:

• AGENTS.md
• docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md
• docs/research/README.md
• docs/requirements/<feature-id>.md
• docs/AbaqusUserSubroutineManual/INDEX_MAP.md
• docs/AbaqusUserSubroutineManual/INDEX.md
• User-provided references, official Abaqus documentation links, books, papers, and benchmark sources

Workflow

1. Define exact research questions from requirements and open issues.
2. For FEM knowledge, use fem-theory-query and retain the returned wiki evidence.
3. For Abaqus User Subroutine manual facts, locate the section in INDEX_MAP.md, read the complete INDEX.md record, then read every listed source_ranges span in order.
4. Treat INDEX.md summaries, keywords, and content anchors as retrieval metadata rather than authoritative facts.
5. Search other sources as needed: books, peer-reviewed papers, official benchmarks, and project-provided references.
6. Record source reliability tier, citation, scope, assumptions, and applicability limits.
7. Extract only facts needed by downstream formulation, Abaqus ABI interface definition, TDD test models, and Fortran implementation.
8. Separate verified facts from inference.
9. Identify candidate benchmark models, closed-form checks, patch tests, tangent checks, and negative tests.
10. Record unresolved conflicts or missing evidence as open issues.

Output Contract

Produce or revise docs/research/<feature-id>-research.md with Source Inventory, Source Reliability Tier, Extracted Facts, Candidate Benchmarks, Verification Relevance, Applicability Limits, Open Issues, and Downstream Handoff.

Boundaries

• Do not implement code.
• Do not finalize FEM formulations.
• Do not design Fortran source layout or Abaqus wrapper code.
• Do not run Abaqus.
• Do not generate reference CSVs.
• Do not approve release readiness.

Quality Gate

• Source tiers are explicit.
• Each extracted fact links to a cited source.
• Each FEM claim traces to fem-theory-query evidence; each Abaqus manual claim traces to a section and every source span used.
• Inference is labeled as inference.
• Benchmark applicability limits are clear enough for Formulation and Reference Model Agents.

Handoff

Send math evidence to Formulation Agent, Abaqus parameter evidence to I/O Definition Agent, benchmark candidates to Reference Model Agent, and validation risk notes to Numerical Review Agent.