product-manager

Convert project briefs into PRDs, epics, user stories, and acceptance criteria.

2|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/haotool/app --skill product-manager-haotool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/haotool/app/tree/main/.agents/skills/product-manager
Command: npx skills add https://github.com/haotool/app --skill product-manager-haotool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to translate high-level ideas into testable, traceable requirements, causing misalignment and rework.

Core Features & Use Cases

  • Generate comprehensive FRs, NFRs, epics, and user stories from briefs
  • Prioritize features using MoSCoW, RICE, and Kano with end-to-end traceability
  • Produce lightweight PRDs and technical specifications aligned to project level
  • Validate requirements with acceptance criteria and testability across teams

Quick Start

Provide a project brief and ask the skill to generate a PRD outline with epics and stories.

Frequently Asked Questions about product-manager

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

FAQPage Schema
How do I convert a project brief into a PRD with epics and user stories?

To convert a project brief into a PRD, you input the brief and the skill generates a comprehensive outline containing epics, user stories, and functional requirements. This bridges high-level vision to actionable product plans.

What is the best way to prioritize product features using MoSCoW and RICE?

Prioritizing features using MoSCoW and RICE involves evaluating requirements against these frameworks to determine value and urgency. The skill applies these models to generate prioritized features with end-to-end traceability.

How do I write testable acceptance criteria for functional and non-functional requirements?

Writing testable acceptance criteria for functional and non-functional requirements means defining specific validation conditions for each user story. The skill validates requirements by generating testable acceptance criteria across teams.

Can I generate lightweight technical specifications for Level 0-2 projects?

You can generate lightweight technical specifications for Level 0-2 projects by providing a project brief. The skill produces lightweight PRDs and technical specifications aligned to the specific project level.

How does traceability matrix generation work for software requirements?

Traceability matrix generation for software requirements works by linking user stories, epics, and features back to their original briefs and prioritization scores. The skill ensures end-to-end traceability across the product lifecycle.

Do I need a detailed brief to generate FRs and NFRs for multi-team programs?

You do not need an overly detailed brief to generate FRs and NFRs for multi-team programs. The skill works across product lifecycles from discovery briefs to implementation-ready specs for multi-team programs.