runbook-generator

1. Every command must be copy-pasteable — no placeholder text, use env vars 2. ✅ after every step — explicit expected output, not "it should work" 3. Time estimates are mandatory — engineers need to know if they have time to fix before SLA breach 4. Rollback before you deploy — plan the undo before executing 5. Runbooks live in the repo — docs/runbooks/, versioned with the code they describe 6. Postmortem → runbook update — every incident should improve a runbook 7. Link, don't duplicate — reference the canonical config file, don't copy its contents into the runbook 8. Test runbooks like you test code — untested runbooks are worse than no runbooks (false confidence)