Technical Health
The unglamorous maintenance nobody asks for. Dependencies and CVEs handled weekly in small batches, a tech-debt ledger with real interest rates paid down every week, incidents followed through to a closed post-mortem, and docs that describe the system that exists.
Your Righthand keeps the system healthy. Security alerts get a fix the day they land and updates ship in small weekly batches, the tech-debt ledger gets its highest-interest item paid every Thursday, every incident ends in a blameless post-mortem whose action items actually close, and the docs stay true enough that anyone could deploy from them. All code changes go through coding agents; your Righthand diagnoses, reviews, and follows through.
What's in the pack.
9 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.
- 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.
- 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
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.
- 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
Hire a Righthand
ready for this job.
Pick Technical Health at signup and your Righthand shows up with every skill in the pack already installed.