modify documents

2026-05-01 02:29:30 +09:00
parent 4b89f4aa96
commit e99b5b8eff
65 changed files with 2814 additions and 72 deletions
@@ -0,0 +1,41 @@
+---
+name: fesa-readiness
+description: Check FESA Phase 1 readiness before implementation planning or coding, especially reference artifacts, MITC4 open decisions, result outputs, and build-system blockers.
+---
+
+# FESA Readiness
+
+Use this skill before drafting implementation phases, starting solver code, or deciding whether Phase 1 can proceed.
+
+## Read First
+
+- `/AGENTS.md`
+- `/PROGRESS.md`
+- `/PLAN.md`
+- `/docs/README.md`
+- `/docs/VERIFICATION_PLAN.md`
+- `/docs/RESULTS_SCHEMA.md`
+- `/docs/MITC4_FORMULATION.md`
+- `/docs/NUMERICAL_CONVENTIONS.md`
+- `/docs/ABAQUS_INPUT_SUBSET.md`
+
+## Workflow
+
+1. Compare `/PLAN.md` Phase 1 readiness tasks with the Implementation Readiness Checklist in `/docs/README.md`.
+2. Classify each item as ready, blocked, explicitly deferred, or unknown.
+3. Confirm that reference artifacts under `references/` do not require local Abaqus execution.
+4. Confirm that at least one `*_displacements.csv` can drive automated `U` comparison, and flag missing `RF` artifacts if reaction verification depends on Abaqus output.
+5. Confirm that MITC4 baseline formulation decisions are not being filled from memory.
+6. Identify the smallest next decision or artifact needed.
+
+## Output
+
+- Lead with the readiness verdict: ready, blocked, or partial.
+- Include blockers and the exact files that should be updated.
+- If work is completed during the turn, update `PROGRESS.md`.
+- If future tasks change, update `PLAN.md`.
+
+## Do Not
+
+- Do not start implementation while unresolved readiness blockers remain unless the user explicitly accepts them as deferred.
+- Do not treat undocumented formulas or reference values as authoritative.