Post-Mortem Root Cause Narrative Engine
Converts raw incident logs and timelines into a structured, blameless Post-Mortem report.
Debugging prompt templates.
Converts raw incident logs and timelines into a structured, blameless Post-Mortem report.
Synthesizes system logs and timelines into a structured incident report for stakeholders and engineering teams.
Defines meaningful Service Level Indicators and Objectives based on user journeys.
Designs the conditional logic and architecture for no-code automation workflows (Zapier/Make).
Investigates a specific quality failure in supplied parts using 5-Why and Ishikawa frameworks.
Designs a robust Airflow or Dagster DAG with proper task partitioning and error handling.
Defines a self-healing workflow for agents executing complex sequences of API calls.
Creates a comprehensive developer-centric error catalog with actionable resolution steps.
Creates step-by-step incident response playbooks for specific cloud security scenarios.
Analyzes how an outage or bug affected the external developer community and ecosystem.
Structures a technical post-mortem for data pipeline failures or ML production incidents.
Analyzes insurance denial patterns to pinpoint upstream registration or coding failures.
Audit what we cannot see and prescribe the smallest useful instrumentation.
Design an API contract that is hard to misuse and easy to version.
Write a migration runbook with verification and a tested rollback.
Explain unfamiliar code and mark the parts that are risky to change.
Define a structured error payload whose codes clients can branch on safely across versions
Restructure a module without changing observable behaviour, protected by characterisation tests
Triage a production failure from symptoms to a ranked set of hypotheses.
Separate under-provisioned heap from a genuine retention leak in a service that dies with out-of-memory errors
Produce an ordered kubectl investigation runbook for a failing or crash-looping workload
Find the true bottleneck before optimising anything.
Turn a production bug report into ranked root-cause hypotheses with a staged investigation plan
Plan a refactor in safe increments that keep the system shippable.
Design a test strategy focused on the riskiest behaviours, not coverage vanity.
Convert raw incident timeline data into a blameless write-up with contributing causes and prioritised follow-ups
Trace a browser memory leak in a single-page application to the JavaScript reference retaining removed DOM nodes
A safe, fast pre-release checklist with rollback notes and named owners.
A pragmatic test plan covering unit, integration and edge cases to prevent regressions.
Reproducible steps, likely root causes and a minimal fix plan with an acceptance test.
A concise pull request review surfacing risks, tests to add and merge readiness.
Review a design for failure modes, coupling and operational cost.
Review a change for correctness, blast radius and reversibility.
Write a blameless postmortem that ends in dated, owned prevention work.
Updates a README or guide with setup, usage and working examples.