Sync project documentation (PRD, ROADMAP, NOTICED_ISSUES) after code changes. Enforces the update rules from CLAUDE.md. Use after implementing features, fixing bugs, or completing roadmap tasks.
After code changes, ensure all canonical docs stay in sync per CLAUDE.md rules.
Review recent changes to understand scope:
git diff --name-only HEAD~1..HEAD 2>/dev/null || git diff --name-only --cached
git log -3 --oneline
Apply these rules from CLAUDE.md:
| Change Type | Update Required |
|---|---|
| Feature added/changed/removed | docs/PRD.md |
| Roadmap task completed | docs/ROADMAP.md |
| Data quality issue fixed/found |
docs/NOTICED_ISSUES.md |
| User-facing docs affected | Corresponding wiki page |
Read each doc identified in step 2 — skip docs that don't need changes.
docs/PRD.md — canonical feature descriptionsdocs/ROADMAP.md — task statuses with IDs like 1.A1, 2.B3, 4.C3docs/NOTICED_ISSUES.md — data quality and UI issues with resolution statusFor each doc:
✅ **Complete** with a brief note on what was done.**[RESOLVED]** with a one-line fix description, or add new **[OPEN]** issues discovered during work. Follow the file's existing formatting conventions (strikethrough on resolved issue titles, bold status tags).If the scope of changes is ambiguous, ask the user before editing.
List exactly which files were updated and what changed. If no doc updates were needed, say so explicitly.