What problem does it solve? Non-obvious technical insights discovered during debugging or design work are often lost once a session ends, leaving no record of why a solution worked. This Skill preserves those breakthroughs as structured, searchable Markdown documents before the context evaporates. ## Core Features & Use Cases - Structured Capture: Prompts for Problem, Insight, Implementation, and Impact, then writes a dated document to docs/breakthroughs/YYYY-MM-DD-<slug>.md with Date, Tags, and Project metadata. - Quality Bar: Applies a "would this surprise a senior engineer?" filter so routine fixes and well-documented knowledge are excluded, keeping the archive high-signal. - Convention Promotion: When an insight implies a reusable pattern, it proposes an update to the relevant rules/ file so one-off discoveries can become team conventions. - Use Case: After discovering that a retry storm was caused by clock skew between pods rather than backoff configuration, trigger the skill to record the insight with its root cause and quantified impact for future reference. ## Quick Start Ask the assistant to capture a breakthrough by saying "key insight: the retry storm was caused by clock skew between pods, not the backoff config" and answer the prompts for problem, insight, implementation, and impact.
