skills.rest
kmshihab7878
kmshihab7878COMMUNITY
Explore all skills by this author →
GitHub

Product Manager

Generate product requirements documents with prioritized feature backlogs.

6|1|Updated Apr 7, 2026
Search Tags:#prioritization#prd#user-stories#acceptance-criteria#product-requirements#requirements-gathering
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill product-manager-kmshihab7878
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Product Manager
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/bmad/bmm/pm
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill product-manager-kmshihab7878

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product planning often lacks clear, testable requirements and prioritized scope, causing misaligned implementation and wasted engineering effort. This Skill guides teams to convert vision and briefs into structured, traceable Product Requirements Documents (PRDs), technical specifications, epics, and user stories ready for handoff.

Core Features & Use Cases

  • PRD generation: Guided workflows to create comprehensive Product Requirements Documents with functional and non-functional requirements and acceptance criteria.
  • Prioritization & scoping: Apply MoSCoW, RICE, and Kano to prioritize features and define MVP scope for Phase 2 projects.
  • Handoff-ready outputs: Break requirements into epics and stories, produce lightweight tech specs for small projects, and store artifacts for traceability and architecture handoff.
  • Use Case: A product manager receives a product brief for MyApp, runs the PRD workflow, captures FRs/NFRs, prioritizes features, and exports a handoff-ready document for architects and UX designers.

Quick Start

Invoke the /prd command and follow the guided prompts to generate a complete PRD with functional and non-functional requirements, epics, user stories, and acceptance criteria.

Frequently Asked Questions about Product Manager

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

FAQPage Schema
How do I create a PRD with testable acceptance criteria and user stories?▼

To create a PRD with testable acceptance criteria, you can use a guided workflow to translate product briefs into structured functional requirements, non-functional requirements, epics, and user stories that are ready for engineering handoff.

What is the best way to prioritize features for an MVP backlog?▼

Prioritizing features for an MVP backlog involves applying structured frameworks like MoSCoW, RICE, and Kano to evaluate and rank product requirements, ensuring properly scoped and traceable implementation.

How do you write epics and user stories from a product brief?▼

Writing epics and user stories from a product brief requires breaking down the overarching vision into structured product requirements and then decomposing those requirements into actionable, testable development tasks.

Can I generate technical specifications and requirements for architecture handoff?▼

Yes, you can generate lightweight technical specifications and comprehensive product requirements designed specifically for architecture handoff, ensuring cross-functional teams have traceable and properly scoped documentation.

Does this PRD workflow support both functional and non-functional requirements gathering?▼

Yes, the PRD workflow supports requirements gathering for both functional and non-functional requirements, capturing them comprehensively to prevent misaligned implementation and wasted engineering effort.

Related Skills

Explore More Product & Management Skills→
akvoakvo
2

bmad-pm

Generate product briefs, PRDs, and feature documents with prioritization frameworks.

Official
Advanced
webdevtodayjasonwebdevtodayjason
7

bmad-prd

Generate structured PRDs, architecture documents, epics, and user stories.

Community
Advanced
marcmontecalvomarcmontecalvo

bmad-create-epics-and-stories

Decompose product requirements into epics and user stories with acceptance criteria.

Community
Advanced
ChoiHyunjinChoiHyunjin

role-po

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

Community
Intermediate