---
name: fesa-doc-sync
description: 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 `.codex` files.

## Workflow

1. Put completed work, changed files, verification, and residual risks in `PROGRESS.md`.
2. Put future tasks, open decisions, and changed ownership in `PLAN.md`.
3. Keep historical notes out of `PLAN.md`.
4. Keep future task lists out of `PROGRESS.md`.
5. 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.py` after edits.

## Output

- Summarize only the meaningful sync changes.
- Call out any stale or contradictory state that remains.