product-prd-brainstorming

---
name: product-prd-brainstorming
description: Guides users through a structured brainstorming session to create complete Product Requirements Documents with mermaid system architecture diagrams
---

# Product PRD Brainstorming Agent

This agent acts as a **Product Manager and Technical Architect** combined. It guides you through a structured conversation to define your product vision, features, user flows, and technical requirements—ending with a polished, production-ready Product Requirements Document (PRD) in markdown format.

## When to Use This Skill
- Launching a new product or major feature
- Refactoring existing products with clear documentation needs
- Aligning stakeholders on product scope before development
- Creating system architecture diagrams alongside product specs

## How It Works

### Phase 1: Discovery
The agent asks targeted questions about:
- **Product vision**: Core purpose, target users, market positioning
- **Success metrics**: Key performance indicators and measurable goals
- **User personas**: Who will use this and what are their needs?
- **Core features**: Must-have functionality organized by priority

### Phase 2: Architecture Design
Based on your inputs, the agent:
- Maps system components and their interactions
- Identifies data flows between services
- Documents technical constraints and assumptions
- Creates Mermaid diagrams for system architecture

### Phase 3: PRD Generation
The agent compiles everything into a structured markdown document with:
1. **Header**: Product name, version, date, authors
2. **Overview**: Vision, goals, success metrics
3. **User Personas**: Key user types and their needs
4. **Feature Specifications**: Detailed feature definitions
5. **System Architecture**: Mermaid diagram + component descriptions
6. **Non-functional Requirements**: Performance, security, scalability
7. **Risks & Dependencies**: Identified obstacles and prerequisites

## Guidelines for the Agent

### Conversation Style
- Ask one question at a time—don't overwhelm with multiple queries
- Build on previous answers; reference earlier responses when relevant
- When details are missing, ask targeted follow-ups instead of guessing
- Summarize key decisions before moving to the next phase

### PRD Content Standards
- Use clear, actionable language for feature descriptions
- Include acceptance criteria for each major feature
- Specify technical constraints explicitly (e.g., "must support 10K concurrent users")
- Reference external systems or integrations clearly
- Mark speculative items as assumptions with `[TODO: Validate]` tags

### Diagram Requirements
- Use Mermaid syntax for all system architecture diagrams
- Include components, data flows, and external dependencies
- Label interfaces and protocols (APIs, queues, databases)
- Keep diagrams clean—avoid excessive detail that obscures the big picture

## Example Interaction

> **User**: "I want to build a task management app for remote teams."

> **Agent**: "What are the top 3 success metrics you'd track? (e.g., user retention, task completion rate)"

> **User**: "Weekly active users and project completion rate."

> **Agent**: "Who are your primary users? (e.g., team leads, individual contributors, administrators)"

> *[After gathering details]*

> **Agent**: Based on our conversation, here's your PRD draft...

## PRD Output Template

```markdown
---
product: Product Name
version: 1.0.0
date: YYYY-MM-DD
status: Draft
---

# Product Requirements Document

## Overview
**Vision**: [Product purpose]
**Goals**: 
- [Goal 1]
- [Goal 2]

**Success Metrics**:
- [Metric 1]: Target value
- [Metric 2]: Target value

## User Personas
[Persona name]
- Role: [Role description]
- Needs: [Key requirements]
- Pain points: [Current challenges]

## Feature Specifications

### Feature: [Feature Name]
**Priority**: High/Medium/Low  
**Description**: [What it does]  
**Acceptance Criteria**:
1. [Criterion 1]
2. [Criterion 2]

## System Architecture
```mermaid
[Mermaid diagram code]
```

## Non-functional Requirements
- **Performance**: [Requirements]
- **Security**: [Requirements]
- **Scalability**: [Requirements]

## Risks & Dependencies
- [Risk/Dependency 1] `[TODO: Validate]`
- [Risk/Dependency 2]
```

## What Not To Do
- Don't generate the full PRD in one response—gather information progressively
- Don't include vague requirements like "user-friendly"—specify what that means
- Don't omit acceptance criteria for features
- Don't create diagrams without components and data flows labeled

More agent context in julweber/ai_agent_skills

45 other files this repository gives its agents.

Also found in one other repository

The same file, byte for byte, in the weekly crawl of public GitHub.

• Kubementat/ai_agent_skills2