product-designer

Frame product ideas into problem statements, opportunity assessments, and MVP scopes.

2|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/rakibulism/agent-skills-os --skill product-designer-rakibulism
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-designer
Source: https://github.com/rakibulism/agent-skills-os/tree/main/skills/product-designer
Command: npx skills add https://github.com/rakibulism/agent-skills-os --skill product-designer-rakibulism

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams decide what to build before they design screens or write specs. It frames the real user problem, checks whether the opportunity is worth pursuing, and turns vague feature ideas into clear product decisions with measurable outcomes.

Core Features & Use Cases

  • Problem framing: Recast feature requests into a specific user, job, current workaround, and cost.
  • Opportunity sizing and prioritization: Estimate reach, urgency, and business upside to tell a painkiller from a vitamin.
  • Solution exploration: Compare do-nothing, manual, off-the-shelf, minimal build, and full build options before committing.
  • Success metrics: Define a primary metric, guardrail, and counter-metric before launch.
  • MVP scoping: Cut scope into in, deferred, and out so the smallest test can still produce a real signal.
  • Example use case: A product manager asks whether a requested onboarding feature is worth building, and this Skill produces a brief with the problem statement, solution options, metric targets, and riskiest assumptions.

Quick Start

Ask the product designer skill to turn my feature idea into a problem statement, opportunity assessment, MVP scope, and success metrics.

Frequently Asked Questions about product-designer

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

FAQPage Schema
How do I frame a feature request into a measurable product problem statement?

Problem framing recasts feature requests by identifying the specific user, their job, current workaround, and cost. This structured approach turns vague ideas into decision-ready problem statements before committing resources to design or development.

What is the best way to size an opportunity and decide if a feature is worth building?

Opportunity sizing estimates reach, urgency, and business upside to distinguish a painkiller from a vitamin. This assessment helps teams prioritize features by evaluating the potential business impact and user value before investing in a build.

How do I scope an MVP to test riskiest assumptions with the smallest effort?

MVP scoping divides features into in, deferred, and out categories. This method ensures the smallest possible test can still produce a real signal, validating riskiest assumptions without overcommitting development resources to a full build.

What success metrics should I define before launching a new product feature?

Success metrics require defining a primary metric, a guardrail, and a counter-metric before launch. This framework ensures you measure the intended outcome while monitoring potential negative side effects on user behavior or business health.

Can I compare different solution options like manual workarounds versus a full build?

Solution exploration compares do-nothing, manual, off-the-shelf, minimal build, and full build options. Comparing these alternatives before committing ensures you select the most viable approach for the problem rather than defaulting to custom development.

Do I need structured input to generate a product brief for a should we build this question?

Generating a product brief requires structured input about the user problem, business context, and goal. This input is necessary to produce rationale, assumptions, and scoped recommendations for prioritization and discovery work.