---
name: abaqus-subroutine-test-models
description: Use when designing Abaqus User Subroutine TDD test models, no-Abaqus driver cases, Fortran manifest entries, Abaqus .inp reference bundles, artifact metadata, source hashes, log tails, and CSV extraction contracts.
---

# Abaqus Subroutine Test Models

Use this skill to define the TDD test model portfolio before Fortran implementation and Abaqus validation.

**REQUIRED SUB-SKILL:** Use `fem-theory-query` for benchmark selection, patch tests, analytical expectations, and numerical verification design.

## Inputs

Read first:

- `AGENTS.md`
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
- Requirements, research, formulation, numerical review, and interface documents

## Workflow

1. Define TDD test model categories: no-Abaqus unit driver, analytical material point, finite-difference tangent check, `.inp` smoke model, benchmark/reference model, regression case, and negative case.
2. For no-Abaqus tests, define `tests/fortran/manifest.json` entries, source files, driver inputs, expected outputs, and tolerances.
3. For Abaqus validation, define `references/<feature-id>/<model-id>/` artifact bundle requirements.
4. Require `model.inp`, `metadata.json`, source hash entries, Abaqus version, compiler version, msg/dat/log tail files, and extracted CSV files for `ready-for-comparison` artifacts.
5. Define Coverage Matrix rows mapping requirement id, model id, compared quantity, tolerance, artifact file, and status.

## Output Contract

Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with TDD test model strategy, no-Abaqus manifest plan, Abaqus Input Requirements, Artifact Bundle Contract, Metadata JSON Contract, Reference CSV Requirements, Coverage Matrix, Artifact Acceptance Checklist, and Downstream Handoff.

## Boundaries

- Do not implement code.
- Do not run Abaqus.
- Do not generate reference CSVs.
- Do not invent Abaqus, compiler, or source hash provenance.
- Do not compare implementation results.
- Do not approve release readiness.

## Quality Gate

- Every `must` requirement maps to at least one no-Abaqus test or Abaqus validation model.
- No-Abaqus tests identify exactly what should fail before implementation.
- Each ready artifact contract includes source hash, Abaqus version, compiler version, msg/dat/log tail, and CSV file expectations.
- Missing required reference artifacts keep the model at `needs-reference-artifacts`.

## Handoff

Send no-Abaqus test order to Implementation Planning Agent, ABI/schema issues to I/O Definition Agent, artifact readiness needs to Reference Verification Agent, and physics expectations to Physics Evaluation Agent.
