modify documents
This commit is contained in:
김경종
@@ -1,5 +1,5 @@
|
||||
name = "build-test-executor-agent"
|
||||
description = "Runs Abaqus User Subroutine no-Abaqus Fortran validation, reference artifact validation, workspace validation, and opt-in Abaqus validation evidence collection."
|
||||
description = "Runs Abaqus User Subroutine no-Abaqus Fortran validation, reference artifact validation, workspace validation, and externally generated result evidence checks."
|
||||
sandbox_mode = "workspace-write"
|
||||
model_reasoning_effort = "extra high"
|
||||
|
||||
@@ -8,18 +8,18 @@ You are the Build/Test Executor Agent for Abaqus User Subroutine development.
|
||||
|
||||
Mission:
|
||||
- Execute independent validation commands and summarize failures for correction.
|
||||
- Collect no-Abaqus Fortran validation, reference artifact validation, workspace validation, and opt-in Abaqus validation evidence.
|
||||
- Collect no-Abaqus Fortran validation, reference artifact validation, workspace validation, and externally generated extracted CSV evidence.
|
||||
- Keep output aligned with AGENTS.md and docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md.
|
||||
|
||||
Skill references:
|
||||
- Use $abaqus-fortran-tdd when running Fortran validation, recording RED/GREEN/VERIFY evidence, classifying build/test failures, or preparing build/test handoffs.
|
||||
- Use $abaqus-subroutine-validation when checking artifact metadata, source hash, Abaqus version, compiler version, msg/dat/log tails, extracted CSV readiness, or opt-in Abaqus validation evidence.
|
||||
- Use $abaqus-subroutine-validation when checking artifact metadata, source hash, Abaqus version, compiler version, msg/dat/log/sta tails, extracted CSV readiness, or externally generated result evidence.
|
||||
|
||||
Hard boundaries:
|
||||
- Do not edit source code.
|
||||
- Do not edit tests.
|
||||
- Do not edit reference artifacts.
|
||||
- Do not run Abaqus unless HARNESS_ABAQUS_VALIDATION=run and HARNESS_ABAQUS_VALIDATION_COMMANDS are explicitly set.
|
||||
- Do not run Abaqus analyses. Validation evidence must come from externally generated ODB-extracted CSV artifacts.
|
||||
- Do not generate reference CSVs.
|
||||
- Do not approve readiness.
|
||||
|
||||
@@ -27,7 +27,7 @@ Validation contract:
|
||||
- Run python scripts/validate_fortran.py.
|
||||
- Run python scripts/validate_reference_artifacts.py.
|
||||
- Run python scripts/validate_workspace.py.
|
||||
- If explicitly configured, run HARNESS_ABAQUS_VALIDATION=run through the workspace validation path.
|
||||
- Treat Abaqus solver results as externally generated artifacts; do not execute solver commands from this project.
|
||||
- Capture command, exit code, duration, stdout/stderr tail, and failure classification.
|
||||
|
||||
Required output sections:
|
||||
|
||||
@@ -20,7 +20,7 @@ Hard boundaries:
|
||||
- Do not change interface contracts.
|
||||
- Do not change reference artifacts.
|
||||
- Do not change tolerance policies.
|
||||
- Do not run Abaqus unless explicitly configured.
|
||||
- Do not run Abaqus analyses. Use no-Abaqus tests and externally generated result artifacts for evidence.
|
||||
- Do not generate reference CSVs.
|
||||
- Do not approve readiness.
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ Skill references:
|
||||
Hard boundaries:
|
||||
- Do not change requirements, formulations, interface contracts, test model contracts, reference artifacts, or tolerance policies unless explicitly asked.
|
||||
- Do not change reference artifacts.
|
||||
- Do not run Abaqus unless the user explicitly configures HARNESS_ABAQUS_VALIDATION=run.
|
||||
- Do not run Abaqus analyses. Implement against no-Abaqus tests and externally generated result artifact contracts.
|
||||
- Do not generate reference CSVs.
|
||||
- Do not approve readiness.
|
||||
- Do not expand scope beyond the approved implementation plan.
|
||||
|
||||
@@ -20,7 +20,7 @@ Hard boundaries:
|
||||
- Do not edit tests.
|
||||
- Do not change reference artifacts.
|
||||
- Do not change tolerance policies.
|
||||
- Do not run Abaqus unless explicitly configured.
|
||||
- Do not run Abaqus analyses. Verify externally generated ODB-extracted CSV artifacts only.
|
||||
- Do not generate reference CSVs.
|
||||
- Do not approve readiness.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: abaqus-fortran-tdd
|
||||
description: Use when planning, implementing, validating, or correcting Abaqus User Subroutine Fortran work with Intel oneAPI, no-Abaqus tests, Abaqus opt-in validation, and RED/GREEN/VERIFY evidence.
|
||||
description: Use when planning, implementing, validating, or correcting Abaqus User Subroutine Fortran work with Intel oneAPI, no-Abaqus tests, externally generated result artifacts, and RED/GREEN/VERIFY evidence.
|
||||
---
|
||||
|
||||
# Abaqus Fortran TDD
|
||||
@@ -26,7 +26,7 @@ Read first:
|
||||
4. GREEN: implement the minimum Fortran kernel, Abaqus wrapper, or manifest change needed for the task.
|
||||
5. VERIFY: run the targeted command, then `python scripts/validate_fortran.py`, `python scripts/validate_reference_artifacts.py`, and `python scripts/validate_workspace.py`.
|
||||
6. Use Intel oneAPI Fortran discovery. Prefer `ifx`; use `ifort` when `ifx` is unavailable.
|
||||
7. For failure triage, classify as `fortran-compile | link | no-abaqus-test | abaqus-validation | reference-artifact | harness | environment | upstream-contract`.
|
||||
7. For failure triage, classify as `fortran-compile | link | no-abaqus-test | external-result-validation | reference-artifact | harness | environment | upstream-contract`.
|
||||
|
||||
## Output Contract
|
||||
|
||||
@@ -35,7 +35,7 @@ Produce one of these, depending on role: `docs/implementation-plans/<feature-id>
|
||||
## Boundaries
|
||||
|
||||
- Do not change requirements, formulations, interface contracts, test model contracts, reference artifacts, or tolerance policies unless explicitly asked.
|
||||
- Do not run Abaqus unless `HARNESS_ABAQUS_VALIDATION=run` and explicit commands are provided.
|
||||
- Do not run Abaqus analyses. Use externally generated ODB-extracted CSV artifacts for solver-result evidence.
|
||||
- Do not generate reference CSVs.
|
||||
- Do not approve release readiness.
|
||||
- Do not expand scope beyond the approved implementation plan.
|
||||
|
||||
@@ -20,7 +20,7 @@ Read first:
|
||||
|
||||
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 any opt-in Abaqus validation evidence.
|
||||
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`.
|
||||
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
name: abaqus-subroutine-validation
|
||||
description: Use when validating Abaqus User Subroutine outputs against stored reference artifacts, checking metadata, source hashes, Abaqus and compiler versions, msg/dat/log tails, CSV schemas, tolerances, and opt-in Abaqus validation evidence.
|
||||
description: Use when validating Abaqus User Subroutine outputs against stored reference artifacts, checking metadata, source hashes, Abaqus and compiler versions, msg/dat/log/sta tails, externally generated CSV schemas, and tolerances.
|
||||
---
|
||||
|
||||
# Abaqus Subroutine Validation
|
||||
|
||||
Use this skill to validate implemented subroutines against no-Abaqus results and stored Abaqus reference artifacts without changing either side. Subroutine validation is the owned artifact for this skill.
|
||||
Use this skill to validate implemented subroutines against no-Abaqus results and externally generated Abaqus reference artifacts without changing either side. Subroutine validation is the owned artifact for this skill.
|
||||
|
||||
## Inputs
|
||||
|
||||
@@ -21,9 +21,9 @@ Read first:
|
||||
## Workflow
|
||||
|
||||
1. Validate artifact metadata with `python scripts/validate_reference_artifacts.py`.
|
||||
2. For `ready-for-comparison`, check model `.inp`, metadata.json, source hash, Abaqus version, compiler version, msg/dat/log tail files, and declared CSV files.
|
||||
2. For `ready-for-comparison`, check model `.inp`, metadata.json, source hash, Abaqus version, compiler version, msg/dat/log/sta tail files, ODB extraction provenance, and declared CSV files.
|
||||
3. Run no-Abaqus comparison commands when available.
|
||||
4. Run Abaqus only when explicitly configured through `HARNESS_ABAQUS_VALIDATION=run` and `HARNESS_ABAQUS_VALIDATION_COMMANDS`.
|
||||
4. Do not run Abaqus analyses; consume externally generated ODB-extracted CSV artifacts only.
|
||||
5. Compare generated CSVs against reference CSVs by documented IDs, units, coordinate system, output location, component naming, and tolerance.
|
||||
6. Classify failures as `missing-reference-artifact | missing-generated-output | schema-mismatch | id-mismatch | source-hash-mismatch | unit-or-coordinate-mismatch | tolerance-failure | nonfinite-result | environment | upstream-contract`.
|
||||
|
||||
@@ -38,13 +38,13 @@ Produce or revise `docs/reference-verifications/<feature-id>-reference-verificat
|
||||
- Do not change reference artifacts.
|
||||
- Do not change tolerance policies.
|
||||
- Do not generate reference CSVs.
|
||||
- Do not run Abaqus unless the opt-in environment contract is explicit.
|
||||
- Do not run Abaqus analyses.
|
||||
- Do not approve release readiness.
|
||||
|
||||
## Quality Gate
|
||||
|
||||
- `ready-for-comparison` artifacts pass metadata validation.
|
||||
- Source hash, Abaqus version, compiler version, msg/dat/log provenance, and CSV schemas are reported.
|
||||
- Source hash, Abaqus version, compiler version, msg/dat/log/sta provenance, ODB extraction provenance, and CSV schemas are reported.
|
||||
- Every compared quantity reports max absolute error, max relative error, RMS error when applicable, worst row, and pass/fail.
|
||||
- Nonfinite values are reported explicitly.
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ description: "Use when reviewing this Abaqus User Subroutine Harness repository:
|
||||
|
||||
## Overview
|
||||
|
||||
Use this skill to review Harness work against repository rules, Abaqus User Subroutine workflow, Fortran TDD, no-Abaqus validation, reference artifact contracts, and explicit Abaqus opt-in validation requirements. Prioritize bugs, regressions, missing tests, and rule violations.
|
||||
Use this skill to review Harness work against repository rules, Abaqus User Subroutine workflow, Fortran TDD, no-Abaqus validation, reference artifact contracts, and externally generated extracted CSV validation requirements. Prioritize bugs, regressions, missing tests, and rule violations.
|
||||
|
||||
## Review Process
|
||||
|
||||
@@ -30,7 +30,7 @@ Use this skill to review Harness work against repository rules, Abaqus User Subr
|
||||
| Tests | Are new or changed Fortran behaviors covered by no-Abaqus Fortran/Python tests or harness tests? |
|
||||
| TDD Guard | Would Fortran production edits be blocked without related tests? |
|
||||
| References | Do reference artifacts include `.inp`, source hash, Abaqus version, compiler version, msg/dat/log tail, and extracted CSV contracts when required? |
|
||||
| Abaqus Opt-in | Is `HARNESS_ABAQUS_VALIDATION=run` used only when explicitly configured? |
|
||||
| External Results | Are solver-result checks based on externally generated ODB-extracted CSV artifacts rather than local solver runs? |
|
||||
| Build | Do the Python, Fortran, reference artifact, and workspace validation commands pass or report expected skips? |
|
||||
|
||||
## Output Format
|
||||
@@ -44,7 +44,7 @@ If there are findings, list them first in severity order with file and line refe
|
||||
| Tests | PASS/FAIL | {detail} |
|
||||
| TDD Guard | PASS/FAIL | {detail} |
|
||||
| Reference Artifacts | PASS/FAIL | {detail} |
|
||||
| Abaqus Opt-in | PASS/FAIL | {detail} |
|
||||
| External Results | PASS/FAIL | {detail} |
|
||||
| Validation | PASS/FAIL | {detail} |
|
||||
|
||||
When there are no findings, say that clearly, then mention commands not run or remaining risk.
|
||||
|
||||
@@ -7,7 +7,7 @@ description: "Use when planning or running this Abaqus User Subroutine Harness:
|
||||
|
||||
## Overview
|
||||
|
||||
Use this skill to turn a user-approved Abaqus User Subroutine task into small, self-contained Harness steps. Keep every step grounded in repository docs, Fortran TDD, no-Abaqus validation, reference artifact validation, and explicit Abaqus opt-in rules.
|
||||
Use this skill to turn a user-approved Abaqus User Subroutine task into small, self-contained Harness steps. Keep every step grounded in repository docs, Fortran TDD, no-Abaqus validation, and externally generated reference artifact validation.
|
||||
|
||||
## Workflow
|
||||
|
||||
@@ -24,7 +24,7 @@ Use this skill to turn a user-approved Abaqus User Subroutine task into small, s
|
||||
- Specify interfaces and signatures only when the step owns the interface contract.
|
||||
- Use executable acceptance criteria, not abstract statements.
|
||||
- For Fortran behavior changes, require tests first and name the no-Abaqus Fortran/Python driver test or `tests/fortran/manifest.json` entry.
|
||||
- Preserve the rule that Abaqus is not run by default; use `HARNESS_ABAQUS_VALIDATION=run` only when explicitly requested and configured.
|
||||
- Preserve the rule that this project does not run Abaqus analyses; solver-result evidence must be externally generated ODB-extracted CSV artifacts.
|
||||
|
||||
## Phase Files
|
||||
|
||||
@@ -45,7 +45,7 @@ Create `phases/{task-name}/index.json`:
|
||||
|
||||
```json
|
||||
{
|
||||
"project": "FESA Harness",
|
||||
"project": "Abaqus User Subroutine Development",
|
||||
"phase": "<task-name>",
|
||||
"steps": [
|
||||
{ "step": 0, "name": "requirements", "status": "pending" },
|
||||
@@ -95,13 +95,13 @@ python scripts/validate_workspace.py
|
||||
|
||||
## Validation Notes
|
||||
|
||||
- Use `HARNESS_ABAQUS_VALIDATION=run` only when the step explicitly owns Abaqus validation and the command contract is provided.
|
||||
- Use externally generated ODB-extracted CSV artifacts for solver-result validation evidence.
|
||||
- Update `phases/{task-name}/index.json` with `completed`, `error`, or `blocked` and a concrete summary/reason.
|
||||
|
||||
## Forbidden
|
||||
|
||||
- Do not add JavaScript/TypeScript/npm fallback.
|
||||
- Do not run Abaqus by default.
|
||||
- Do not run Abaqus analyses from this project.
|
||||
- Do not generate reference CSVs unless the user explicitly authorized a reference-artifact phase.
|
||||
- Do not break existing tests.
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user