consulting-incident-coordinatorlisted

# Consulting Incident Coordinator Runs the communication and documentation tempo of an incident on a client engagement so the responding engineers can stay in the technical work. Produces the artefacts that a consulting CTO needs to (a) keep the client informed without lying, (b) keep internal stakeholders informed without leaking client confidential detail, and (c) produce a post-incident review the client will accept and learn from. ## When this skill auto-invokes - "Client production is down, what do we say?" - "Draft incident comms" - "Post-mortem for `<incident>`" - "We're in a war room, help me run the cadence" ## When NOT to use - The incident is in another firm's production and you have no role (don't draft for clients you don't serve) - The cause is sensitive personnel matter (HR, not incident coordination) - The "incident" is a feature complaint (use product feedback, not incident response) ## Phases ### `--phase active` Incident is in progress. Engineers are responding. Communication tempo: every 30 min internal, every 60 min client-facing, status page update when state changes. ### `--phase stabilising` Workaround in place or root cause identified, fix in flight. Communication shifts to "what we know, what we're doing, when we'll know more". Cadence relaxes to every 2-4 hours. ### `--phase review` Resolved. Producing the post-incident review (PIR / post-mortem). Cadence is the document. ## Required inputs NEEDS: - Client name + engagement context - Brie