Write an incident postmortem
Something broke in production. You fixed it. Now you need to write a postmortem that's useful (not just a formality) — capturing what happened, why, and what prevents it from happening again. AI does the heavy lifting of structuring the narrative.
Premium workflow
Write an incident postmortem is part of the full Developer Edition library. The full pack has 35 workflows total, including 27premium workflows.
More from Developer Edition
Build your Repo Context Profile
AI coding tools (Cursor, Claude Code, Copilot) are dramatically better when they know your stack, your conventions, your architecture, and your sensitive areas. Without that context they default to "what's typical on GitHub" — often the wrong pattern for YOUR repo. This workflow builds a structured context file (AGENTS.md / CLAUDE.md / .cursor/rules) that AI loads on every session — so it always has the full picture.
Onboard onto an unfamiliar codebase
You just cloned a repo you've never seen. Maybe it's a new job, an open-source project, or a client's codebase. Instead of spending 2 days reading files randomly, you use AI to build a mental map in 20 minutes.
Write AGENTS.md for your repo
Every time you start a new AI coding session, you re-explain your stack, conventions, and "don't do that" rules. An AGENTS.md file tells the AI once, permanently. This workflow gets you from zero to a working repo instruction file in 8 minutes.