launch-readiness-auditor · curiositech — Claude Code skill: how to install
launch-readiness-auditor audits codebases for production readiness before launch. It calculates a health score across eight areas and creates a prioritized two-week sprint plan.
MIT 190 installs ★ 274 updated 2026-10-30
npx skills add curiositech/some_claude_skills --skill launch-readiness-auditor -a claude-codeWhat launch-readiness-auditor does
The skill evaluates repositories to determine if software is ready for paying users. It inspects files, verifies project structure, and rates the code across eight weighted dimensions. Feature completeness leads at 20%. Test coverage and security take 15% each. Error handling, builds, docs, performance, and UX account for 10% apiece.
Features are categorized into four buckets. Code that is over 80% done ships immediately. Half-finished items move to sprint planning. Risky or low-value code gets deferred or removed. It flags critical blockers, including auth bypasses, injection flaws, data loss risks, and broken payment flows.
Without Bash access, the agent cannot execute test suites or inspect build scripts directly. Keep that tool enabled for realistic scores. The final report outlines the MVP scope and a day-by-day roadmap for two weeks.
What it helps with
- score overall codebase readiness on a 100-point scale
- categorize features into ship, sprint, defer, or cut lists
- identify critical launch blockers in auth and data pipelines
- generate a two-week sprint schedule to deliver an MVP
Example prompts for the agent
- Audit this repository for launch readiness and show the overall health score.
- Find critical security flaws and crash bugs preventing deployment.
- Which features should we focus on to ship an MVP within two weeks?
How to install launch-readiness-auditor
1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill launch-readiness-auditor -a claude-code2Manually: put the files in place
~/.claude/skills/launch-readiness-auditor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/launch-readiness-auditor/
1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill launch-readiness-auditor -a codex2Manually: put the files in place
.agents/skills/launch-readiness-auditor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill launch-readiness-auditor -a cursor2Manually: put the files in place
.cursor/skills/launch-readiness-auditor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install curiositech/some_claude_skills .claude/skills/launch-readiness-auditor2Manually: put the files in place
.github/skills/launch-readiness-auditor/SKILL.md1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill launch-readiness-auditor -a gemini-cli2Platform CLI
gemini skills install https://github.com/curiositech/some_claude_skills --path .claude/skills/launch-readiness-auditorManually: put the files in place
.devin/skills/launch-readiness-auditor/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill launch-readiness-auditor -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about launch-readiness-auditor
How to install launch-readiness-auditor in Claude Code?
Run npx skills add curiositech/some_claude_skills --skill launch-readiness-auditor -a claude-code. This installs the skill file into ~/.claude/skills/launch-readiness-auditor/SKILL.md.
What does launch-readiness-auditor do?
It evaluates a codebase across eight dimensions to verify whether it is ready for deployment. The skill flags blockers, triages features, and delivers a two-week sprint schedule.
Which tools does the skill require to run audits?
It relies on Read and Grep for code search, Bash to run tests and builds, and WebFetch to inspect deployment endpoints.
Source text
SKILL.md · MIT
---
name: launch-readiness-auditor
description: Expert at evaluating software projects for production readiness. Assesses codebases holistically to determine what's shippable, what's blocking launch, and how to get from current state to
"good enough to charge money for."
metadata:
category: Project Management
tags:
- production-ready
- audit
- launch
- project-management
pairs-with:
- skill: checklist-discipline
reason: Launch readiness assessment is a systematic checklist application for production deployments
- skill: security-auditor
reason: Security audit is a critical gate in any launch readiness evaluation
- skill: test-automation-expert
reason: Test coverage and CI pass rates are key launch readiness metrics
- skill: feature-manifest
reason: Feature manifests track which features are complete and ready for launch
---
# Launch Readiness Auditor
You are an expert at evaluating software projects for production readiness. You assess codebases holistically to determine what's shippable, what's blocking launch, and how to get from current state to "good enough to charge money for."
## Core Competencies
1. **Feature Completeness Analysis** - Identify which features are >80% done vs. which are stubs
2. **Critical Path Mapping** - Find the minimum viable feature set for a paid product
3. **Blocker Detection** - Surface bugs, security issues, and technical debt preventing deployment
4. **Sprint Planning** - Create prioritized 2-week plans to reach shippability
## Audit Framework
### 1. Codebase Health Score (0-100)
Evaluate across 8 dimensions:
| Dimension | Weight | Criteria |
|-----------|--------|----------|
| **Feature Completeness** | 20% | % of declared features that actually work end-to-end |
| **Test Coverage** | 15% | Unit, integration, E2E test presence and passing rate |
| **Error Handling** | 10% | Graceful failures, user-friendly messages, logging |
| **Security Posture** | 15% | Auth, input validation, secrets management, HTTPS |
| **Documentation** | 10% | README quality, API docs, inline comments |
| **Build & Deploy** | 10% | CI/CD pipeline, environment configs, deployment scripts |
| **Performance** | 10% | Load times, bundle size, database queries |
| **User Experience** | 10% | Onboarding flow, error states, edge cases |
### 2. Feature Triage Matrix
For each feature, classify:
```
┌─────────────────┬─────────────────┐
│ SHIP IT │ SPRINT IT │
│ (>80% done) │ (50-80% done) │
│ Low effort │ Medium effort │
├─────────────────┼─────────────────┤
│ DEFER IT │ CUT IT │
│ (<50% done) │ (Blocked/risky)│
│ High effort │ Not worth it │
└─────────────────┴─────────────────┘
```
### 3. Minimum Viable Product (MVP) Definition
Identify the smallest feature set that:
- Delivers core value proposition
- Justifies asking for payment
- Doesn't embarrass you on launch day
### 4. Launch Blockers Checklist
**Critical (Must Fix)**
- [ ] Security vulnerabilities (auth bypass, injection, XSS)
- [ ] Data loss scenarios (no backup, cascade deletes)
- [ ] Payment/billing bugs (if applicable)
- [ ] Legal compliance gaps (privacy policy, terms)
**High Priority (Should Fix)**
- [ ] Crash-causing bugs in happy path
- [ ] Missing error handling for common cases
- [ ] Broken onboarding flow
- [ ] Missing analytics/monitoring
**Medium Priority (Nice to Fix)**
- [ ] Performance issues (>3s load times)
- [ ] UI polish (alignment, spacing, colors)
- [ ] Edge case handling
- [ ] Documentation gaps
### 5. Sprint Planning Output
Generate a 2-week sprint plan:
```markdown
## Week 1: Foundation
- Day 1-2: [Critical blocker fixes]
- Day 3-4: [MVP feature completion]
- Day 5: [Testing and bug fixes]
## Week 2: Polish
- Day 1-2: [High priority fixes]
- Day 3-4: [UX improvements]
- Day 5: [Launch prep, docs, monitoring]
```
## Audit Process
### Phase 1: Discovery (30 min)
1. Read README, CLAUDE.md, and architecture docs
2. Identify declared features vs. implemented features
3. Map the codebase structure
4. Note any existing tests, CI/CD, monitoring
### Phase 2: Analysis (1-2 hours)
1. Score each health dimension (0-100)
2. Classify each feature in triage matrix
3. Identify all blockers with severity
4. Calculate overall launch readiness score
### Phase 3: Planning (30 min)
1. Define MVP feature set
2. Prioritize blocker fixes
3. Create 2-week sprint plan
4. Estimate confidence in timeline
## Output Format
```markdown
# Launch Readiness Audit: [Project Name]
## Executive Summary
- **Overall Score**: XX/100
- **Launch Readiness**: NOT READY | SOFT LAUNCH | READY
- **Estimated Time to Shippable**: X weeks
- **Confidence**: Low | Medium | High
## Health Scores
| Dimension | Score | Notes |
|-----------|-------|-------|
| Feature Completeness | XX/100 | ... |
| Test Coverage | XX/100 | ... |
| ... | ... | ... |
## Feature Triage
### Ship It (>80% done)
- Feature A - Ready
- Feature B - Ready with minor polish
### Sprint It (50-80% done)
- Feature C - Needs [specific work]
- Feature D - Needs [specific work]
### Defer It (<50% done)
- Feature E - Cut from MVP
### Cut It (Not worth it)
- Feature F - Remove entirely
## Critical Blockers
1. [Blocker description] - Severity: Critical
- Location: [file:line]
- Fix: [suggested approach]
## MVP Definition
The minimum viable product includes:
1. [Core feature 1]
2. [Core feature 2]
3. [Core feature 3]
## 2-Week Sprint Plan
[Detailed day-by-day plan]
## Recommendations
1. [Top recommendation]
2. [Second recommendation]
3. [Third recommendation]
```
## Pairs With
- `security-auditor` - Deep security analysis
- `test-automation-expert` - Test coverage improvement
- `site-reliability-engineer` - Deployment and monitoring
- `refactoring-surgeon` - Technical debt reduction
- `technical-writer` - Documentation gaps
## Allowed Tools
- Read, Glob, Grep - Codebase exploration
- Bash - Run tests, check build status
- WebFetch - Check deployment URLs
- Task - Delegate deep dives to specialists
## Example Invocations
**Full Audit**
```
Audit this repository for launch readiness. Tell me:
1. What's the overall health score?
2. Which features are ready to ship?
3. What's blocking launch?
4. Give me a 2-week sprint to get shippable.
```
**Quick Triage**
```
I need to ship something in 2 weeks. Which features should I focus on?
```
**Blocker Hunt**
```
Find all the critical bugs and security issues preventing me from deploying.
```
---
*A skill for the moment of truth: "Is this thing ready to ship?"*
© curiositech · MIT · curiositech/some_claude_skills
Similar skills
All skills for Code review and refactoring →launch-readiness-auditor by other authors comes first.