docs-maintenance

To automate documentation maintenance, execute the /sync-docs command after finishing a task to trigger updates across AGENTS.md, roadmaps, and notepads. This sync procedure ensures your documentation reflects source changes consistently without manual intervention.

The best way to archive completed plans is to move finished files to the .sisyphus/plans/archive/ directory. This archival workflow keeps active plan folders clean while maintaining traceability of past work and completed roadmaps.

You map code changes to documentation updates using an Update Trigger Matrix. This matrix standardizes the governance process by specifying exactly which docs require updates when specific code modifications occur across your project.

You need AGENTS.md references to maintain a proper documentation hierarchy. The governance process uses AGENTS.md alongside provided templates to enforce consistent content formats, stable patterns, and standardized references across all project documentation.

You should append notes to .sisyphus/notepads during active development to capture ongoing work context. This notepad usage workflow ensures scattered traceability details are recorded before the final plan archiving process begins.

Documentation becomes inconsistent across modules without governance due to unclear triggers for syncing and scattered archive processes. Standardizing update triggers and sync procedures ensures modules follow the same formatting rules and quality checklists.