product-manager

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

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/AmirEmad11/instabot --skill product-manager-amiremad11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/AmirEmad11/instabot/tree/main/.local/secondary_skills/product-manager
Command: npx skills add https://github.com/AmirEmad11/instabot --skill product-manager-amiremad11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing product requirement documents, prioritizing backlogs, and building roadmaps is time-consuming and often produces generic templates that don't fit your team's context. This Skill generates PRDs, user stories, and roadmaps using proven formats from top product organizations like Amazon, Intercom, and Linear. ## Core Features & Use Cases - Context-aware PRD formats: Choose between Amazon PR/FAQ (Working Backwards), Intercom's one-page Intermission, or Linear's Project Spec based on team size, product stage, and audience. - Prioritization frameworks: Score features with RICE, WSJF (Cost of Delay), or Kano surveys, with guidance on when each framework applies. - Roadmaps and acceptance criteria: Build Now/Next/Later roadmaps linked to OKRs and write Gherkin-style Given/When/Then acceptance criteria. - Use Case: A startup PM needs executive buy-in for a new feature. The Skill runs a discovery intake, maps stakeholders with a DACI matrix, drafts an Amazon-style PR/FAQ, and scores the backlog with RICE exported as CSV. ## Quick Start Ask the assistant to write a PRD for your feature idea and answer its discovery 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 discovery intake covering product stage, team size, decision audience, and competitive landscape. 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?

RICE scores features as (Reach x Impact x Confidence) / Effort, where Reach is users affected per quarter, Impact is 0.25-3, Confidence is a percentage, and Effort is person-months across all functions. Avoid RICE when effort estimates are unreliable or the list exceeds 30 items.

Amazon PR/FAQ vs Intercom Intermission: which PRD format should I use?

Use Amazon PR/FAQ for big bets and new product lines requiring executive alignment before committing engineering resources. Use Intercom's one-page Intermission for feature-level work with fast-moving teams where scope creep is the main risk.

How do I write acceptance criteria in Gherkin format?

Write one scenario per criterion using Given (precondition), When (action), Then (observable result), and optional And clauses. If a requirement cannot be expressed as Given/When/Then, the requirement itself is ambiguous and needs clarification.

Can this skill integrate with Jira or Linear?

No, it cannot directly integrate with Jira, Linear, or Asana. Output is delivered as markdown or CSV for copy-paste, though it can format output to match tool conventions like Linear's project spec if integrations exist in the workspace.

When should I not use RICE for prioritization?

Skip RICE when effort estimates are unreliable at early stages, when one item is existential and should just be done, or when the backlog exceeds 30 items, which signals a strategy problem rather than a prioritization problem.