sprint-docs-sync

Automate sprint documentation updates by triggering a batch synchronization that reads existing status files and applies updates to PROJECT-STATUS and NIGHTLY-RUN-LOG. This ensures sprint status and completion notes are aligned across repositories after sprint completion.

Syncing sprint status boards and release notes is handled by batch documentation synchronization across docs/status and board references. The process reads existing status files and updates project documentation to reflect new features and changes consistently.

Sprint docs sync is designed for agile teams requiring consistent documentation, status boards, and release notes. It ensures traceable integrity history by applying structured updates to PROJECT-STATUS and NIGHTLY-RUN-LOG files after each sprint.

Trigger a docs sync by running a sprint completion trigger, which automates the batch update of project docs and reflects the latest status across boards. This action applies updates to status files and completion notes automatically.

Yes, you can update NIGHTLY-RUN-LOG and PROJECT-STATUS files automatically. The skill reads existing status files and applies targeted updates to these documents to maintain traceable integrity history and consistent project documentation.

Automating sprint docs updates is limited to post-sprint synchronization of documentation, status boards, and release notes. It requires existing status files to read from and applies updates specifically to PROJECT-STATUS and NIGHTLY-RUN-LOG for traceable integrity history.