10x-lesson

Appends recurring rules and patterns to a lessons.md register for future reviews.

Updated May 23, 2026
One-click install
npx skills add https://github.com/BMS-kmusial/bms-stream-monitor --skill 10x-lesson-bms-kmusial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-lesson
Source: https://github.com/BMS-kmusial/bms-stream-monitor/tree/main/.claude/skills/10x-lesson
Command: npx skills add https://github.com/BMS-kmusial/bms-stream-monitor --skill 10x-lesson-bms-kmusial

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about 10x-lesson

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record a recurring rule for future code reviews?

Invoke the skill with an optional freeform description of the rule. It interviews you for four fields — Context, Problem, Rule, and Applies to — then appends a formatted entry to context/foundation/lessons.md after your confirmation.

What counts as a lesson versus a one-off bug fix?

A lesson is a recurring rule that would have changed the framing or fix on past work and will keep coming up. Single-incident write-ups do not qualify and should not be captured through this skill.

What happens if lessons.md does not exist yet?

The skill self-bootstraps: it creates context/foundation/lessons.md with a canonical header on first use, then appends your entry. You do not need to run any initialization step first.

Can I edit or delete existing lessons through this skill?

No. The register is strictly append-only; the skill never edits, reorders, or deduplicates existing entries. To revise a rule, open lessons.md and edit it directly — that friction is intentional.

Can I capture multiple lessons in one invocation?

No. The skill captures exactly one entry per invocation to avoid half-written batched entries. Invoke it once per lesson you want to record.