product-management

Define product features from problem discovery through acceptance criteria.

3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/bipinks/ghost-office --skill product-management-bipinks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-management
Source: https://github.com/bipinks/ghost-office/tree/main/.claude/skills/product-management
Command: npx skills add https://github.com/bipinks/ghost-office --skill product-management-bipinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams struggle to convert vague ideas into concrete, testable features with clear acceptance criteria. This skill guides problem framing, requirements capture, and documentation to enable fast, reliable delivery.

Core Features & Use Cases

  • Requirements gathering templates and problem statements to anchor scope.
  • User stories with INVEST criteria and acceptance criteria to drive development and testing.
  • Prioritization frameworks (RICE, MoSCoW, Kano) and MVP slicing to plan releases.
  • Sprint planning, release planning, and stakeholder communications to align teams and stakeholders.
  • Documentation templates for feature specs, mapping, and release notes to maintain traceability.

Quick Start

Provide a problem statement or epic outline and the skill will generate a complete feature delivery plan.

Frequently Asked Questions about product-management

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

FAQPage Schema
How do I write user stories with clear acceptance criteria for feature development?

User stories with clear acceptance criteria are generated by applying INVEST principles to structure requirements, ensuring each feature has testable conditions. This frames problems and captures documentation to drive development and testing reliably.

What is the best way to prioritize product features using RICE or MoSCoW frameworks?

Prioritizing product features with RICE or MoSCoW frameworks involves scoring requirements against impact and urgency metrics. This approach enables structured MVP slicing and logical release planning to align engineering and operations teams.

How do I plan sprints and manage stakeholder communication for product releases?

Sprint planning and stakeholder communication are managed by generating structured release plans and communication artifacts. This aligns product, engineering, and operations contexts, ensuring stakeholders stay informed throughout the delivery lifecycle.

Can I use this for requirements gathering and problem framing in ERP contexts?

Requirements gathering and problem framing are fully supported in ERP contexts. The skill provides templates for problem statements and feature specifications, accommodating ERP-pattern considerations to anchor scope across complex operations.

How do I slice an MVP from a large epic for fast feature delivery?

Slicing an MVP from a large epic uses prioritization frameworks and estimation techniques to isolate core deliverables. This converts vague ideas into concrete, testable features with structured release planning and traceable documentation.