Run a full pre-launch quality gate before shipping — chains product review, growth audit, UX audit, security scan, and deployment preflight into a go/no-go launch decision. Stops on critical blockers. Use before v1 launch, beta release, major version rollout, or feature launch.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are an autonomous launch readiness agent. Do NOT ask the user questions. Run the full pre-launch pipeline below. If any phase finds CRITICAL issues, STOP immediately and report before proceeding -- do not let critical problems cascade through later phases unaddressed.
TARGET: $ARGUMENTS
If arguments are provided, use them as context for the launch scope (e.g., "v2.0 launch", "beta release", specific feature area). If no arguments, evaluate full product launch readiness.
Follow the instructions defined in the /cpo-review skill exactly.
Evaluate the product from a Chief Product Officer perspective:
Record the CPO verdict and all findings.
CRITICAL GATE: If the CPO review identifies any CRITICAL product gaps (e.g., core user flow is broken, value proposition is unclear, critical feature is missing), STOP and report. Do NOT proceed to later phases -- launching with a broken product wastes all downstream effort.
Follow the instructions defined in the /growth-audit skill exactly.
Evaluate growth readiness:
Record the growth readiness score and all findings.
CRITICAL GATE: If growth audit finds CRITICAL issues (e.g., no way to acquire users, activation flow is broken, zero retention infrastructure), STOP and report.
Follow the instructions defined in the /ux skill exactly, in UX Audit mode.
Evaluate every user-facing screen against:
Fix all issues found and commit the fixes. Record the UX verdict: UX READY, UX NEEDS WORK, or UX POOR.
CRITICAL GATE: If UX verdict is UX POOR, STOP and report.
Follow the instructions defined in the /secure skill exactly.
Run the full security audit:
Fix all issues found and commit the fixes.
CRITICAL GATE: If any CRITICAL security vulnerabilities are found that could not be fixed, STOP and report. Do NOT launch with known critical security issues.
Follow the instructions defined in the /preflight skill exactly.
Run pre-deploy verification:
Record the preflight verdict: READY TO DEPLOY or NOT READY.
After completing all phases, validate the combined output:
STOP when:
IF STILL FAILING after 3 iterations:
| Phase | Skill | Status | Critical | High | Medium | Verdict |
|---|---|---|---|---|---|---|
| 1 | /cpo-review | {PASS/FAIL} | {N} | {N} | {N} | {verdict} |
| 2 | /growth-audit | {PASS/FAIL} | {N} | {N} | {N} | {verdict} |
| 3 | /ux | {PASS/FAIL} | {N} | {N} | {N} | {UX verdict} |
| 4 | /secure | {PASS/FAIL} | {N} | {N} | {N} | {verdict} |
| 5 | /preflight | {PASS/FAIL} | {N} | {N} | {N} | {READY/NOT READY} |
LAUNCH VERDICT: {GO / NO-GO / CONDITIONAL GO}
Phase {N} ({skill name}) found CRITICAL issues. Pipeline halted.
Blockers that must be resolved before re-running:
| Phase | Fix | Files Changed |
|---|---|---|
| 3 | {UX fix description} | {files} |
| 4 | {security fix description} | {files} |
| # | Issue | Phase | Severity | Recommendation |
|---|---|---|---|---|
| 1 | {description} | {phase} | {HIGH/MEDIUM} | {action} |
============================================================
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /launch-readiness — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}
Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
NEXT STEPS:
After GO:
/full-deploy to execute the deployment pipeline."After CONDITIONAL GO:
/iterate to address the high-severity items within 1 week."/customer-success-audit to ensure post-launch support infrastructure is ready."After NO-GO:
/launch-readiness."/iterate to address the critical issues."/polish for a thorough quality pass before retrying."まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Run a full Section 508 + WCAG 2.2 Level AA accessibility audit on a federal / .gov / public-sector website or ICT product. Triggers: "Section 508", "508 audit", "WCAG", "VPAT", "ACR".
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes actuarial modeling systems for loss reserving accuracy, premium pricing methodology, mortality/morbidity tables, stochastic modeling, and capital adequacy per SOA and Solvency II standards..
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes advertising yield across programmatic and direct-sold inventory including CPM/CPC/CPA performance, header bidding efficiency, fill rate optimization, inventory monetization strategies, and compliance with IAB standards and OpenRTB protocols..
日本語の概要は準備中です。原文の説明を表示しています。
Create and manage Architecture Decision Records using the Michael Nygard format. Triggers: you need to document architecture decisions, record technical choices, explain why a technology was chosen.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes affordable housing management software for unit allocation algorithms, waitlist management, income verification workflows, Fair Housing compliance, LIHTC and Section 8 program tracking, inspection scheduling, and tenant reporting..
日本語の概要は準備中です。原文の説明を表示しています。
Rewrites existing landing pages, blog posts, and documentation so AI search engines (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini) cite them. Triggers: an existing page underperforms in AI answers despite ranking well in classic SERPs.
日本語の概要は準備中です。原文の説明を表示しています。