resonance-ops-product

Define product scope through Working Backwards PRDs, RICE prioritization, and PMF diagnostics.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-product-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resonance-ops-product
Source: https://github.com/manusco/wolfgang/tree/main/.agents/skills/ops/product
Command: npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-product-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often build features without validated demand, prioritize roadmaps by gut feel, and ship tickets that say "Build X" without explaining why it matters to users. This Skill enforces validation before implementation so engineering effort goes toward evidenced customer needs. ## Core Features & Use Cases - Working Backwards PRDs: Drafts Press Release format PRDs with premises, 10x vision, narrowest wedge scope, and success metrics so engineering can estimate without clarifying questions. - RICE Prioritization: Scores backlogs with (Reach x Impact x Confidence) / Effort, presenting assumptions so users can challenge inputs rather than outputs. - PMF Diagnostics: Applies the Sean Ellis 40% test and pivot frameworks (zoom in, zoom out, customer, need, channel) to determine whether to iterate, pivot, or scale. - Use Case: A founder says "add dark mode." The Skill maps the request to an Opportunity in the Opportunity Solution Tree, asks for demand evidence, and requires a RICE score before any PRD is written. ## Quick Start Ask the product manager skill to evaluate a feature idea and produce a Working Backwards PRD with a RICE-scored priority ranking.

Frequently Asked Questions about resonance-ops-product

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize a product backlog with RICE scoring?▼

RICE scoring ranks features by (Reach x Impact x Confidence) / Effort. Estimate each input per feature, compute the score, and sort descending. Present the assumptions behind each score so stakeholders can challenge the inputs rather than the ranking.

How do I write a PRD using the Working Backwards method?▼

Working Backwards starts with a Press Release written before any code: headline, customer quote, problem, solution, and call to action. Add an FAQ for hard questions, then define the narrowest wedge version that ships this week.

What is the Sean Ellis test for product-market fit?▼

The Sean Ellis test asks users how they would feel if they could no longer use the product. If 40% or more answer "very disappointed," you have a PMF signal. Below 40%, evaluate pivots across product, market, or channel before scaling acquisition.

When should a feature request be rejected before engineering?▼

Reject a feature request when it lacks evidenced customer demand or cannot map to an Opportunity in the Opportunity Solution Tree. A ticket that says "Build X" without explaining why it matters to the user is a failure condition.

What is the difference between scope expansion and scope reduction?▼

Scope expansion pushes toward the 10x ideal version for greenfield or core-value features. Scope reduction strips a plan to the minimum that ships value. Choose one mode explicitly and commit rather than drifting between them.