What problem does it solve? After merging a PR or finishing a development session, valuable observations about codebase patterns, developer friction, and suspicious areas get lost because they fell outside the PR's scope. This Skill captures those journey-specific insights as a structured retrospective, distinct from code review. ## Core Features & Use Cases - Pattern Synthesis: Groups individual observations into systemic themes (e.g., inconsistent error handling across routes) rather than listing isolated bugs. - Breadcrumb Trails: Flags unverified areas suspected of having similar issues, framed as investigation leads with reasoning. - Friction & Positive Pattern Reporting: Documents what slowed the work down and what conventions are worth preserving, with impact/effort-rated next steps. - Use Case: After merging a feature PR, run the retro to produce a structured report of systemic patterns and optionally publish each finding as a labeled GitHub Issue via --output github. ## Quick Start Ask the assistant to run a development retro on the work just completed and surface any patterns, friction points, and recommended follow-ups.
