bmad-extract-lessons-from-adrs

Analyze ADRs, retrospectives, and postmortems to summarize recurring failure patterns.

2|Updated Apr 19, 2026

Search Tags:#pattern detection #incident analysis #lessons #retrospectives #adrs #postmortems

Ready to run

npx skills add https://github.com/Wizarck/openTrattOS --skill bmad-extract-lessons-from-adrs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-extract-lessons-from-adrs
Source: https://github.com/Wizarck/openTrattOS/tree/main/skills/bmad-extract-lessons-from-adrs
Command: npx skills add https://github.com/Wizarck/openTrattOS --skill bmad-extract-lessons-from-adrs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams systematically mine architecture decision records, gotchas, and postmortems to identify recurring patterns and lessons learned across projects.

Core Features & Use Cases

Mining Architectural Lessons: Reads ADRs, gotchas, runbooks, and postmortems to uncover cross-project patterns.
Identifying Recurring Issues: Detects common failure modes and best practices from multiple sources.
Use Case: A DevOps team wants to consolidate incident learnings across different microservices by analyzing their architectural decision documentation.

Quick Start

Analyze the current project directory for ADRs, gotchas, runbooks, and postmortems to generate a structured lessons digest.

Frequently Asked Questions about bmad-extract-lessons-from-adrs

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

FAQPage Schema

How do I extract lessons from ADRs and postmortems across multiple projects?▼

To extract lessons from ADRs and postmortems, you analyze scattered architectural decision records and incident response documents to identify recurring failure patterns and best practices. This process consolidates cross-project experience for improved decision-making and risk mitigation.

What is the best way to consolidate incident learnings across different microservices?▼

Consolidating incident learnings across microservices requires mining architectural decision documentation and retrospectives. By analyzing these scattered documents, you can detect common failure modes and generate a structured lessons digest for the team.

Can I use retrospectives to identify recurring failure patterns in my documentation?▼

Yes, you can analyze retrospectives alongside ADRs and runbooks to identify recurring failure patterns. This approach helps teams systematically mine architectural decision records and incident response documents to uncover cross-project lessons.

How do I generate a structured lessons digest from scattered runbooks and gotchas?▼

Generating a structured lessons digest involves analyzing your project directory for runbooks, gotchas, and postmortems. The analysis summarizes cross-project lessons by focusing on recurring patterns and best practices found within these documents.

Do I need access to architectural decision records to analyze cross-project lessons?▼

Yes, extracting cross-project lessons requires access to architectural decision records, postmortems, and related retrospectives. Analyzing this scattered documentation allows teams to consolidate experience and uncover recurring issues.

Why analyze architectural decision documentation for risk mitigation?▼

Analyzing architectural decision documentation for risk mitigation helps teams systematically mine postmortems and ADRs to identify recurring failure patterns. This consolidates experience from scattered sources, supporting improved decision-making and reducing future incidents.