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.
Product
Writing Product Specs
Write, structure, and maintain product specs — PRDs, feature specs, one-pagers, and scope documents. Use when: defining a new feature, scoping work for engineering, proposing a product change to stakeholders, or refining an existing spec that's unclear. Covers problem framing, solution design, acceptance criteria, edge cases, and trade-off documentation. PM-focused — produces artifacts that drive decisions and unblock engineering.
Part of these packs.
Skills travel in packs — pick one and your Righthand arrives already equipped with everything the job needs.
- 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.
- 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
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