What problem does it solve? Multi-session tasks accumulate scattered progress, completion, and handoff reports across folders, causing information drift, duplication, and loss. This Skill enforces a single-source-of-truth report structure so every task maintains one master plan with chaptered documents instead of ever-growing piles of standalone report files. ## Core Features & Use Cases - Centralized Report Governance: All reports for a task live in one folder with a 00-master-plan document plus numbered chapter documents; updates merge into existing chapters rather than creating new files. - Safe Consolidation and Deletion Flow: A five-step process (inventory, build skeleton, deep-merge content, grep-verify before deletion, archive to _archive) prevents information loss when consolidating scattered legacy reports. - HTML Report Paradigms: Multi-page architecture with a single index entry and shared report-assets (css/js/pages), Mermaid diagrams via CDN, and a six-element module overview card specification (number, name, three tag groups, description, notes, update time) with equal-height cards. - Use Case: When finishing a project phase, update the corresponding chapter document and its HTML page instead of writing a new dated completion report; when inheriting a messy task folder, consolidate 25+ scattered reports into the master-plan structure with zero content loss. ## Quick Start Ask the AI to produce or update a task progress report following the report-paradigm discipline, merging it into the existing chapter document rather than creating a new file.
