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.
Engineering
Using Coding Agents
Delegate bounded engineering implementation to an asynchronous Codex or Claude coding job, answer only judgment questions, and independently review the resulting diff against user acceptance scenarios.
Part of these packs.
Skills travel in packs — pick one and your Righthand arrives already equipped with everything the job needs.
- 5 skills
Coordinating Launches
The launch layer. Every user-facing change gets its release note, support heads-up, and customer comms drafted before it merges, a kill switch and rollback path with a named owner, and a dated verdict weeks later against the metric the spec promised.
- 10 skills
Delivery Visibility
The answer before the question. Standups, delivery reviews, the numbers behind every shipped feature, and one honest status view, so what is in flight, what landed, and what it did are always a glance away.
- 7 skills
Engineering Team
Shipping through the codebase, keeping PRs moving, and delivery visibility — standup digests, review sweeps, and honest weekly delivery reports.
- 3 skills
Handling Incidents
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.
- 3 skills
Keeping CI Green
The pipeline layer. The main branch stays green, flaky tests get fixed or deleted instead of retried, stale branches get pruned, deploys get verified, and every fix arrives as a PR or an issue rather than a report.
- 3 skills
Keeping Dependencies Current
The dependency layer. Updates land weekly in small batches instead of quarterly in a terrifying one, critical and high security alerts get a fix dispatched the day they appear, and every bump arrives as a reviewed pull request rather than a warning count.
- 4 skills
Keeping Docs True
The documentation layer. The README, runbooks, architecture notes, ADRs, and Notion engineering pages describe the system that exists, docs change with the change that invalidated them, and wrong docs get fixed or deleted rather than left to mislead.
- 3 skills
Measuring What Ships
The proof layer. Five core metrics the founder recognizes stay on one trusted view, every Monday says what changed and what it means, and every feature merged without an event gets an instrumentation issue the same week.
- 3 skills
Paying Down Tech Debt
The debt layer. A real ledger with an interest rate per item, a dated list of things that will bite us, a fixed weekly slice spent on the highest-interest item, and every shortcut noted with a date and a reason.
- 3 skills
Reviewing Pull Requests
The review layer. Every open pull request, human or agent-authored, gets a full read against what it claimed to do, within a day, and nothing sits unreviewed or stalls on a silent author.
- 6 skills
Shipping Code
The whole line from a one-line issue to deployed code — bounded work dispatched to coding agents against acceptance scenarios written first, every diff read in full before approval, and a pipeline where red main is an emergency.
- 5 skills
Shipping With Coding Agents
The delivery engine. Ready issues become acceptance scenarios, then bounded coding-agent jobs, then independently reviewed diffs, then merges followed through CI and deploy, every weekday without being walked through it.
- 28 skills
Software Development
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.
- 9 skills
Technical Health
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 all skills