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.
Integrations
Working With Linear
Use this skill when: - Creating or updating Linear issues - Managing project workflows and cycles - Organizing development tasks and priorities - Setting up project structures and teams
Part of these packs.
Skills travel in packs — pick one and your Righthand arrives already equipped with everything the job needs.
- 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.
- 8 skills
Product Manager
Feedback synthesis, buildable specs, and a roadmap that admits what's slipping — the space between what users say and what the team builds.
- 12 skills
Product Signal
The space between what users say and what the team builds. Feedback synthesized into themes, users talked to on a cadence and thanked when their issue ships, specs that surface disagreement before the code does, and a roadmap that admits what is slipping.
- 4 skills
Running the Issue Tracker
The single true picture of the work. Every ask lands in the tracker, gets triaged within a day with severity, owner, and next action, and cycles are sized to what the team actually finishes.
- 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.
- 4 skills
Talking to Users
The listening layer. One real user conversation every week, a "this shipped, thank you" to every reporter whose issue closed, an eye on reporters who went quiet, and the standing answer to "what did the user actually mean."
- 4 skills
Writing Specs That Decide
The spec layer. Anything big enough to argue about gets a written spec before it enters a cycle, with the problem, the evidence, the proposed shape, the acceptance criteria, the open questions, and what is out of scope, so the argument happens on paper instead of in the diff.
Browse all skills