product-manager

Converts vague ideas into bounded proposals, user stories, acceptance criteria, and MVP/V2 scope definitions.

2|Updated Jun 13, 2025
One-click install
npx skills add https://github.com/mattszein/pro-rails --skill product-manager-mattszein
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/mattszein/pro-rails/tree/main/.claude/skills/product-manager
Command: npx skills add https://github.com/mattszein/pro-rails --skill product-manager-mattszein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this Skill when you need to turn an uncertain feature idea into a clear product proposal. It helps you define who benefits, what problem is being solved, and why the feature matters before any build work starts.

Core Features & Use Cases

  • Scope clarification: Break a rough idea into a bounded feature with explicit MVP, V2, and out-of-scope items.
  • User-centered planning: Translate product ideas into user stories, acceptance criteria, and persona impact.
  • Integration thinking: Map how a new feature affects authentication, authorization, notifications, real-time behavior, support, and multilingual content.
  • Tradeoff analysis: Compare approaches and document the product decisions that shape what should be built first.
  • Use case: A founder wants to add team invitations to an app; this Skill helps define the problem, affected users, rollout scope, and key tradeoffs in a form an architect can use.

Quick Start

Ask the product-manager skill to turn your feature idea into a scoped proposal with user stories, integration points, tradeoffs, and clear MVP boundaries.

Frequently Asked Questions about product-manager

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

FAQPage Schema
How do I turn a vague product idea into clear user stories and acceptance criteria?

Product planning for a new feature requires defining the target persona, problem context, and scope boundaries to generate a bounded proposal. This structures rough concepts into explicit MVP, V2, and out-of-scope items before build work starts.

How do I define MVP scope and plan V2 feature boundaries for a new product?

Defining MVP scope involves breaking a rough idea into bounded features with explicit MVP, V2, and out-of-scope items. This clarifies what should be built first and separates immediate user needs from future enhancements.

What integration points should I consider when planning feature scope for an existing product?

When planning feature scope, consider integration points across authentication, authorization, notifications, real-time behavior, support, and multilingual content. Mapping these dependencies ensures the new feature fits cohesively into the existing product architecture.

How do I evaluate product tradeoffs when deciding what to include in a feature rollout?

Evaluating product tradeoffs involves comparing approaches and documenting the decisions that shape what should be built first. This helps prioritize features within the MVP scope by analyzing their impact on affected users and system integrations.

Can I use product planning techniques to map authorization and real-time behavior requirements?

Yes, product planning explicitly maps how a new feature affects authentication, authorization, notifications, and real-time behavior. This ensures technical integration requirements are documented alongside user stories and acceptance criteria.