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-requirements-baseline/SKILL.md
+8 -4
View File
@@ -24,7 +24,8 @@ Read these first:
3. Convert requested behavior into `shall` statements with ids like `FESA-REQ-<FEATURE>-###`.
4. Define verification quantities: displacement, reaction, element force, stress, strain, energy, or residual.
5. Record Tolerance Policy values or mark them `needs-user-decision`.
6. Record Reference Artifact Requirements under `references/<feature-id>/`.
6. Record a minimal Reference Case: exact existing input/required CSV paths, blocking and
warning-only quantities, HDF5 projection, source-ID/component matching, and tolerance.
7. Build a Requirement Verification Matrix that maps requirement, source, verification method, acceptance criteria, tolerance, downstream agents, and status.
8. Keep unresolved decisions visible as open issues; do not hide gaps behind vague wording.
@@ -37,7 +38,7 @@ Produce or revise `docs/requirements/<feature-id>.md` with:
- Input and Output Requirements
- Verification Quantities
- Tolerance Policy
- Reference Artifact Requirements
- Reference Case Requirements
- Requirement Verification Matrix
- Open Questions and Downstream Handoff
@@ -53,8 +54,11 @@ Produce or revise `docs/requirements/<feature-id>.md` with:
## Quality Gate
- Every `must` requirement has a verification method and acceptance criteria.
- Every numerical requirement has units, coordinate system, and tolerance or an explicit owner for the decision.
- Every reference-comparison requirement names required artifacts.
- Every numerical solver-output requirement has units, coordinates, and tolerance when applicable.
- Every reference-comparison requirement names exact required files, compared components,
source identity, blocking/warning behavior, and tolerance.
- Do not require canonical names, README, metadata, provenance, or CSVs for quantities outside
the feature acceptance boundary.
- Words like "accurate", "fast", and "Abaqus-like" are converted into measurable criteria or open questions.
## Handoff