NINI
1015 B
1015 B
name, description
| name | description |
|---|---|
| fesa-doc-sync | Keep FESA documentation, PLAN.md, and PROGRESS.md synchronized after design, planning, or Codex extension changes. |
FESA Doc Sync
Use this skill whenever documentation, .codex extension files, phase files, or planning state changes.
Read First
/AGENTS.md/PROGRESS.md/PLAN.md/docs/README.md- Any changed docs, phase files, or
.codexfiles.
Workflow
- Put completed work, changed files, verification, and residual risks in
PROGRESS.md. - Put future tasks, open decisions, and changed ownership in
PLAN.md. - Keep historical notes out of
PLAN.md. - Keep future task lists out of
PROGRESS.md. - Check whether documentation indexes or agent instructions need updates.
Verification
- Parse changed TOML, JSON, or YAML-like frontmatter when practical.
- Run
python scripts/validate_workspace.pyafter edits.
Output
- Summarize only the meaningful sync changes.
- Call out any stale or contradictory state that remains.