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

update agent, skill and scripts

Browse Source
This commit is contained in:
KOKO\Mimi
2026-09-07 01:15:26 +09:00
parent 42a4847da5
commit d7e9629640
38 changed files with 476 additions and 2946 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/skills/fem-research-evidence/SKILL.md
+4 -30
View File
@@ -1,38 +1,12 @@
---
name: fem-research-evidence
description: Use when a structural FEM feature needs source-backed theory, benchmark, verification, or reference-convention evidence before formulation.
description: Gather source-backed FEM theory, benchmark, or observable reference-convention evidence for a concrete solver decision.
---
# FEM Research Evidence
Build an auditable evidence brief while keeping documented fact, calculation, inference, and unresolved questions distinct.
Answer only the research questions needed by the assigned decision. Prefer standards, primary literature, authoritative textbooks, official verification guides, and public vendor documentation. Separate sourced fact, calculation, inference, and remaining gap; record stable locators and applicability limits.
## Inputs
Identify useful analytical, invariant, patch, convergence, manufactured, or published benchmark cases without treating a single solver comparison as proof. Abaqus material supports only documented observable syntax, semantics, outputs, and verification conventions, never its private internals. Use `fem-theory-query` only when the configured vault is the requested source.
- `docs/<feature-id>/requirements.md`
- Project instructions and user-supplied sources
- Existing research brief and reference artifacts, read-only
## Workflow
1. Derive research questions from requirement IDs and open decisions.
2. Prefer governing standards, primary literature, authoritative textbooks, and official vendor documentation; record reliability and applicability.
3. Summarize only the theory needed downstream. Identify analytical solutions, patch tests, convergence studies, manufactured solutions, and published benchmarks appropriate to the analysis family.
4. State what each source or case can and cannot verify. Mark unsupported claims as inference or evidence gaps.
When a configured FEM vault is the requested evidence source, use `fem-theory-query`. Apply [workflow and decision authority](../fem-requirements-baseline/references/workflow-and-decisions.md) to product references and [evidence and handoff](../fem-requirements-baseline/references/evidence-and-handoff.md) to the result.
## Output
Follow [Feature document management](../../../docs/FEATURE_DOCUMENTATION.md): read the Coordinator's
feature context, keep main reports concise, and link necessary owned details in the same feature folder.
Create or revise `docs/<feature-id>/research.md` with research questions, source inventory and reliability, theory findings, candidate verification cases, applicability limits, conflicts, gaps, and downstream handoff.
## Evidence
Trace every material claim to a stable locator. For a project-selected reference solver or format, use official public documentation for observable syntax, semantics, output, or procedure only. Record edition/version and access date when behavior can vary.
## Boundary
Do not finalize the mathematical formulation, set tolerance values, design APIs or schemas, implement code, alter reference artifacts, or run an external licensed solver without explicit authorization. Do not treat agreement with one product as proof of correctness or infer its undocumented internals.
Return concise evidence, candidate verification cases, and gaps. Do not finalize formulations, tolerances, schemas, code, or reference artifacts.