baram2584/FESADev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: align FESA agents with minimal reference cases

Browse Source
This commit is contained in:
KOKO\Mimi
2026-08-12 03:31:08 +09:00
parent 5c08f1cf83
commit 188bf31e44
27 changed files with 438 additions and 593 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/skills/fesa-release-readiness/SKILL.md
+7 -3
View File
@@ -24,8 +24,10 @@ Read these first:
1. Follow `GATE AUDIT -> TRACEABILITY CHECK -> RELEASE DOCUMENTATION -> RELEASE VERDICT`.
2. GATE AUDIT: confirm required reports exist, share the same `feature_id`, are not stale or contradictory, and carry required pass statuses.
3. Require `pass-for-reference-verification`, `pass-for-physics-evaluation`, and `pass-for-release-agent`.
4. TRACEABILITY CHECK: confirm each `must` requirement maps to acceptance criteria, test evidence, reference model evidence, and release scope.
5. Record deferred requirements, unsupported Abaqus keywords, incomplete artifacts, unresolved defects, accepted risks, and known limitations.
4. TRACEABILITY CHECK: confirm each `must` requirement maps to acceptance criteria, test evidence,
feature-required reference evidence when applicable, and release scope.
5. Record deferred requirements, unsupported Abaqus keywords, missing required comparison files,
unresolved defects, accepted risks, and known limitations.
6. RELEASE DOCUMENTATION: prepare a release checklist, Known Limitations, and Release Notes Draft.
7. RELEASE VERDICT: issue `ready-for-release` only when all required evidence is present and passing.
@@ -59,7 +61,9 @@ Produce or revise `docs/releases/<feature-id>-release.md` with:
- Do not issue `ready-for-release` without `pass-for-release-agent`, `pass-for-physics-evaluation`, and `pass-for-reference-verification`.
- Every `must` requirement traces to release scope, acceptance criteria, test or reference evidence, and final disposition.
- Known limitations and deferred issues are included in the Release Notes Draft.
- Missing evidence, contradictory reports, unresolved defects, incomplete artifacts, or unavailable validation commands block release readiness.
- Missing required evidence, contradictory reports, unresolved defects, missing declared comparison
files, or unavailable validation commands block release readiness. Canonical naming, README,
metadata, provenance, or unrequested portfolio expansion do not.
## Handoff