feature-resultslisted

# /feature-results - Post-Launch Analysis Document feature results and capture learnings. ## Quick Start ``` /feature-results ``` Then provide: 1. **Feature name** and ship date 2. **Original hypothesis** (or I'll pull it from your PRD) 3. **Actual results** (metrics, or I'll query your analytics MCP) I'll generate a results doc with: executive summary, results vs targets, root cause analysis (if missed), segment breakdown, estimate calibration, stakeholder communication guidance, and concrete next steps. **Output:** Saved to `outputs/analyses/feature-results-[name]-[date].md` **Time:** ~10 min with data ready, ~20 min if we need to dig --- ## Pre-Launch Detection Before generating a results analysis, verify the feature has actually shipped. **Check for launch signals:** - Does the PRD in `context-library/prds/` or `outputs/prds/` show status "Shipped" or "Launched"? - Does the PM mention actual results data (not projections)? **If the feature hasn't launched yet:** ``` It looks like [feature] hasn't shipped yet. Post-launch analysis works best with real data. For pre-launch work, you might want: - `/feature-metrics` - Define what you'll measure before launch - `/impact-sizing` - Estimate expected impact - `/experiment-decision` - Plan your A/B test or rollout - `/launch-checklist` - Make sure you're ready to ship Want to proceed anyway (e.g., analyzing a soft launch or pilot), or switch to one of these? ``` --- ## When to Use - After A/B test completes - After