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.
Your Righthand owns software development end to end. It takes issues to deployed code through coding agents and reads every diff before it merges, keeps CI green and the tracker honest, sends the standup and the Friday delivery review, reads the numbers every Monday, talks to a user every week and thanks the ones whose reports shipped, writes the spec and the unasked-for pre-mortem before big work, handles dependencies, debt, incidents, and docs on a weekly cadence, and runs every launch through the same playbook. Adopted as one, it staggers its own setup over two weeks so no day asks you more than a few questions.
What's in the pack.
28 skills, installed together — your Righthand arrives already equipped for the job.
- Coding
Software Engineering
Software-engineering work across the full development lifecycle: implementing changes, reviewing peers' code, debugging failures, and monitoring repository health. Use when (1) you've been handed a feature or bug to implement and need to write/branch/test/PR/merge end-to-end — load `Reference/writing-and-shipping-code.md`; (2) a PR has landed in your queue to review — load `Reference/reviewing-code.md`; (3) a test is failing, the build broke, or a bug was reported and you need to trace it to root cause — load `Reference/debugging-and-investigating.md`; (4) you're doing a routine repo health check, triaging stale PRs, or responding to CI/dependency alerts — load `Reference/monitoring-repositories.md`. Each phase doc has its own deeper Reference subdirectory with the specifics. For GitHub CLI mechanics (gh commands, repo cloning, PR/issue queries), use `using-github`. For Linear-based issue tracking, use `working-with-linear`. For drafting product specs before implementation, use `writing-product-specs`.
- 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.
- Coding
Using Github
Interact with GitHub repositories, issues, pull requests, and CI/CD using the GitHub CLI (gh). Use when: cloning repos, creating or reviewing pull requests, managing issues, checking CI/CD status, browsing code, or any GitHub operation. GitHub is NOT accessed through tool_use — it uses the gh CLI directly.
- 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
- Engineering
Babysit Commit
Follow one exact APC commit through GitHub checks, development deployment, and a live acceptance canary; intervene on failures and report durable evidence.
- Engineering
CI and Release Hygiene
Use when keeping a CI pipeline healthy and releases verifiable: acting on a red main branch the moment you see it, triaging flaky tests (quarantine, fix, or delete with a dated note), pruning stale branches, tagging releases, verifying deploys, and reading a failing CI log fast. Maintains Knowledge/Organizations/pipeline.md.
- Engineering
Issue Tracker Hygiene
Use when running the issue tracker as the single true picture of the work — triaging new issues within a day, keeping status honest, planning cycles the team actually finishes, linking PRs to issues to specs, and standing a tracker up from nothing.
- Email And Comms
Working With Email
Operates on a USER's connected Gmail or Outlook account via `agent connection tool-exec` — drafting messages from their address, reading and searching their threads, and triaging incoming replies in their mailbox. Use when the user delegates email work to you on THEIR account: composing outreach from their address, responding to messages in their inbox, classifying replies to a campaign they're running, or organizing their inbox (search, label, archive). The mailbox belongs to THEM, not to you. For the Righthand's own inbox (using `agent email` directly), use `my-email` instead.
- Product
Shipping And Launch Coordination
Track a feature from approved spec through to shipped and measured. Coordinate QA, manage rollout plans, write release notes, monitor post-launch metrics, and close the loop on whether the feature achieved its goals. Use when: a spec is approved and entering development, a feature is approaching release, or you need to evaluate whether a shipped feature actually worked. PM-focused — you own the feature from spec to measured impact.
- Product
Cross Functional Coordination
Coordinate across engineering, design, and leadership to drive product decisions. Run design reviews, negotiate scope, align stakeholders, unblock decisions, and communicate trade-offs. Use when: a feature needs input from multiple teams, a scope decision is stuck, stakeholders disagree on priorities, or you need to say "no" with a rationale. PM-focused — you are the connective tissue between teams.
- Research
Searching The Web
Use when you need up-to-date facts, news, or external verification beyond the knowledge graph.
- Product
Product Instrumentation
Use when making sure every shipped feature has the event that proves it was used and the metric that says whether it worked: events as code, one metric per feature named in the spec, the one view of core metrics the founder recognizes, change-only weekly readouts, and the instrumentation issue for anything merged without a number. Maintains Knowledge/Organizations/metrics.md.
- Knowledge
Status Dashboards
Use when maintaining an at-a-glance health view of your manager's world and the institutional memory behind it in Knowledge/ — the status-view format, freshness discipline, change-only reporting, and filing decisions and post-mortems so they resurface when the topic returns.
- Productivity
Working With Documents
Anything to do with document files — sending them, receiving them, creating them from scratch, reading or extracting data from them, or editing them. Use when: (1) someone has attached a file to an email/SMS/Slack message and you need to download it with `agent download` to read or analyze its contents; (2) you're sending an email or MMS and need to attach a file (`agent email send --attachment …`, `agent sms send --media …`); (3) you've been asked to create a new spreadsheet, slide deck, PDF, business report, or proposal; (4) you need to extract text, tables, or data from a PDF or Excel file, or do spreadsheet work (formulas, pivots, charts); (5) you're editing existing document files (merging PDFs, OCR, password-protecting, format conversion). Covers PDFs, Excel/CSV, PowerPoint, general business documents, and attachment handling end-to-end. For documents that live inside Notion or Linear specifically, use `working-with-notion` or `working-with-linear` instead.
- 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.
- Integrations
Working With Notion
Use this skill when: - Creating or organizing Notion pages - Setting up databases and views - Managing documentation and wikis - Building knowledge bases - Organizing team information
- Calendar And Meetings
Generating Meeting Prep
Proactively prepares meeting briefings by combining calendar review with participant research. Only activate when reminded — not spontaneously.
- Gtm
Competitor Intelligence
Builds and maintains competitor intelligence for sales and marketing. Use when monitoring competitor pricing, features, or messaging changes; researching alternatives for a comparison page; building 'vs' or 'alternatives to' SEO landing pages (e.g. 'create alternatives to Lindy'); handling competitive objections in deals; or analyzing customer sentiment on review sites (G2, Capterra). Sources include review sites, LinkedIn, competitor websites, news alerts, and Reddit. For broader positioning strategy see `marketing`; for SEO optimization of the comparison pages see `seo`; for prospect (not competitor) research see `prospect-research-automation`.
- Product
User Conversations
Use when talking to the product's users directly: keeping a cadence of conversations, writing outreach that gets replies, running a 30-minute interview, writing the note, closing the loop with everyone who reported something, and translating what a user said into what they actually meant. Maintains Knowledge/Organizations/user-roster.md and Knowledge/People/ notes.
- Calendar And Meetings
Working With Calendar
Manages a USER's connected Google Calendar or Outlook calendar via `agent connection tool-exec`. Use when the user delegates calendar work to you on THEIR account — checking their availability, scheduling meetings on their schedule, accepting/declining invites for them, coordinating attendees across timezones, or auditing their calendar for conflicts. Applies the same scheduling, etiquette, and timezone wisdom as `my-calendar` but executed against the user's connected calendar instead of your own. The calendar belongs to THEM, not to you. For your own calendar (the one the Righthand uses `agent calendar` against directly), use `my-calendar` instead.
- Documents
Decision Memos
Use when writing the artifact behind a decision — one-pagers, strawman memos, and simple models that put options, a recommendation, and "what would change my mind" in front of the room before the meeting.
- Engineering
Dependency and Security Updates
Use when keeping a codebase's dependencies current and its security alerts handled: shipping weekly small update batches instead of quarterly big bangs, triaging CVEs the day they land with severity thresholds, keeping lockfiles honest, reading a changelog fast for breaking changes, running a major upgrade safely, and keeping a dated list of things that will expire. Maintains Knowledge/Organizations/dependency-norms.md.
- Engineering
Tech Debt Ledger
Use when keeping tech debt as a costed, dated ledger instead of a complaint box: pricing each item by interest rate and cost to fix, marking which shortcuts are load-bearing, maintaining the dated "will bite us" list, paying down the highest-interest item in a fixed weekly slice via a coding-agent job, and leaving every touched file more legible. Maintains Knowledge/Organizations/tech-debt.md.
- Operations
Incident Communications
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/.
- Communications
Sending Communications
Use whenever you need to send an outbound SMS, email, Slack message, or voice call from your own number/address. Your final response text is internal logging only — the ONLY way to talk to the outside world is the agent CLI.
- Engineering
Living Documentation
Use when keeping a team's documentation true: auditing READMEs, runbooks, architecture notes, ADRs, and Notion engineering pages against the code and the deploy path, fixing docs alongside the change that invalidated them, writing light decision records, deleting wrong docs, and running the absence test. Maintains Knowledge/Organizations/docs-index.md.
- Calendar And Meetings
Meeting Operations
Use when running the mechanics of decision-producing meetings — writing agendas, sending pre-reads, capturing action items with owners and dates, chasing them to closure, and recommending which recurring meetings to kill.
- Work Management
Special Projects
Use when running point on a cross-cutting or ownerless project — scoping it, driving it to done, and handing it back to a real owner or closing it finished.
Hire a Righthand
ready for this job.
Pick Software Development at signup and your Righthand shows up with every skill in the pack already installed.