feature-results
Post-launch analysis and results documentation. Document what shipped and what we learned.
npx skills add majiayu000/claude-skill-registry --skill feature-results --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /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` - E
- Quick Start
- Pre-Launch Detection
- When to Use
- Quick Start Prompt
- Results Doc Structure
- 1. Executive Summary
- 2. Original Hypothesis
- 3. Results
- 4. Analysis
- 5. Learnings
- 6. Next Steps
- Output Template
- Root Cause Analysis
- Discovery Problem (Users don't know it exists)
What does the feature-results skill do?
Post-launch analysis and results documentation. Document what shipped and what we learned.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill feature-results --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.