product-brief

Guide product idea capture and generate structured Product Requirements Documents.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/hemory/amp --skill product-brief-hemory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-brief
Source: https://github.com/hemory/amp/tree/main/.claude/skills/product-brief
Command: npx skills add https://github.com/hemory/amp --skill product-brief-hemory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users articulate product ideas by guiding them through a series of questions, ultimately generating a comprehensive Product Requirements Document (PRD).

Core Features & Use Cases

  • Guided Idea Capture: Asks clarifying questions to flesh out initial product concepts.
  • Iterative Spec Building: Progresses through phases of understanding, specification, prioritization, and flow design.
  • PRD Generation: Creates a structured PRD document based on captured information.
  • Use Case: A product manager has a nascent idea for a new feature but struggles to define its scope and requirements. They use /product-brief to be prompted with questions, refine their vision, and generate a PRD.

Quick Start

Use the product-brief skill to start generating a PRD for a new notification system.

Frequently Asked Questions about product-brief

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

FAQPage Schema
How do I generate a PRD from a rough product idea?

Generating a PRD from a rough product idea involves a conversational process that asks clarifying questions to capture problem statements, target users, features, and technical requirements, ultimately producing a structured Product Requirements Document.

What is the best way to structure product requirements for a new feature?

The best way to structure product requirements is through iterative spec building that progresses through phases of understanding, specification, prioritization, and flow design to ensure comprehensive documentation for product development.

How does guided idea capture help define product scope?

Guided idea capture helps define product scope by asking targeted clarifying questions that flesh out initial concepts, allowing you to iteratively refine problem statements and feature prioritization.

Can I iteratively refine success metrics and technical requirements during spec writing?

Yes, you can iteratively refine success metrics and technical requirements during spec writing, as the process supports ongoing adjustments to problem statements and features throughout the documentation generation.

When do I need a Product Requirements Document for product management?

You need a Product Requirements Document for product management when you have a nascent product idea and struggle to define its scope, requiring structured documentation to align development teams on features and technical requirements.