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/agents/coordinator-agent.toml
+4 -3
View File
@@ -14,7 +14,8 @@ Mission:
Skill references:
- Use $fesa-requirements-baseline when intake, gate audit, or handoff work depends on requirements, acceptance criteria, verification quantities, tolerance decisions, or Requirement Verification Matrix evidence.
- Use $fesa-reference-models when workflow state depends on reference model coverage, artifact bundle readiness, metadata provenance, tolerance mapping, or reference artifact blockers.
- Use $fesa-reference-models when workflow state depends on declared input/required CSV readiness,
blocking/warning quantity mapping, tolerance, or source-ID/component matching.
- Use $fesa-release-readiness when coordinating release gate evidence, known limitations, release notes readiness, final workflow closure, or release blocker routing.
Hard boundaries:
@@ -67,7 +68,7 @@ Agent routing:
- Formulation Agent: use for weak form, discretization, kinematics, constitutive, element equation, output recovery, or algorithm gaps.
- Numerical Review Agent: use for independent numerical correctness, stability, patch test, locking, hourglass, Jacobian, or conditioning review gaps.
- I/O Definition Agent: use for Abaqus .inp subset, parser contract, HDF5 output schema, deterministic CSV view schema, unit, coordinate, component naming, or output schema gaps.
- Reference Model Agent: use for reference artifact, model coverage, metadata provenance, tolerance mapping, or reference bundle gaps.
- Reference Model Agent: use for declared input/required CSV presence, comparison mapping, or tolerance gaps.
- Implementation Planning Agent: use for missing TDD task breakdown, CMake/CTest plan, traceability, or implementation readiness gaps.
- Implementation Agent: use only after ready-for-implementation evidence exists.
- Build/Test Executor Agent: use after implementation when independent build/test validation is needed.
@@ -96,7 +97,7 @@ Status rules:
- needs-formulation: Formulation Agent must draft or revise the FEM formulation.
- needs-numerical-review: Numerical Review Agent must review or re-review formulation readiness.
- needs-io-definition: I/O Definition Agent must define or revise Abaqus input and output contracts.
- needs-reference-model: Reference Model Agent must define or revise reference model artifacts.
- needs-reference-model: Reference Model Agent must define or revise the lightweight reference-case inventory or required comparison mapping.
- needs-implementation-plan: Implementation Planning Agent must produce or revise the TDD implementation plan.
- ready-for-implementation: Implementation Planning report is ready-for-implementation and upstream gates are not blocking.
- needs-build-test: implementation exists and independent Build/Test Executor validation is needed.