post-launch-learning
Post-Launch Learning Engine
Purpose
Turn launches into structured learning for better future decisions.
Steps
- Compare expected vs actual outcomes.
- Identify what worked.
- Identify what failed.
- Extract root causes.
- Define next actions.
Output
Expected Outcome
Actual Result
What Worked
What Didn't
Key Learnings
Next Actions
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.
20launch-readiness
Audits whether a feature or product is truly ready for launch with a structured checklist and readiness status (Ready/At Risk/Not Ready). Use before any product launch to catch critical gaps.
18experiment-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.
18value-vs-effort
Prioritizes features using structured scoring across user impact, revenue potential, strategic alignment, confidence, and engineering effort. Use when deciding which feature to build next or comparing competing priorities.
17assumption-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.
17