Agent skill · product strategy · jeremylongshore
product-brief
Structured product brief and PRD creation assistant. Use when the user
Why this skill is useful
Provides a structured template and advanced patterns for creating actionable product briefs that enhance clarity and alignment between teams.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Product Brief Skill Overview Create a decision-ready brief that ties a verified user problem to scope, measurable outcomes, risks, and open decisions. Run the evidence and review checklist before treating a draft as ready for engineering. Use Glob to locate research, Grep to trace prior decisions, and Read to verify the evidence. Instructions Guide the creation of clear, actionable product briefs that engineering can use to scope and build. Behavior 1. Gather context first — Problem, users, constraints 2. Use a consistent structure — Same format every time 3. Focus on "what" and "why" — Leave "how" to engineering 4. Include success metrics — How will we know it worked? 5. Surface open questions — Don't hide uncertainty Tone Clear and decisive Specific over vague Honest about what's unknown Respectful of engineering's expertise Brief Structure Every product brief should include the decision-relevant sections below. Replace bracketed prompts with verified project context and remove any section that truly does not apply. Advanced Patterns 1. Scope negotiation — The In Scope / Out of Scope section is the most-debated part of any brief. Write Out of Scope as a decision, not a deferral: "We're not building desktop support because mobile accounts for 92% of this use case's sessions. Revisit threshold: if desktop sessions exceed 20%." This turns "why not?" conversations into data conversations 2. Metric selection — Pick metrics you can actually measure within the project timeline. "Increase retention" is meaningless in a brief for a feature shipping in 4 weeks — you won't have retention data for months. Instead, pick a leading indicator: "Increase Day-1 feature activation from X% to Y%." Every metric in the brief should have a known data source and a realistic measurement window 3. Dependency surfacing — The Dependencies section should scare you a little. If it doesn't, you haven't thought hard enough. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/product-brief