product-manager

Create PRDs, FRs, NFRs, epics, and user stories from a project brief.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Ocean326/Agents --skill product-manager-ocean326
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/Ocean326/Agents/tree/main/skills/global/product-manager
Command: npx skills add https://github.com/Ocean326/Agents --skill product-manager-ocean326

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product planning can be error-prone without structured requirements. This Skill translates a project brief into comprehensive, testable requirements including PRDs, FRs, NFRs, epics, and user stories, ensuring clear scope, traceability, and ready-to-implement guidance.

Core Features & Use Cases

  • Create comprehensive Product Requirements Documents (PRDs) that capture scope, objectives, success criteria, and stakeholder alignment.
  • Define Functional Requirements (FRs) and Non-Functional Requirements (NFRs), prioritize features using MoSCoW, RICE, and Kano, and break work into epics and user stories.
  • Generate lightweight Technical Specifications for smaller projects and maintain traceability from requirements to implementation for audit and delivery.

Quick Start

Provide a project brief and I will generate a PRD and related artifacts.

Frequently Asked Questions about product-manager

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

FAQPage Schema
How do I write comprehensive product requirements from a project brief?

To write product requirements from a project brief, define comprehensive PRDs, epics, and user stories. This process ensures clear scope, stakeholder alignment, and ready-to-implement guidance for development teams.

How do I break down product requirements into epics and user stories?

Break down work into epics and user stories by translating high-level PRDs into smaller, actionable items. Explicit acceptance criteria are then attached to ensure the resulting user stories are fully testable.

What is requirements traceability and how does it apply to user stories?

Requirements traceability maps Functional Requirements directly to specific user stories and implementation tasks. This ensures every story delivers against a documented PRD objective for reliable audit and delivery.

Can I generate a lightweight technical specification for smaller projects?

Yes, you can generate lightweight Technical Specifications for smaller projects. This provides ready-to-implement guidance and testable scope without the overhead of a full PRD for faster delivery.

Do I need acceptance criteria for every user story in a PRD?

Yes, explicit acceptance criteria are needed for every user story to ensure requirements are testable. This validates that each story meets the documented Functional Requirements and scope objectives accurately.

How do I ensure product requirements are testable before development?

Ensure product requirements are testable by defining explicit acceptance criteria for each user story. This maintains traceability from high-level Functional Requirements down to implementation, validating scope and delivery.