Generate a structured Markdown post-launch feature results document.
npx skills add https://github.com/coalesce-labs/catalyst --skill feature-results
Please help me install this Agent Skill. Skill: feature-results Source: https://github.com/coalesce-labs/catalyst/tree/main/plugins/pm/skills/feature-results Command: npx skills add https://github.com/coalesce-labs/catalyst --skill feature-results
Post-launch analysis and results documentation to capture what shipped and what we learned.
Run the feature-results workflow after a feature ships: provide the feature name, ship date, original hypothesis, and actual results to generate the comprehensive results document.
High-intent search queries and answers about installing and using this skill.
Automate post-launch analysis by running the feature-results workflow with the feature name, ship date, original hypothesis, and actual results. It consolidates goals, metrics, root-cause-analysis, and learnings into a structured Markdown report.
A comprehensive feature results document includes an executive summary, original hypothesis, primary metrics, segment breakdowns, root-cause-analysis, calibration, and next steps. This structure captures what shipped and what was learned for stakeholder communication.
Compare planned versus actual results by pulling original hypotheses and targets from PRDs and MCPs. The feature-results workflow matches these inputs against actual post-launch metrics to generate a calibration analysis within the final Markdown report.
Yes, you can generate an executive summary and stakeholder update by feeding post-launch metrics into the feature-results workflow. It outputs structured Markdown artifacts containing results, analysis, and follow-up actions suitable for team alignment.
No, a PRD or MCP connection is not strictly required to perform segment analysis, but connecting them allows the feature-results workflow to automatically pull original hypotheses and targets, enriching the post-launch calibration and root-cause-analysis.
The best way to consolidate root-cause-analysis and next steps is using a structured post-launch workflow. It captures segment insights and follow-up actions, outputting a comprehensive Markdown results document that aligns stakeholders on what was learned.
bketelsenGenerate a lightweight Product Requirements Document defining vision, user problems, and success metrics.
cklxxConvert meeting notes into structured Markdown summaries with decisions and action items.
limzivectorAudit developer experience against planned goals and generate a scorecard.
pisithrpsDocument post-launch feature performance and synthesize learnings into a structured markdown results document.
