product-manager

Create PRDs, user stories, roadmaps, and RICE prioritization frameworks for product teams.

Updated May 25, 2026
One-click install
npx skills add https://github.com/dheejay282002/final_project --skill product-manager-dheejay282002
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/dheejay282002/final_project/tree/main/.local/secondary_skills/product-manager
Command: npx skills add https://github.com/dheejay282002/final_project --skill product-manager-dheejay282002

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing product requirements documents, prioritizing backlogs, and planning roadmaps is time-consuming and often produces generic outputs that don't match real team workflows. This Skill generates PRDs, user stories, and roadmaps using proven templates from companies like Amazon, Intercom, and Linear. ## Core Features & Use Cases - PRD Generation: Choose from Amazon PR/FAQ, Intercom Intermission, or Linear Project Spec formats based on team size and culture, with DACI stakeholder mapping and competitive landscape sections. - Prioritization Frameworks: Score features with RICE, WSJF, or Kano models, including scope estimation via t-shirt sizing or reference-class estimation. - Roadmaps & Acceptance Criteria: Build Now/Next/Later roadmaps linked to OKRs and write Gherkin Given/When/Then acceptance criteria. - Use Case: A startup PM needs a one-page spec for a new feature. After a short intake about stage, audience, and decision context, the Skill produces an Intercom-style Intermission with job stories, success criteria, and explicit non-goals. ## Quick Start Ask the assistant to write a PRD for your new feature using the product-manager skill, answering its intake questions about product stage, team size, and audience.

Frequently Asked Questions about product-manager

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

FAQPage Schema
How do I write a PRD for a new product feature?▼

Start with a short intake covering product stage, team size, the decision the document enables, and the audience. Then pick a format: Amazon PR/FAQ for big bets needing exec alignment, Intercom's one-page Intermission for feature work, or Linear's project spec for eng-heavy teams.

What is the RICE prioritization framework and how do I score features?▼

RICE scores features as (Reach x Impact x Confidence) / Effort. Reach is users affected per quarter, Impact ranges 0.25 to 3, Confidence is a percentage punishing guesses, and Effort is person-months across all functions. Output can be generated as a CSV spreadsheet.

When should I not use RICE for backlog prioritization?▼

Skip RICE when effort estimates are unreliable at early stages, when one item is existential and must ship regardless, or when the list exceeds 30 items, which signals a strategy problem rather than a prioritization problem. Consider WSJF when timing and deadlines matter.

How do I write acceptance criteria in Gherkin format?▼

Write one scenario per criterion using Given/When/Then syntax: Given a precondition, When an action occurs, Then an observable result follows. If a requirement cannot be expressed this way, it is ambiguous and needs clarification before development.

Can this skill integrate with Jira or Linear directly?▼

No, it cannot connect to Jira, Linear, or Asana APIs. Deliverables are produced as markdown or CSV for copy-paste into your tool, and output can be formatted to match Linear's project spec conventions when relevant.