product-brief-writer

Writes one-page product briefs using evidence from context files to secure stakeholder buy-in.

Updated May 18, 2026
One-click install
npx skills add https://github.com/fahadnari/Claude-skills --skill product-brief-writer-fahadnari
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-brief-writer
Source: https://github.com/fahadnari/Claude-skills/tree/main/product-brief-writer/product-brief-writer
Command: npx skills add https://github.com/fahadnari/Claude-skills --skill product-brief-writer-fahadnari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a full PRD is overkill when you only need initial approval to explore an idea. This Skill produces a focused one-page product brief that answers the problem, why now, and the specific ask, so PMs can get buy-in before investing in detailed specs. ## Core Features & Use Cases - Context-grounded evidence: Pulls pain points, known issues, strategic priorities, and competitor data from context files (personas.md, product.md, company.md, competitors.md) to support the brief. - Structured one-page template: Covers problem definition, why now, solution direction, impact and effort sizing, explicit ask, risks, and open questions. - Guided input gathering: Asks clarifying questions when the problem, target persona, or request is unclear instead of writing an unsupported brief. - Use Case: A PM wants approval for two sprints of discovery on a reporting feature. The Skill cites persona pain points and competitor gaps from context files, sizes the effort, and states the exact decision needed. ## Quick Start Ask the assistant to write a product brief for your feature idea, describing the problem, who has it, and what decision or resources you are requesting.

Frequently Asked Questions about product-brief-writer

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

FAQPage Schema
How do I write a one-page product brief to get leadership buy-in?▼

State the problem and affected persona first, back it with evidence from context files, explain why now, propose a high-level solution direction, and end with a specific ask such as discovery sprints or approval to proceed. Keep it to one page.

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

A product brief is a one-page pitch used to get initial buy-in before investing in discovery or specs. A PRD is a detailed specification written after approval. Use the brief to earn the right to write the PRD.

What inputs do I need to provide for a product brief?▼

At minimum, provide the problem you are solving, who experiences it, and evidence it is worth solving. Helpful additions include a rough solution direction, competitor context, effort sizing, and your specific ask such as time, people, or a decision.

Does the product brief writer use my existing product context files?▼

Yes. It reads context files such as personas.md, product.md, company.md, and competitors.md to pull persona pain points, known issues, strategic priorities, and competitive landscape as evidence for the brief.

When should I not use a one-page product brief?▼

Skip the brief when the initiative is already approved and needs detailed requirements, or when the problem is not yet understood well enough to state clearly. In the latter case, gather problem clarity first before pitching.