product-brief

Create structured product briefs with UX copy and implementation notes.

Updated Jul 3, 2026

Search Tags:#requirements #feature planning #ux writing #product strategy #product brief #task authoring

Ready to run

npx skills add https://github.com/Reidond/Banshee --skill product-brief-reidond

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-brief
Source: https://github.com/Reidond/Banshee/tree/main/.claude/skills/product-brief
Command: npx skills add https://github.com/Reidond/Banshee --skill product-brief-reidond

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams turn unstructured feature ideas into clear, codebase-grounded product briefs by challenging assumptions before implementation and defining user-facing requirements.

Core Features & Use Cases

Product Brief Authoring: Creates structured feature task documents with problems, behaviors, UX content, scope boundaries, and implementation notes.
Assumption Challenging: Surfaces 2-3 grounded product questions before writing to prevent unclear requirements and implementation rework.
UX Content Generation: Produces production-ready copy for modals, messages, buttons, and surveys aligned with feature behavior.
Use Case: A product team can use this Skill when proposing a new feature to research existing flows, resolve product decisions, and prepare a team-ready task file.

Quick Start

Ask the product-brief skill to turn this feature idea into a codebase-grounded product brief with UX copy and implementation notes.

Frequently Asked Questions about product-brief

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

FAQPage Schema

How do I turn a feature idea into a structured product brief?▼

Turning a feature idea into a structured product brief requires challenging assumptions, defining user behaviors, and producing implementation-ready task documents. This process grounds feature requests in codebase research before generating team-readable requirements.

What is the best way to define implementation-ready requirements for UX content?▼

Defining implementation-ready requirements for UX content involves generating production-ready copy for modals, messages, and buttons. This ensures the UX writing aligns directly with the defined feature behaviors and scope boundaries.

How does assumption challenging prevent rework in feature planning?▼

Assumption challenging in feature planning prevents rework by surfacing grounded product questions before writing tasks. Resolving these questions early clarifies product decisions and avoids unclear requirements during implementation.

Can I use product briefs for engineering task preparation and UX writing together?▼

Yes, product briefs support both engineering task preparation and UX writing together. They structure feature task documents with problems, behaviors, and implementation notes alongside production-ready UX copy for modals and surveys.

Do I need codebase research to create a product brief?▼

Yes, codebase research is required to create a grounded product brief. Researching existing code and flows validates product decisions and ensures the generated task documents are implementation-ready for the engineering team.