product-manager

Create PRDs, user stories, and roadmaps with structured discovery intake.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/kvm9-dev/susanoo --skill product-manager-kvm9-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/kvm9-dev/susanoo/tree/main/.local/secondary_skills/product-manager
Command: npx skills add https://github.com/kvm9-dev/susanoo --skill product-manager-kvm9-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert a messy product idea into clear, decision-ready artifacts like PRDs, user stories, and roadmaps so teams can align and move forward.

Core Features & Use Cases

  • Discovery intake before writing: gathers key context (stage, team culture, decision type, audience, and competitive landscape needs) to pick the right document structure.
  • PRD format selection + high-signal templates: generates docs using well-known, production-tested formats (Amazon PR/FAQ, Intercom Intermission, Linear project spec) instead of generic placeholders.
  • Prioritization and acceptance: supports RICE/WSJF/Kano prioritization guidance, Gherkin-style acceptance criteria, and living-document workflow (versioning + changelog).

Quick Start

Ask the skill to create a PRD by first running a brief intake and then generating the best-matching PRD format for your product stage, team size, and the decision your document needs to enable.

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 from a rough product idea?

Writing a PRD from a rough idea requires a structured discovery intake to gather context on product stage and audience, which then selects a production-tested template like Amazon PR/FAQ or Intercom Intermission to produce a decision-ready document.

What is the best way to prioritize features for a product roadmap?

Prioritizing features for a product roadmap is best handled using established frameworks like RICE, WSJF, or Kano, which weigh reach, impact, confidence, and effort to sequence backlog items across cross-functional teams.

How do I write Gherkin acceptance criteria for user stories?

Writing Gherkin acceptance criteria for user stories involves structuring requirements using Given-When-Then syntax, ensuring clear, testable conditions that align development and stakeholder expectations within a living PRD document.

Can I use a DACI matrix to align stakeholders on a product decision?

Using a DACI matrix to align stakeholders maps Driver, Approver, Contributor, and Informed roles, clarifying decision authority and enabling cross-functional teams to move forward on product roadmap sequencing and feature prioritization.

When do I need an Amazon PR/FAQ versus a Linear spec for my product document?

Choosing between an Amazon PR/FAQ and a Linear spec depends on your product stage and decision type, where a discovery intake evaluates team culture and competitive landscape needs to select the right high-signal PRD format.

How do I maintain a living-document PRD with versioning and changelogs?

Maintaining a living-document PRD with versioning and changelogs tracks iterative updates to user stories and acceptance criteria, ensuring cross-functional teams reference the latest decision-ready outputs for feature prioritization.