🗺️ Engineering Essentials · Journey Playbooks

Playbook: Learn from production incidents properly

Blameless retro turning each incident into systemic fixes, not scar tissue.

journey~40 minAll Software Engineers

Journey Steps

1Step 1 — Debug production without stopping the world (Python): start with "Correlate user report to trace IDs through gateway → service → data layer"
2How it fits together: Timeline from evidence, actions with owners, and a follow-up review date.

Commands

Install all referenced skills

$ npx skills add aniruddhaadak80/skills --skill debug-craft-production-debugging-python

Tags

#playbook#journey#engineering-essentials

Install this skill

$ npx skills add aniruddhaadak80/skills --skill playbook-engineering-essentials-incident-learning -a opencode

SKILL.md

# Playbook: Learn from production incidents properly

> Blameless retro turning each incident into systemic fixes, not scar tissue.

## When to Use This Skill

Blameless retro turning each incident into systemic fixes, not scar tissue.

## Steps

1. Step 1 — Debug production without stopping the world (Python): start with "Correlate user report to trace IDs through gateway → service → data layer"
2. How it fits together: Timeline from evidence, actions with owners, and a follow-up review date.

View source on GitHub ↗

Take retrieval-augmented answers from empty repo to evaluated production feature.

🗺️ AI Engineering·~135m

Open →

🗺️Playbook: Harden an agent before giving it toolsjourney

Ship an autonomous agent whose failure modes are cheap, visible, and reversible.

🗺️ AI Engineering·~125m

Open →

🗺️Playbook: Cut LLM costs without quality collapsejourney

Reduce monthly inference spend measurably while keeping answer quality within tolerance.

🗺️ AI Engineering·~95m

Open →