product-manager_skill

Overview

This skill is a product requirements and planning specialist that creates PRDs, lightweight tech specs, prioritized backlogs, and traceable epics and user stories. It ensures functional and non-functional requirements are measurable, testable, and scoped to project level so teams can move from strategy to implementation with confidence.

How this skill works

Given project context or a product brief, the skill gathers stakeholder inputs, categorizes requirements as FRs or NFRs, assigns unique IDs and priorities, and defines acceptance criteria. It breaks epics into user stories, applies prioritization frameworks (MoSCoW, RICE, Kano), and produces a validated PRD or tech spec with traceability links to business objectives.

When to use it

• Create a PRD for Level 2+ projects that need cross-functional alignment
• Produce a lightweight tech spec for Level 0-1, fast-delivery tasks
• Define clear functional and non-functional requirements with acceptance criteria
• Prioritize features for an MVP using MoSCoW or RICE scoring
• Break large epics into testable user stories and acceptance criteria
• Validate or review existing requirements for completeness and traceability

Best practices

• Put user value first: each requirement must map to a clear outcome or metric
• Make every requirement testable with explicit acceptance criteria
• Right-size documentation to project level: full PRD for complex work, tech spec for tactical work
• Prioritize ruthlessly; use MoSCoW for scope decisions and RICE for quantitative ranking
• Avoid prescribing implementation details—describe WHAT and WHY, not HOW
• Maintain a traceability matrix linking requirements → epics → stories → objectives

Example use cases

• Draft a PRD for a new user dashboard that lists FRs, NFRs, epics, and a traceability matrix
• Create a tech spec for a single-team feature with scope, approach, and test scenarios
• Run RICE scoring across epics to produce a prioritized release backlog
• Transform stakeholder interviews into numbered FRs/NFRs with clear acceptance criteria
• Review an existing PRD and validate IDs, priorities, acceptance criteria, and dependencies