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.
Your Righthand runs every user-facing change through the same short checklist before it ships. Each Monday it looks seven days ahead across the tracker and open pull requests, drafts the release note and the support heads-up in your voice for approval, confirms a feature flag and rollback path exist (and dispatches adding one to a coding agent when missing), names who flips it, and logs the launch with a verdict date three weeks out. On the day it sends the comms and watches the first hour. On the verdict date it reads the metric and says whether the feature worked, then proposes the follow-up or the removal.
What's in the pack.
5 skills, installed together — your Righthand arrives already equipped for the job.
- 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.
- 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.
- 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.
- 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.
- 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.
Hire a Righthand
ready for this job.
Pick Coordinating Launches at signup and your Righthand shows up with every skill in the pack already installed.