product-manager

Define product vision, user stories, and acceptance criteria for software development.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bennie-ng/AgCel --skill product-manager-bennie-ng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/bennie-ng/AgCel/tree/main/skills/product-manager
Command: npx skills add https://github.com/bennie-ng/AgCel --skill product-manager-bennie-ng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of translating high-level business objectives into actionable product requirements, ensuring alignment between stakeholders and development teams.

Core Features & Use Cases

  • Requirement Elicitation: Gathers detailed user needs through targeted questions.
  • User Story & Acceptance Criteria: Crafts clear, testable user stories and their corresponding acceptance criteria.
  • Roadmap Planning: Assists in defining product vision, prioritizing features using methods like MoSCoW, and identifying the Minimum Viable Product (MVP).
  • Use Case: A startup needs to define the core features for their new mobile app. This Skill can help them articulate the product vision, write user stories for key functionalities like user registration and profile management, and define the acceptance criteria for each.

Quick Start

Use the product-manager skill to write a user story for a new feature.

Frequently Asked Questions about product-manager

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

FAQPage Schema
How do I write user stories and acceptance criteria for software development?

Defining a Minimum Viable Product requires identifying core functionalities through requirement elicitation and prioritizing features. Structuring these prioritized features into a clear product vision ensures alignment between stakeholders and development teams.

How do I create a product roadmap from high-level business objectives?

Creating a product roadmap from high-level business objectives involves defining the product vision and prioritizing features using methods like MoSCoW. This process translates overarching goals into actionable development plans.

What is the best way to define a Minimum Viable Product for a new app?

Defining a Minimum Viable Product requires identifying core functionalities through requirement elicitation and prioritizing features. Structuring these prioritized features into a clear product vision ensures alignment between stakeholders and development teams.

Can I use this approach to align stakeholders with development teams?

Yes, you can align stakeholders with development teams by translating high-level business objectives into actionable product requirements. Crafting clear user stories and acceptance criteria ensures everyone shares a unified, testable specification.

When do I need to use MoSCoW prioritization for product management?

You need to use MoSCoW prioritization during roadmap planning to categorize features by importance. This method helps define the Minimum Viable Product by clearly separating must-have features from nice-to-have items.