What problem does it solve? Recurring bugs and design pitfalls get rediscovered repeatedly because there is no durable place to record the rules learned from them. This Skill captures a recurring rule into context/foundation/lessons.md so future planning, implementation, and review runs re-read it as a prior. ## Core Features & Use Cases - Structured Interview: Collects four fields (Context, Problem, Rule, Applies to) via guided questions so the user writes the rule wording, not the tool. - Canonical Entry Format: Appends a standardized markdown entry with an H2 rule title that future skills can scan quickly. - Self-Bootstrapping: Creates lessons.md with the canonical header on first use, and appends only — never edits or reorders existing entries. - Use Case: After noticing that feature flags keep shipping without kill dates, invoke the skill to record "Always give feature flags a kill date" as a recurring rule that future /10x-plan and /10x-impl-review runs will weigh. ## Quick Start Ask the assistant to record a recurring lesson, for example: capture a lesson that feature flags should always have a kill date.