Incident

Works a production incident together with a person: one record of what is seen, the timeline and the hypotheses, and every mitigation prepared as a staged script that the person starts. Use when the user says production is down, the site is broken for customers, we have an incident, users cannot log in or pay, we need to roll back, or comes back to an incident that is still open. Not for a defect that hurts no running user and not for finding the root cause afterwards (systematic-debugging), not for the routine reading of what production reports (signal-intake), and not for one planned production step (handover-step).

Yesterday-AI Updated 2 repo stars
ytstack greenfield flow -- office-hours -> plan-ceo-review -> init-project -> plan-milestone -> slice -> task-loop (plan-task -> TDD -> verify -> summarize) ->

File contents

Yesterday-AI/ytstack commit ed55375bfd

Frequently asked questions

npx get-skill add yesterday-ai/incident