modify documents

.codex/skills/fesa-phase-planning/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: fesa-phase-planning
+description: Create or review FESA Harness phase plans and self-contained step files after readiness blockers are understood.
+---
+
+# FESA Phase Planning
+
+Use this skill when drafting or reviewing `phases/` work plans for FESA.
+
+## Read First
+
+- `/AGENTS.md`
+- `/PROGRESS.md`
+- `/PLAN.md`
+- `/docs/README.md`
+- `/docs/HARNESS_ENGINEERING.md`
+- `/docs/PRD.md`
+- `/docs/ARCHITECTURE.md`
+- `/docs/ADR.md`
+- `/docs/NUMERICAL_CONVENTIONS.md`
+- `/docs/ABAQUS_INPUT_SUBSET.md`
+- `/docs/VERIFICATION_PLAN.md`
+- `/docs/RESULTS_SCHEMA.md`
+- `/docs/MITC4_FORMULATION.md`
+
+## Workflow
+
+1. Run the readiness check first.
+2. Use the repo `harness-workflow` skill when generating phase files.
+3. Keep each step scoped to one layer or module where possible.
+4. Make each `stepN.md` executable in a fresh Codex session.
+5. Include a sprint contract section following `/docs/HARNESS_ENGINEERING.md`.
+6. Include acceptance commands and explicit prohibitions.
+7. Do not hide unresolved reference, build, or MITC4 decisions inside implementation tasks.
+
+## Phase Shape
+
+- Start with project skeleton, build/test harness, and core types only after readiness blockers are accepted.
+- Preserve the documented sequence: Domain, parser, diagnostics, DofManager, math adapters, results, reference comparator, MITC4, assembly, linear static path.
+- For implementation phases, plan the Planner -> Generator -> Evaluator loop explicitly enough that an independent evaluator can pass/fail each step.