docs-maintenance-after-work

To keep documentation in sync after a release, you can automate post-implementation docs maintenance by running the skill against your recent work. It coordinates plan synchronization and writer agents to align living documentation with evolving code.

The best way to automate documentation updates is to provide inputs like diff, changed_files, and work_summary. The skill processes these inputs to focus updates on relevant areas and enforce a structured documentation quality gate.

Cross-document consistency works by coordinating specialized doc writers to validate and align API references, architectural diagrams, and user guides with the current implementation, ensuring accuracy across all project documentation.

Yes, you can enforce a documentation quality gate after implementation. The skill applies structured checks to ensure specificity, clarity, accuracy, and cross-document consistency across your updated living documentation.

You need to run post-implementation docs maintenance after finishing a development task or executing a work-plan. It synchronizes project documentation with the latest implementation changes and performs necessary quality checks.

Project documentation drifts after code changes because manual updates often lag behind implementation. Automating post-implementation docs maintenance prevents this drift by keeping living documentation accurate, trustworthy, and aligned with evolving code.