NINI
42 lines
1.1 KiB
Markdown
42 lines
1.1 KiB
Markdown
---
|
|
name: fesa-review
|
|
description: Review FESA changes against repository guardrails, technical dossier docs, TDD expectations, and validation requirements.
|
|
---
|
|
|
|
# FESA Review
|
|
|
|
Use this skill for repository-grounded review of docs, `.codex` extensions, phase plans, or implementation patches.
|
|
|
|
## Read First
|
|
|
|
- `/AGENTS.md`
|
|
- `/PROGRESS.md`
|
|
- `/PLAN.md`
|
|
- `/docs/README.md`
|
|
- `/docs/HARNESS_ENGINEERING.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`
|
|
- The changed files under review.
|
|
|
|
## Checklist
|
|
|
|
- Architecture and ADR compliance.
|
|
- Numerical convention compliance.
|
|
- Abaqus subset discipline.
|
|
- Result schema compatibility.
|
|
- MITC4 formulation traceability.
|
|
- TDD or reference verification coverage.
|
|
- Sprint contract compliance when implementation work is under review.
|
|
- PLAN.md and PROGRESS.md synchronization.
|
|
|
|
## Output
|
|
|
|
- Lead with findings ordered by severity.
|
|
- Include concrete file references and the risk behind each finding.
|
|
- If no material issues exist, say so and list remaining evidence gaps.
|