10x-lesson

Capturing recurring engineering rules involves recording the context, problem, rule, and applies-to scope in a persistent lessons register so future planning and review workflows can reuse them. This Skill guides you through structuring each entry and appending it to a markdown knowledge base.

Documenting lessons learned from code review findings requires appending canonical markdown entries to a persistent lessons register. This ensures recurring bug patterns and design pitfalls are preserved as durable rules that can influence later framing, research, planning, and implementation.

An append-only knowledge base for engineering workflow rules is created by bootstrapping a context/foundation/lessons.md file and safely appending one canonical lesson entry at a time. This preserves prior history without rewriting existing rules.

Yes, structured lesson capture prevents recurring design pitfalls by interviewing users for context, problem, rule, and lifecycle scope, then confirming the entry. This process turns repeated mistakes into reusable rules visible during future design and code reviews.

You need to record recurring engineering rules when a repeated bug pattern, design pitfall, or review finding should influence future framing, research, planning, implementation, or review. This ensures hard-won engineering judgment is preserved for future project work.

Yes, capturing lessons learned requires interviewing the user for context, problem, rule, and lifecycle scope before confirming the entry. This ensures each recurring engineering rule is accurately structured before being appended to the lessons register.