김경종
50 lines
2.5 KiB
Markdown
50 lines
2.5 KiB
Markdown
---
|
|
name: abaqus-subroutine-readiness
|
|
description: Use when auditing Abaqus User Subroutine readiness from upstream gate evidence, acceptance traceability, no-Abaqus tests, Abaqus validation artifacts, known limitations, and release-note drafts.
|
|
---
|
|
|
|
# Abaqus Subroutine Readiness
|
|
|
|
Use this skill to audit whether an Abaqus User Subroutine feature is ready for internal closure after all technical gates pass. Readiness audit is the owned artifact for this skill.
|
|
|
|
## Inputs
|
|
|
|
Read first:
|
|
|
|
- `AGENTS.md`
|
|
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
|
|
- `docs/releases/README.md`
|
|
- Requirements, research, formulation, numerical review, interface, test model, implementation, validation, and physics reports
|
|
|
|
## Workflow
|
|
|
|
1. Run gate audit over requirements, research, formulation, interface, TDD test models, Fortran implementation evidence, subroutine validation, and physics sanity.
|
|
2. Build Acceptance Traceability from requirements to tests, artifacts, validation evidence, and limitations.
|
|
3. Record Validation Evidence, including no-Abaqus tests, `python scripts/validate_workspace.py`, and externally generated ODB-extracted CSV comparison evidence.
|
|
4. Record Known Limitations, deferred requirements, unsupported entry points, missing artifacts, unresolved defects, accepted risks, and open items.
|
|
5. Return a verdict: `ready-for-release`, `needs-documentation`, `needs-correction`, `needs-reference-artifacts`, `needs-upstream-decision`, or `blocked`.
|
|
|
|
## Output Contract
|
|
|
|
Produce or revise `docs/releases/<feature-id>-release.md` with Gate Evidence Inventory, Acceptance Traceability, Validation Evidence, Known Limitations, Release Notes Draft, Release Verdict, and No-Change Assertion.
|
|
|
|
## Boundaries
|
|
|
|
- Do not implement code.
|
|
- Do not edit source code or tests.
|
|
- Do not change requirements, formulations, interface contracts, reference artifacts, or tolerance policies.
|
|
- Do not run Abaqus.
|
|
- Do not override failed or missing upstream gates.
|
|
- Do not publish, deploy, package, tag, commit, or externally release anything unless the user explicitly asks.
|
|
|
|
## Quality Gate
|
|
|
|
- Every `must` requirement is traced to passing evidence or a blocker.
|
|
- Missing validation evidence is a blocker, not a limitation.
|
|
- Known limitations are explicit and tied to requirements, models, or artifacts.
|
|
- Release Verdict is internal readiness, not permission to publish.
|
|
|
|
## Handoff
|
|
|
|
Send missing gate evidence to Coordinator Agent, implementation defects to Correction Agent, artifact gaps to Reference Model Agent, and accepted ready evidence to the user.
|