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.
Your Righthand makes delivery visible. A morning standup digest says what moved and what is blocked, with an unblock attached. A Monday metrics readout says what the numbers did and what that means. A status view stays honest about every tracked project and risk. And the Friday review closes the week against the tracker, calibrating its own estimates in public.
What's in the pack.
10 skills, installed together — your Righthand arrives already equipped for the job.
- 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
- 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.
- 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`.
- 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.
- 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.
- 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.
Hire a Righthand
ready for this job.
Pick Delivery Visibility at signup and your Righthand shows up with every skill in the pack already installed.