31 lines
1.0 KiB
Markdown
31 lines
1.0 KiB
Markdown
---
|
|
name: fesa-adr-update
|
|
description: Draft or revise FESA ADRs when architecture, numerical conventions, dependencies, result schema, or phase scope decisions change.
|
|
---
|
|
|
|
# FESA ADR Update
|
|
|
|
Use this skill when a design decision should become durable project policy.
|
|
|
|
## Read First
|
|
|
|
- `/AGENTS.md`
|
|
- `/PROGRESS.md`
|
|
- `/PLAN.md`
|
|
- `/docs/ARCHITECTURE.md`
|
|
- `/docs/ADR.md`
|
|
- The topic-specific design document.
|
|
|
|
## Workflow
|
|
|
|
1. Identify whether the change is a new decision, a clarification, or a superseding decision.
|
|
2. Capture context, decision, consequences, alternatives considered, and validation impact.
|
|
3. Update related docs only when needed to avoid drift.
|
|
4. Add follow-up tasks to `PLAN.md`.
|
|
5. Record completed ADR work in `PROGRESS.md`.
|
|
|
|
## Decision Quality Bar
|
|
|
|
- Decisions should preserve runtime polymorphism, documented state ownership, DofManager ownership, adapter boundaries, step/frame/history outputs, and reference-driven verification.
|
|
- If a decision weakens those policies, document why and what test or reference coverage will protect it.
|