The problem

Engineering and design teams often jump straight into implementation without defining the actual user pain or business value. This leads to scope creep, wasted development cycles on low-impact features, and products that fail to move core metrics.

What it does

• Synthesizes vague feature requests into structured Problem Statements and User Pain Points.
• Defines clear Goals and Success Metrics to ensure every feature is measurable.
• Performs quick-turn Competitive Analysis to identify market gaps and opportunities.
• Applies MoSCoW prioritization to aggressively cut non-essential scope before coding starts.
• Generates comprehensive PRD outlines and concrete next steps for development teams.

Why this beats prompting it yourself

General-purpose LLMs often produce vague, repetitive "corporate speak." This skill enforces an opinionated, industry-standard framework that demands concrete user quotes, specific metrics, and hard prioritization choices that save actual development time.

Use cases

• Transforming a stakeholder's "idea" into a structured feature proposal.
• Evaluating the UX and competitive positioning of a new product vertical.
• Prioritizing a bloated backlog using structured frameworks like MoSCoW.
• Drafting the foundational outline for a formal Product Requirements Document.