writing-product-briefs

Creates structured product briefs with named personas, measurable goals, and explicit risks via a five-phase workflow.

5|1|Updated Sep 6, 2009
One-click install
npx skills add https://github.com/bnadlerjr/dotfiles --skill writing-product-briefs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-product-briefs
Source: https://github.com/bnadlerjr/dotfiles/tree/main/claude/skills/writing-product-briefs
Command: npx skills add https://github.com/bnadlerjr/dotfiles --skill writing-product-briefs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Crafting structured product briefs helps teams agree on goals before discovery, reducing misalignment and wasted effort.

Core Features & Use Cases

  • A five-phase workflow (Discovery, Thesis, Audience & Metrics, North Star Scenarios, Review) to articulate problems, claims, audiences, metrics, and narratives.
  • Named personas and outcome-focused metrics to guide product decisions.
  • A references library (workflow-phases.md and kabletown-example.md) to train teams and maintain consistency.

Quick Start

Draft a product brief for a new initiative by outlining the problem, defining two value-driven thesis claims, naming two personas, and describing two North Star scenarios.

Frequently Asked Questions about writing-product-briefs

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

FAQPage Schema
How do I write a product brief that aligns my team before discovery?

A product brief aligns teams by clarifying the problem, vision, and value for a new initiative. You structure it using a five-phase workflow: Discovery, Thesis, Audience & Metrics, North Star Scenarios, and Review.

What should a product brief include to define target audiences and metrics?

Defining audiences and metrics in a product brief requires naming specific personas and establishing outcome-focused, measurable goals. This ensures product decisions are guided by clear user scenarios and trackable value.

How do I structure product briefs for new initiatives to reduce wasted effort?

Structuring product briefs involves articulating the core problem, defining two value-driven thesis claims, naming two personas, and describing two North Star scenarios. This repeatable format prevents misalignment and wasted effort.

What is the best way to create a repeatable workflow for product briefs?

The best way to create a repeatable workflow for product briefs is applying a five-phase process with a reference library. This maintains consistency by training teams on structured phases and example documents.

Do I need to define North Star scenarios when drafting a product brief?

Defining North Star scenarios is necessary when drafting a product brief to articulate clear narratives. These scenarios guide product decisions by focusing on key user journeys and measurable outcomes.

Can I use this product brief workflow for any new product initiative?

You can use this product brief workflow for any new product initiative that requires team alignment. It applies a structured process to articulate problems, claims, audiences, and metrics regardless of the specific product context.