What problem does it solve? Teams lose track of decisions, bugs, scope changes, and progress across sessions, making retrospectives, status reports, and session resumption unreliable. This Skill creates a persistent, append-only project memory in a .logs/ directory so nothing important is forgotten. ## Core Features & Use Cases - Structured Logging Protocol: Eight append-only markdown logs (activity, decisions, issues, risks, corrections, communications, sessions, metrics) with a standardized entry format and automatic trigger table defining who logs what and when. - KPI Tracking & Health Scoring: Defines ten KPIs (velocity, completion rate, bug rate, scope creep, estimation accuracy, etc.) plus a 0-100 health score computed from open issues, blockers, and risks. - Automated Status Reports: A Python report generator parses the logs and produces a formatted status report with progress, quality metrics, open items, and recent decisions. - Use Case: When resuming work after a break, the Skill reads the last SESSION_END entry and presents what was completed, what is in progress, and what is blocked, so the session continues without re-explaining context. ## Quick Start Ask the assistant to initialize project logging and show the current project status report from the .logs directory.
