What problem does it solve? Teams and solo builders lose valuable lessons when session friction, failures, and wins go unrecorded. This Skill continuously listens for notable signals during guided and piloted sessions, captures them as structured observations, and converts them into actionable retrospective entries with root causes and proposed fixes. ## Core Features & Use Cases - Always-on listening mode: Detects framework signals (stuck protocols, repeated review failures, rollbacks), solo-expressed dissatisfaction, and explicit flags, writing one-line captures to both a session buffer and a per-project persistent store. - Phase-end retro processing: Groups unprocessed observations into patterns, one-offs, and positives, then produces structured entries with root cause, impact, proposed fix, and a decision on whether to update the skill now or queue it. - Project vs framework classification: Distinguishes project-specific adjustments from framework-level improvements, routing the latter to a queued improvements log. - Use Case: During a build phase, code review fails twice on the same data check. The observation is captured immediately, and at phase end the retro identifies the pattern, traces the root cause to an ambiguous instruction in a skill file, and proposes the exact sentence to change. ## Quick Start Ask the assistant to run the retrospective and process this session's flagged observations into improvement entries.
