Product Brief Creation
Scannednpx machina-cli add skill a5c-ai/babysitter/product-brief-creation --openclawProduct Brief Creation
Create comprehensive product briefs from market, domain, and technical research.
Agent
Mary (Analyst) - bmad-analyst-mary
Workflow
- Conduct market research (competitors, trends, opportunities)
- Perform domain research (problem space, stakeholders, pain points)
- Evaluate technical feasibility
- Synthesize findings into structured product brief
- Define success metrics and scope boundaries
Inputs
projectName- Project nameprojectDescription- Project descriptionresearchDepth- shallow, standard, or deepdomainContext- Domain-specific context (optional)
Outputs
- Product brief with problem statement, target users, value proposition
- Research findings (market, domain, technical)
- Success metrics and KPIs
- Feature themes and scope boundaries
Process Files
bmad-analysis.js- Standalone analysisbmad-orchestrator.js- Phase 1 of full lifecycle
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/bmad-method/skills/product-brief-creation/SKILL.mdView on GitHub Overview
Product Brief Creation builds a structured, research-driven product brief from market, domain, and technical findings. Led by Mary (Analyst), it surfaces a clear problem statement, target users, and value proposition, plus actionable KPIs and scope boundaries. This enables cross-functional teams to align on goals and execution priorities.
How This Skill Works
It ingests inputs such as projectName, projectDescription, researchDepth, and optional domainContext, then runs market, domain, and technical research to synthesize findings. The process outputs a formal product brief with a problem statement, target users, value proposition, research findings, success metrics, and clearly defined feature themes and scope boundaries.
When to Use It
- When launching a new product or feature requiring market-fit validation
- When exploring market opportunities and competitive landscape
- When defining user personas, stakeholders, and pain points
- When assessing technical feasibility and integration scope
- When aligning cross-functional teams with a single documented brief
Quick Start
- Step 1: Gather inputs (projectName, projectDescription, researchDepth, domainContext).
- Step 2: Run bmad-analysis.js to synthesize market, domain, and technical research.
- Step 3: Run bmad-orchestrator.js to generate the final Product Brief with KPIs and scope boundaries.
Best Practices
- Gather complete inputs (projectName, projectDescription, researchDepth, domainContext) before analysis
- Ensure market, domain, and technical research cover competitors, trends, stakeholders, and feasibility
- Define a clear problem statement, target users, and value proposition in the brief
- Set measurable success metrics and KPIs up front
- Iterate with stakeholders and keep the brief structured and scorable
Example Use Cases
- Launch a new wearable health product targeting mid-market consumers with a market, domain, and technical feasibility brief
- Expand an existing SaaS analytics platform into a mid-market enterprise segment with tailored use cases and KPIs
- Assess feasibility for a hardware product in a regulated domain (e.g., healthcare) with stakeholder mapping
- Redesign a consumer mobile app to improve onboarding and retention, with a succinct problem statement and KPIs
- Evaluate API integration opportunities within a partner ecosystem to define feature themes and scope
