auro-release-process

Run the Auro 2.0 release-caused incident response — the first hour after a bad release. Use when a post-deploy smoke test fails, an error or latency spike appears after a recent deploy, a PagerDuty alert fires on a service just released to, a customer reports a problem within the active monitoring window, or the team explicitly says they have a release incident. Trigger with "release incident", "we just deployed and it's broken", "error spike post-deploy", "should we roll back or fix forward", "open the incident thread", "post-deploy issue", "P1 release issue", or "P2 release issue". Walks the release runner through detection, triage, severity, the rollback-vs-fix-forward decision, internal and customer comms, resolution, and postmortem handover. Drafts Teams updates, in-app banner copy, status-page entries, and resolution summaries on demand. Do not trigger for general production incidents not linked to a recent deploy, planned maintenance, or unrelated tech debt.

Execute the Auro 2.0 production or staging rollback runbook — the click-by-click for rolling a release back. Use when a rollback decision has already been made (typically by the release-incident-response process) and the team needs to walk through pre-flight checks, identify the target version, trigger the rollback workflow, and verify production is back on the previous version. Trigger with "roll back the release", "trigger the rollback", "rollback runbook", "redeploy previous version", "rollback workflow", "previous good release", "pre-flight checks", "rollback to vX.Y.Z", "we need to roll back", "execute rollback", "rollback executor", "production rollback", or "staging rollback". Distinct from release-incident-response — that skill runs the broader incident; this skill is specifically the mechanical execution of a rollback. Always reminds the user that production rollback can only be triggered by the tech lead or EM, not the release runner.

Walk a user through filing an Auro production incident post-mortem in ClickUp. Steps through every template section via structured questions — incident metadata, summary, impact, timeline, detection, root cause, resolution, what worked and what didn't, action items, lessons learned, and the sign-off checklist — then creates a new page as a subpage under Auro Incident Logs (page 8cn806c-9074 in document 8cn806c-1774). Trigger with "log an Auro incident", "create a post-mortem", "we had an outage and need to write it up", "fill out the post-mortem template", "Auro post-mortem", "hotfix post-mortem", "blameless post-mortem", "production incident", or any time the user describes an Auro production issue and wants it written up. Do not trigger for customer-support tickets, generic project retros, or non-Auro incidents.

Cuts a Production release in ClickUp for the Auro engineering ecosystem: creates the release task, finds all Done sprint tasks without a Release set, links them after user confirmation, generates the engineering description and deploy notes, and posts a customer-facing release notes draft as a comment on the release task for CS review. Triggers: "cut a release", "create a release", "build a release", "new release", "package a release", "time to release", "we're cutting v...", "release for [date]", "do a release", "sweep up done tasks for release", "build the release task". Do NOT trigger for: viewing existing releases, rewriting an already-created release's description (do that via direct ClickUp MCP calls), feedback intake (use prod-feedback-to-clickup), QA sessions, smoke tests, or non-release ClickUp work.

Drives Claude in Chrome through the deterministic post-deploy smoke test checklist for Auro Prod, captures pass/fail state for each item with evidence, auto-logs high-confidence failures via the prod-feedback-to-clickup skill, and produces a filled-in checklist ready to paste into the release log. Triggers: "run the prod smoke test", "validate the deploy", "run release validation", "post-deploy smoke test", "smoke test the release", "validate prod release", "run the release smoke test", "smoke the deploy", "just deployed, check it", "is prod still up after that release", "validate the rollout". Also triggers when a user mentions a fresh Prod deploy and asks for validation. Do NOT trigger for: exploratory testing (use prod-qa-session-runner), Staging-only checks, mobile/Technician app testing (manual only), or testing during active development.