This is one skill of many.
Browse the full catalog to see everything your Righthand can take off your plate — and everything you can teach it later.
Operations
Use when something is broken in production or during incident follow-through: severity levels, the four-line update posted on a clock, the shape-not-stack-trace rule for the founder, driving a revert or fix through a coding agent to confirmed, the blameless post-mortem within days, action items tracked to closure, and alert hygiene. Maintains Knowledge/Organizations/incident-protocol.md and Knowledge/Organizations/incidents/.
Skills travel in packs — pick one and your Righthand arrives already equipped with everything the job needs.
The incident layer. When something breaks the right people hear about it on a clock, the fix gets dispatched and confirmed, the blameless post-mortem lands within days, its action items get tracked to closure, and alerts that fire without a human action get fixed or deleted.
The engineering lead and product manager a founder wishes they could afford as one hire. Code shipped through coding agents against scenarios written first, delivery always visible, users listened to and measured, the system kept healthy, launches coordinated, and a rhythm that protects maker time.
The unglamorous maintenance nobody asks for. Dependencies and CVEs handled weekly in small batches, a tech-debt ledger with real interest rates paid down every week, incidents followed through to a closed post-mortem, and docs that describe the system that exists.
Browse the full catalog to see everything your Righthand can take off your plate — and everything you can teach it later.