role-po

Define product requirements, MVP scope, and agile user stories.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/ChoiHyunjin/ai_skills --skill role-po
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-po
Source: https://github.com/ChoiHyunjin/ai_skills/tree/main/skills/role-po
Command: npx skills add https://github.com/ChoiHyunjin/ai_skills --skill role-po

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps define product requirements, set MVP scope, and break down features for agile development, ensuring clear product direction.

Core Features & Use Cases

  • Requirements Definition: Clearly outlines goals, hypotheses, and success metrics.
  • Scope Management: Differentiates between Must-have and Nice-to-have features for MVP.
  • Agile Decomposition: Breaks down epics into user stories with acceptance criteria.
  • Use Case: A startup founder wants to define the MVP for a new mobile app. This Skill can guide them through defining the core features, user stories, and acceptance criteria.

Quick Start

Transition to the Product Owner role to define requirements for a new feature.

Frequently Asked Questions about role-po

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

FAQPage Schema
How do I define product requirements and set MVP scope for a new feature?

To define product requirements and set MVP scope, you outline goals, core hypotheses, and success metrics, differentiating between Must-have and Nice-to-have features. This approach defaults to MVP-first thinking to ensure clear product direction and avoid over-specification.

What is agile decomposition and how does it break down epics into user stories?

Agile decomposition breaks down epics into user stories with acceptance criteria. It transforms high-level feature definitions into actionable development tasks, ensuring each story aligns with the core product goals and MVP scope defined earlier.

Can I use this to manage scope for a startup mobile app MVP?

Yes, you can use this to manage scope for a startup mobile app MVP. It guides you through defining core features, user stories, and acceptance criteria, ensuring the MVP focuses on Must-have features and validates core hypotheses without over-specifying.

What's the best way to outline goals, hypotheses, and success metrics for agile development?

The best way to outline goals, hypotheses, and success metrics is to define them upfront during requirements definition. This process ensures clear product direction by establishing what you are testing, what success looks like, and the functional requirements needed.

What are the limitations of MVP-first thinking in product management?

The limitation of MVP-first thinking is that it intentionally avoids over-specification, focusing only on Must-have features to validate hypotheses. This means Nice-to-have features are deferred, which may limit initial product completeness but ensures faster validation of core assumptions.