Does this skill work with other Claude skills?

Yes, it is designed to receive input from Business Analyst skills and hand off output to System Architect or Scrum Master skills for a complete development lifecycle.

Can I use this for small projects without a full PRD?

Yes, the skill includes a /tech-spec command specifically designed for Level 0-1 projects that require lightweight technical documentation rather than a full PRD.

What does the /prd command do in this skill?

The /prd command initiates a structured workflow to create a comprehensive Product Requirements Document, including functional requirements, non-functional requirements, and epics.

How does the skill handle feature prioritization?

It utilizes MoSCoW (Must, Should, Could, Won't), RICE (Reach, Impact, Confidence, Effort), and the Kano Model to help users make data-driven decisions about project scope.

Product Management Planning

Name: Product Management Planning
Author: delorenj

bydelorenj

•

Collaboration Tools

Generates comprehensive product requirements documents and technical specifications to bridge the gap between vision and development.

About

The Product Management skill is a specialized Phase 2 planning tool designed to transform high-level product visions into actionable development roadmaps. It enables Claude to function as a senior product manager, facilitating the creation of detailed Product Requirements Documents (PRDs) and technical specifications while utilizing industry-standard prioritization frameworks like MoSCoW and RICE. By ensuring requirements are testable, traceable, and aligned with user value, this skill provides a structured bridge between business analysis and system architecture, making it indispensable for teams moving from concept to implementation.

Key Features

Feature prioritization using MoSCoW, RICE, and Kano frameworks
Epic and user story breakdown from high-level goals
5 GitHub stars
Requirement validation for testability and traceability
Automated PRD and Technical Specification generation
Functional and non-functional requirement definition

Use Cases

Translating a business brief into a detailed product roadmap
Prioritizing feature backlogs for MVP development
Validating existing project documentation for scope gaps

About

Key Features

Feature prioritization using MoSCoW, RICE, and Kano frameworks
Epic and user story breakdown from high-level goals
5 GitHub stars
Requirement validation for testability and traceability
Automated PRD and Technical Specification generation
Functional and non-functional requirement definition

Use Cases

Translating a business brief into a detailed product roadmap
Prioritizing feature backlogs for MVP development
Validating existing project documentation for scope gaps