- Home
- Skills
- Whawkinsiv
- Solo Founder Superpowers
- Product Strategy Prioritization
product-strategy-prioritization_skill
142
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill whawkinsiv/solo-founder-superpowers --skill product-strategy-prioritization- SKILL.md4.0 KB
Overview
This skill helps founders and product leaders prioritize what to build next, define a razor-focused MVP, and create a pragmatic roadmap for early-stage SaaS. It combines ruthless prioritization with hypothesis-driven product thinking so you ship the smallest thing that tests the biggest assumption. Use it to decide feature trade-offs, score ideas, and align teams around measurable outcomes.
How this skill works
The skill inspects proposed features and product goals, reframes them as user problems, and applies an adapted RICE scoring model to rank opportunities. It prescribes an MVP definition process that forces one problem, one persona, and the minimum experience that delivers real learning. It returns a clear recommendation, v1 scope, risks and mitigations, and success metrics for fast validation.
When to use it
- You need to choose what to build next from a backlog of ideas.
- You're launching a first or second MVP and must cut scope ruthlessly.
- You want to rank feature requests objectively (RICE-adapted).
- A customer or sales ask threatens to derail product focus.
- You're planning a 2–4 week experiment to validate a key hypothesis.
Best practices
- Always restate the user problem before evaluating solutions.
- Score features with Reach, Impact, Confidence, and Effort, then use judgment.
- Ship the smallest thing that tests the biggest assumption; prefer speed over completeness.
- Treat product work as hypothesis testing: instrument before launch and schedule a review.
- Say no with context: acknowledge the problem, explain priorities, and offer workarounds.
Example use cases
- Convert a long feature list into a ranked roadmap using RICE scores and qualitative checks.
- Define a 2–4 week MVP that answers whether a persona will complete a core task.
- Reject a custom feature request from a single customer while proposing an alternative path.
- Create a launch checklist that includes instrumentation, support docs, and a 2-week impact review.
- Design a focused competitive wedge to win a narrow, underserved segment.
FAQ
Be very strict. Narrow focus reduces unknowns and speeds learning. You can expand once the core hypothesis is validated.
When should I ignore the RICE score?
Use RICE as a conversation starter. Override scores when new evidence, strategic constraints, or regulatory risk change the calculus.