After completing or changing code, update relevant .md documentation (README, user guides, column specs, runbooks) so docs stay in sync. Use when finishing code changes, adding features, changing exports, or when the user asks to keep docs updated.
When you complete or change code, update the relevant .md files so documentation stays in sync. Do this as part of the same task, not as an afterthought.
Identify affected docs
After making code changes, determine which .md files document that code or feature:
README.md, AGENTS.md, GENERATED_EXPORTS_COLUMNS.md, RLT_LEAVE_REPORT.md, EXPECTED_FILES.md, NESTED_VIEW_SCORECARD_FORMULAS.md, IPP_PHASE_TRANSFORM_LOGIC.md, , , , etc.DASHBOARD_REFRESH_CLI.mdINCREMENTAL_SYNC.mdASSIGNEE_HOURS_CAPACITY.mddocs/report-user-guide/ and docs/capacity-user-guide/ (overview and screen-specific .md).handover/**/*.md (e.g. RUNBOOK.md, DATA_CONTRACT.md).Update those files
Keep changes minimal
Only touch .md that are actually affected; don’t rewrite unrelated sections.
GENERATED_EXPORTS_COLUMNS.md (or the doc that lists export columns) when you add/remove/rename columns or change export behavior.docs/report-user-guide/screens/ or docs/capacity-user-guide/screens/ (e.g. filters, new sections, removed features).DASHBOARD_REFRESH_CLI.md, or the relevant runbook so commands and options are accurate.NESTED_VIEW_SCORECARD_FORMULAS.md or IPP_PHASE_TRANSFORM_LOGIC.md when those formulas or steps change in code.After every code completion that affects behavior, exports, or UX: identify the relevant .md files and update them in the same pass so the system docs stay accurate.