new-product-brief

Guides a nine-step structured interview that produces a PRODUCT_BRIEF.md before writing code.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/naorez92-svg/printa4 --skill new-product-brief-naorez92-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-product-brief
Source: https://github.com/naorez92-svg/printa4/tree/main/.claude/skills/new-product-brief
Command: npx skills add https://github.com/naorez92-svg/printa4 --skill new-product-brief-naorez92-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams that start coding a new product without a shared definition end up with duplicated business logic, inconsistent terminology, unplanned database migrations, and security models bolted on after launch. This Skill runs a structured founding session that captures every critical decision in one PRODUCT_BRIEF.md document before a single line of code is written. ## Core Features & Use Cases - Nine-step guided interview: Walks through Amazon PRFAQ, Jobs To Be Done, Shape Up appetite and rabbit holes, business model and quotas, technical architecture, database schema, design tokens and terminology, distribution, and MVP scope. - Single source of truth output: Generates a complete PRODUCT_BRIEF.md covering pricing tables, secrets mapping, CORS policy, OWASP checklist, RLS policies, lifetime counters, approved terminology, and launch metrics. - Pre-code checklist: Enforces ten verification gates (constants file, secrets mapping, RLS, analytics events, pre-launch list) before development begins. - Use Case: A founder says "I want to build a new SaaS app." The Skill runs a 45-90 minute structured session, captures all 45 decisions, and outputs a PRODUCT_BRIEF.md that every future coding agent reads first. ## Quick Start Ask the assistant to run the new-product-brief founding session for your product idea and answer the nine stages of questions to generate your PRODUCT_BRIEF.md.

Frequently Asked Questions about new-product-brief

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

FAQPage Schema
How do I plan a new product before writing code?

Run a structured founding session that captures positioning, customer jobs, scope, business model, architecture, and launch plan in one document. This Skill guides you through nine stages and 45 questions, then generates a PRODUCT_BRIEF.md that all future development work references.

What is a PRFAQ and how do I write one?

A PRFAQ is Amazon's Working Backwards method where you write a future press release and FAQs before building anything. It includes a headline, opening paragraph, customer quote, three external FAQs, and three internal FAQs that force clarity on the product definition.

What should a product brief include for a SaaS MVP?

A complete brief covers the one-liner positioning, JTBD struggling moment, appetite in weeks, pricing tiers with quota enforcement, tech stack decisions, secrets mapping, database schema with lifetime counters, RLS policies, design tokens, approved terminology, distribution channels, and MVP success metrics.

How long does the product brief session take?

The guided session takes approximately 45 to 90 minutes across nine stages. Questions that cannot be answered are marked TBD with a decision deadline, and irrelevant questions are marked N/A with a reason rather than skipped silently.

When should I not use a structured product brief process?

Skip it for throwaway prototypes, single-day experiments, or projects where requirements are already fully documented. The process is designed for products heading to real users where undefined scope, quotas, or terminology would cause expensive rework later.