launch-readiness
Launch Readiness Auditor
Purpose
Ensure a feature or product is truly ready for launch.
Checklist
- Core functionality stable
- Metrics and analytics in place
- Rollback plan defined
- Support documentation ready
- Stakeholders aligned
Output
Readiness Status
Ready / At Risk / Not Ready
Critical Gaps
Launch Risks
Required Actions Before Launch
References
See worked example for a complete scenario.
More from pratikshadake/claude-product-management-skills
prd-critic
Evaluates PRD quality for clarity, testability, and build-readiness across problem clarity, scope, acceptance criteria, edge cases, and metrics. Use before sharing a PRD with engineering to catch gaps early.
20experiment-design
Designs fast, reliable validation experiments with hypothesis, method, success metric, and decision rules (Ship/Iterate/Kill). Use when you need to validate an assumption or test a product hypothesis before committing resources.
18assumption-mapper
Exposes hidden risks by identifying and ranking assumptions across desirability, feasibility, and viability categories. Use when evaluating new products or features to surface the highest-risk assumption to test first.
17roadmap-reality-checker
Detects unrealistic planning and hidden delivery risks like overcommitment, missing dependencies, resource mismatches, and undefined metrics. Use when reviewing quarterly roadmaps or sprint plans.
17problem-clarity
Evaluates whether a proposed idea addresses a genuine user problem worth solving. Use when assessing new feature ideas, startup concepts, or vague user complaints to determine if the pain justifies building a solution.
16user-segment-prioritizer
Identifies which user segment to focus on first using pain severity, willingness to pay, reachability, and strategic alignment. Use when choosing your initial target audience or re-evaluating segment focus.
16