Engineering Team
Shipping through the codebase, keeping PRs moving, and delivery visibility — standup digests, review sweeps, and honest weekly delivery reports.
Your Righthand ships. It takes issues from the tracker to merged code, keeps pull requests moving with an afternoon review sweep, sends a morning standup digest so you always know what is in flight and what is blocked, coordinates launches, and closes each week with an honest report of what shipped and what slipped.
What's in the pack.
6 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`.
- 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
- 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.
Hire a Righthand
ready for this job.
Pick Engineering Team at signup and your Righthand shows up with every skill in the pack already installed.