Tech Readiness Review

Review a service against blast radius, observability, failure handling, rollback and ownership, and separate real blockers from debt. Use for production or launch readiness.

5 stars 1 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add eshmith7/claude-skills-library --skill tech-readiness-review
Manual install
git clone --depth 1 https://github.com/eshmith7/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/tech-skills/tech-readiness-review ~/.claude/skills/tech-readiness-review

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Production Readiness Review

A service ships because it works, and works is the lowest bar available. Six weeks later somebody discovers it has no alerts, no runbook, no tested rollback and exactly one person who understands it. They discover this during an incident, at a bad hour, and none of it is fixable then.

## When to use this

Trigger on: production readiness, launch readiness, go live checklist, PRR, operational readiness, pre-launch review, GA checklist, handover to on-call, "are we ready to ship", "what are we missing before launch".

## Before you start

Required: a description of what is shipping and what it depends on.

Ask, briefly:
1. **What breaks for a user if this is completely down, and separately if it is only slow.** These differ, and they set how much of the rest matters. A batch job and a login path do not need the same review.
2. **Who owns it after launch, and whether they know that.** An unowned service is the finding, not a footnote.
3. What it depends on, including the ones people forget: auth, config, DNS, a third-party API, a shared database, a cron job somewhere.
4. What the launch actually is: internal, a percentage of traffic, one customer, or everyone.
5. Whether an existing checklist or standard applies. Follow theirs rather than proposing your own.

## Workflow

### 1. Establish the blast radius first, because it scales everything else
Read the full skill on GitHub

Details

Skill name
tech-readiness-review
Path
tech-skills/tech-readiness-review/SKILL.md
Repo updated
9 September 2026

FAQ

What does the Tech Readiness Review skill do?

Review a service against blast radius, observability, failure handling, rollback and ownership, and separate real blockers from debt. Use for production or launch readiness.

How do I install the Tech Readiness Review skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add eshmith7/claude-skills-library --skill tech-readiness-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Tech Readiness Review popular?

It lives in eshmith7/claude-skills-library, which has 5 GitHub stars and 1 forks.

Related skills

Content Brief

5

eshmith7/claude-skills-library

Turn a vague content request into a brief a writer can execute without a second conversation: one question, reader, intent, angle, structure, evidence required. Use for content briefs.

Writing & Content

Content Performance Audit

5

eshmith7/claude-skills-library

Turn a performance export into one decision per asset: keep, refresh, rewrite, consolidate or delete, with cannibalisation groups found first. Use for content audits or pruning.

Writing & Content

Content Prepublication Check

5

eshmith7/claude-skills-library

Check a draft before publishing: every claim registered with its source, numbers verified, headline against body, originality and compliance flags. Use before anything goes out.

Writing & Content

Deploy Status Report

5

npow/claude-skills

Use when checking deployment status, Spinnaker deploys, canary results, what's deployed, pending rollouts, or generating a deployment report. Trigger phrases: deploy status, what's deployed, spinnaker status, canary results, deployment report, rollout status.

DevOps & Cloud

Tailscale Manager

8

Freddy-CHEN-ux/00_claude_skills

Manage Tailscale funnels across different ct project instances. Start/stop funnels and route traffic to different docker containers.

DevOps & Cloud

Dora Lite Report

5

npow/claude-skills

Use when generating a weekly DORA metrics report, checking deployment frequency, lead time, change failure rate, recovery time, or assessing software delivery performance. Trigger phrases: DORA report, DORA metrics, deployment frequency, lead time for changes, change failure rate, MTTR, recovery time, delivery performance, software delivery metrics.

DevOps & Cloud

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.