Prod Readiness
Scans a codebase and config for 24 production readiness items and produces a scored report. Use when the user asks to check production readiness, audit for prod, review operational concerns, scan for health checks, verify deployment readiness, or assess if code is ready for production.
Install
/plugin marketplace add npow/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add npow/claude-skills --skill prod-readinessgit clone --depth 1 https://github.com/npow/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/prod-readiness ~/.claude/skills/prod-readinessPersonal 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 Scanner
Scans code and config for 24 production readiness items using **24 independent Haiku judges in parallel** — one per item. Coordinator orchestrates; it never assigns pass/fail. Produces a structured defect registry with verbatim file/line evidence, a scored scorecard, and an honest termination label.
## Contents
- [Workflow](#workflow)
- [Model tier strategy](#model-tier-strategy)
- [Integration with other skills](#integration-with-other-skills)
- [Degraded mode](#degraded-mode)
- [Self-review checklist](#self-review-checklist)
- [Reference files](#reference-files)
---
## Workflow
### Phase 0: Stack detection (coordinator)
1. Generate `run_id: $(date +%Y%m%d-%H%M%S)`.
2. Create `prod-readiness-{run_id}/` in CWD with subdirectories per STATE.md.
3. Write `prod-readiness-{run_id}.lock` in CWD; verify write succeeded.
4. Detect language, framework, package manager, container tooling, CI tooling per PATTERNS.md project-type table.
5. Write findings to `prod-readiness-{run_id}/stack.json` and to `state.json` under `stack` key.
6. Initialize the 24 item entries in `state.items` per STATE.md; each starts `status: "not_started"`.
**If `--diff [ref]` is passed:** scope is the git diff only; still run all 24 judges, but judges narrow their search to changed files + callers.
### Phase 1: Compile per-item judge inputs (coordinator)
For each of the 24 items (parallel-safe, so write in parallel):
1. Read the full item definition from CHECKS.md.Details
- Skill name
prod-readiness- Repository
- npow/claude-skills
- Path
prod-readiness/SKILL.md- License
- Apache-2.0
- Repo updated
- 20 August 2026
FAQ
What does the Prod Readiness skill do?
Scans a codebase and config for 24 production readiness items and produces a scored report. Use when the user asks to check production readiness, audit for prod, review operational concerns, scan for health checks, verify deployment readiness, or assess if code is ready for production.
How do I install the Prod Readiness skill?
Claude Code plugin: /plugin marketplace add npow/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Prod Readiness popular?
It lives in npow/claude-skills, which has 5 GitHub stars and 1 forks.
Related skills
Autopilot
5npow/claude-skills
Use when the user says "autopilot", "build this", "make it", "ship it", "just do it", "do it", "implement this", or gives a vague idea, spec, task list, or bug fix and expects autonomous execution. Handles decomposition, agent coordination, and verification automatically. "build me end to end", "go from idea to code", "do everything", "run this autonomously". Follows the Spec-Driven Development workflow: specify → clarify → plan → tasks → analyze → implement.
Build Python Library
5npow/claude-skills
Implements pip-installable Python libraries from scratch using src layout, pyproject.toml, and pytest. Use when the user asks to build, create, implement, or scaffold a Python library, package, pip package, middleware, SDK, or wrapper. Covers project scaffolding, proxy/wrapper patterns, provider-agnostic interfaces, async/sync support, and test infrastructure.
Canon Design Review
5npow/claude-skills
Architecture-level design review evaluating 15 Tier 2 best practices drawn from DDD (Evans), POEAA (Fowler), Release It! (Nygard), DDIA (Kleppmann), Team Topologies (Skelton/Pais), How Buildings Learn (Brand), and Systemantics (Gall). Auto-invoke when a PR touches: - Service definitions, infrastructure code, API boundaries, or database schemas - Files matching **/architecture*, **/design*, **/api/*, **/schema*, **/migrations/* - Any directory named services/, infrastructure/, platform/, domain/, core/ Also invoke when the user says: - "design review", "architecture review", "review the design"
Request Refactor Plan
5GAGAA-HUE/ASHUO-claude-skills
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
Diagram
5npow/claude-skills
Renders interactive diagrams in the browser using Cytoscape.js. Use when the user asks to visualize, diagram, draw, render, or show a graph, flowchart, dependency tree, roadmap, architecture diagram, or any node-and-edge structure. Always renders live in browser — never as a static image.
Setup Ts Deep Modules
5GAGAA-HUE/ASHUO-claude-skills
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.