product-brief

Converts raw stakeholder intake into a signed-off Product Brief for Sign-Off 1.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill product-brief-muhammaddadu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-brief
Source: https://github.com/muhammaddadu/ai-skill-collection/tree/main/1-exploration/product-brief
Command: npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill product-brief-muhammaddadu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? New feature requests and ideas often arrive as vague, solution-shaped asks, and teams jump into Discovery or delivery without agreed intent, constraints, or success criteria. This Skill turns raw intake into a one-to-two page Product Brief that earns Sign-Off 1 before any Discovery work begins. ## Core Features & Use Cases - Intake-to-Intent Framing: Captures the original ask verbatim, then separates the underlying outcome (intent) from the proposed solution through structured questioning. - Stakeholder-Elicited Constraints and Success Criteria: Records hard and soft constraints with owners, and pushes every success criterion to a metric, target, and time horizon. - Sign-Off 1 Gate Checklist: Verifies intent clarity, explicit constraints, measurable success, and agreed priority, then records formal sign-off before handing off to Discovery. - Use Case: A stakeholder messages "we need a dashboard." Use this Skill to capture the ask verbatim, uncover that the real intent is reducing weekly reporting time, document constraints and measurable success criteria, and produce a signed-off brief at docs/product/briefs/reporting-dashboard.md. ## Quick Start Turn this stakeholder request into a Product Brief using the product-brief skill and prepare it for Sign-Off 1.

Frequently Asked Questions about product-brief

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

FAQPage Schema
How do I write a product brief from a stakeholder request?▼

Capture the original ask verbatim, then interview stakeholders to separate the underlying intent from the proposed solution. Record hard and soft constraints, measurable success criteria, out-of-scope items, and a priority rationale using the product-brief-template.md structure.

What is the difference between a product brief and a PRD?▼

A product brief frames intent, constraints, success criteria, and scope at one to two pages and is approved at Sign-Off 1 before Discovery. A PRD comes after the gate and specifies the actual solution, user flows, and requirements in detail.

When should I use a problem statement instead of a product brief?▼

Use a problem statement when there is no concrete ask yet, only a vague sense that something is wrong in an area. Once a specific request or idea exists, the product brief adds stakeholders, constraints, success criteria, scope, and priority on top of that framing.

What makes success criteria measurable in a product brief?▼

Each criterion needs a metric, a numeric target, and a time horizon, such as reducing report generation time to under five minutes by Q3. Criteria that cannot be quantified yet must be recorded explicitly as hypotheses for Discovery, not dressed up as criteria.

Can I skip the sign-off gate for small requests?▼

No, the Sign-Off 1 gate is unconditional regardless of request size. For genuinely small asks the brief can be half a page, but a recorded sign-off with approver, date, and conditions is still required before Discovery starts.