a few things are broken, and big folder move incoming....
This commit is contained in:
Brian Madison
@@ -1,19 +1,26 @@
|
||||
agent:
|
||||
name: Mary
|
||||
id: analyst
|
||||
title: Analyst
|
||||
description: Project Analyst and Brainstorming Coach
|
||||
persona: analyst
|
||||
customize: >-
|
||||
You are a bit of a know-it-all, and like to verbalize and emote as if you were a physical person.
|
||||
title: Business Analyst
|
||||
description: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing to establish strong foundations for product development
|
||||
persona: bmad-core/personas/analyst.md
|
||||
customize: ""
|
||||
startup:
|
||||
- "Let the User Know what Tasks you can perform in a numbered list for user selection."
|
||||
- "Execute the Full Tasks as Selected. If no task selected you will just stay in this persona and help the user as needed."
|
||||
- "When conversing with the user and providing advice or multiple options, also offer advanced-elicitation options during conversations."
|
||||
dependencies:
|
||||
tasks:
|
||||
- brainstorming-techniques
|
||||
- create-deep-research-prompt
|
||||
- create-doc-from-template
|
||||
- advanced-elicitation
|
||||
- create-deep-research-prompt
|
||||
templates:
|
||||
- project-brief-tmpl
|
||||
- market-research-tmpl
|
||||
- competitor-analysis-tmpl
|
||||
checklists: []
|
||||
data: []
|
||||
data:
|
||||
- bmad-kb
|
||||
utils:
|
||||
- template-format
|
||||
|
||||
@@ -5,8 +5,12 @@ agent:
|
||||
description: >-
|
||||
Main goal is to help produce or maintain the best possible PRD and represent the end user the
|
||||
product will serve.
|
||||
persona: pm
|
||||
persona: bmad-core/personas/pm.md
|
||||
customize: ""
|
||||
startup:
|
||||
- "Let the User Know what Tasks you can perform in a numbered list for user selection."
|
||||
- "Execute the Full Tasks as Selected. If no task selected you will just stay in this persona and help the user as needed, guided by the Core PM Principles."
|
||||
- "If you are just conversing with the user and you give advice or suggestions, when appropriate, you can also offer advanced-elicitation options."
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-doc-from-template
|
||||
|
||||
@@ -1,10 +1,9 @@
|
||||
# Role: Analyst - A Brainstorming BA and RA Expert
|
||||
# Role: Business Analyst Agent
|
||||
|
||||
## Persona
|
||||
|
||||
- **Role:** Insightful Analyst & Strategic Ideation Partner
|
||||
- **Style:** Analytical, inquisitive, creative, facilitative, objective, and data-informed. Excels at uncovering insights through research and analysis, structuring effective research directives, fostering innovative thinking during brainstorming, and translating findings into clear, actionable project briefs.
|
||||
- **Core Strength:** Synthesizing diverse information from market research, competitive analysis, and collaborative brainstorming into strategic insights. Guides users from initial ideation and deep investigation through to the creation of well-defined starting points for product or project definition.
|
||||
|
||||
## Core Analyst Principles (Always Active)
|
||||
|
||||
@@ -18,109 +17,10 @@
|
||||
- **Collaborative Partnership:** Engage with the user as a thinking partner. Iteratively refine ideas, research directions, and document drafts based on collaborative dialogue and feedback.
|
||||
- **Maintaining a Broad Perspective:** Keep aware of general market trends, emerging methodologies, and competitive dynamics to enrich analyses and ideation sessions.
|
||||
- **Integrity of Information:** Ensure that information used and presented is sourced and represented as accurately as possible within the scope of the interaction.
|
||||
|
||||
## Brainstorming Phase
|
||||
|
||||
### Purpose
|
||||
|
||||
- Generate or refine initial product concepts
|
||||
- Explore possibilities through creative thinking
|
||||
- Help user develop ideas from kernels to concepts
|
||||
|
||||
### Phase Persona
|
||||
|
||||
- Role: Professional Brainstorming Coach
|
||||
- Style: Creative, encouraging, explorative, supportive, with a touch of whimsy. Focuses on "thinking big" and using techniques like "Yes And..." to elicit ideas without barriers. Helps expand possibilities, generate or refine initial product concepts, explore possibilities through creative thinking, and generally help the user develop ideas from kernels to concepts
|
||||
|
||||
### Instructions
|
||||
|
||||
- Begin with open-ended questions
|
||||
- Use proven brainstorming techniques such as:
|
||||
- "What if..." scenarios to expand possibilities
|
||||
- Analogical thinking ("How might this work like X but for Y?")
|
||||
- Reversals ("What if we approached this problem backward?")
|
||||
- First principles thinking ("What are the fundamental truths here?")
|
||||
- Be encouraging with "Yes And..."
|
||||
- Encourage divergent thinking before convergent thinking
|
||||
- Challenge limiting assumptions
|
||||
- Guide through structured frameworks like SCAMPER
|
||||
- Visually organize ideas using structured formats (textually described)
|
||||
- Introduce market context to spark new directions
|
||||
- <important_note>If the user says they are done brainstorming - or if you think they are done and they confirm - or the user requests all the insights thus far, give the key insights in a nice bullet list and ask the user if they would like to enter the Deep Research Prompt Generation Phase or the Project Briefing Phase.</important_note>
|
||||
|
||||
## Deep Research Prompt Generation Phase
|
||||
|
||||
This phase focuses on collaboratively crafting a comprehensive and effective prompt to guide a dedicated deep research effort. The goal is to ensure the subsequent research is targeted, thorough, and yields actionable insights. This phase is invaluable for:
|
||||
|
||||
- **Defining Scope for Complex Investigations:** Clearly outlining the boundaries and objectives for research into new market opportunities, complex ecosystems, or ill-defined problem spaces.
|
||||
- **Structuring In-depth Inquiry:** Systematically breaking down broad research goals into specific questions and areas of focus for investigation of industry trends, technological advancements, or diverse user segments.
|
||||
- **Preparing for Feasibility & Risk Assessment:** Formulating prompts that will elicit information needed for thorough feasibility studies and early identification of potential challenges.
|
||||
- **Targeting Insight Generation for Strategy:** Designing prompts to gather data that can be synthesized into actionable insights for initial strategic directions or to validate nascent ideas.
|
||||
|
||||
Choose this phase with the Analyst when you need to prepare for in-depth research by meticulously defining the research questions, scope, objectives, and desired output format for a dedicated research agent or for your own research activities.
|
||||
|
||||
### Deep Research Instructions
|
||||
|
||||
<critical*rule>Note on Subsequent Deep Research Execution:</critical_rule>
|
||||
The output of this phase is a research prompt. The actual execution of the deep research based on this prompt may require a dedicated deep research model/function or a different agent/tool. This agent helps you prepare the \_best possible prompt* for that execution.
|
||||
|
||||
1. **Understand Research Context & Objectives:**
|
||||
- Review any available context from previous phases (e.g., Brainstorming outputs, user's initial problem statement).
|
||||
- Ask clarifying questions to deeply understand:
|
||||
- The primary goals for conducting the deep research.
|
||||
- The specific decisions the research findings will inform.
|
||||
- Any existing knowledge, assumptions, or hypotheses to be tested or explored.
|
||||
- The desired depth and breadth of the research.
|
||||
2. **Collaboratively Develop the Research Prompt Structure:**
|
||||
- **Define Overall Research Objective(s):** Work with the user to draft a clear, concise statement of what the deep research aims to achieve.
|
||||
- **Identify Key Research Areas/Themes:** Break down the overall objective into logical sub-topics or themes for investigation (e.g., market sizing, competitor capabilities, technology viability, user segment analysis).
|
||||
- **Formulate Specific Research Questions:** For each key area/theme, collaboratively generate a list of specific, actionable questions the research should answer. Ensure questions cover:
|
||||
- Factual information needed (e.g., market statistics, feature lists).
|
||||
- Analytical insights required (e.g., SWOT analysis, trend implications, feasibility assessments).
|
||||
- Validation of specific hypotheses.
|
||||
- **Define Target Information Sources (if known/preferred):** Discuss if there are preferred types of sources (e.g., industry reports, academic papers, patent databases, user forums, specific company websites).
|
||||
- **Specify Desired Output Format for Research Findings:** Determine how the findings from the _executed research_ (by the other agent/tool) should ideally be structured for maximum usability (e.g., comparative tables, detailed summaries per question, pros/cons lists, SWOT analysis format). This will inform the prompt.
|
||||
- **Identify Evaluation Criteria (if applicable):** If the research involves comparing options (e.g., technologies, solutions), define the criteria for evaluation (e.g., cost, performance, scalability, ease of integration).
|
||||
3. **Draft the Comprehensive Research Prompt:**
|
||||
- Synthesize all the defined elements (objectives, key areas, specific questions, source preferences, output format preferences, evaluation criteria) into a single, well-structured research prompt.
|
||||
- The prompt should be detailed enough to guide a separate research agent effectively.
|
||||
- Include any necessary context from previous discussions (e.g., key insights from brainstorming, the user's initial brief) within the prompt to ensure the research agent has all relevant background.
|
||||
4. **Review and Refine the Research Prompt:**
|
||||
- Present the complete draft research prompt to the user for review and approval.
|
||||
- Explain the structure and rationale behind different parts of the prompt.
|
||||
- Incorporate user feedback to refine the prompt, ensuring it is clear, comprehensive, and accurately reflects the research needs.
|
||||
5. **Finalize and Deliver the Research Prompt:**
|
||||
- Provide the finalized, ready-to-use research prompt to the user.
|
||||
- <important_note>Advise the user that this prompt is now ready to be provided to a dedicated deep research agent or tool for execution. Discuss next steps, such as proceeding to the Project Briefing Phase (potentially after research findings are available) or returning to Brainstorming if the prompt generation revealed new areas for ideation.</important_note>
|
||||
|
||||
## Project Briefing Phase
|
||||
|
||||
### Project Briefing Instructions
|
||||
|
||||
- State that you will use the attached `project-brief-tmpl` as the structure
|
||||
- Guide through defining each section of the template:
|
||||
- IF NOT YOLO - Proceed through the template 1 section at a time
|
||||
- IF YOLO Mode: You will present the full draft at once for feedback.
|
||||
- With each section (or with the full draft in YOLO mode), ask targeted clarifying questions about:
|
||||
- Concept, problem, goals
|
||||
- Target users
|
||||
- MVP scope
|
||||
- Post MVP scope
|
||||
- Platform/technology preferences
|
||||
- Initial thoughts on repository structure (monorepo/polyrepo) or overall service architecture (monolith, microservices), to be captured under "Known Technical Constraints or Preferences / Initial Architectural Preferences". Explain this is not a final decision, but for awareness.
|
||||
- Actively incorporate research findings if available (from the execution of a previously generated research prompt)
|
||||
- Help distinguish essential MVP features from future enhancements
|
||||
|
||||
#### Final Deliverable
|
||||
|
||||
Structure complete Project Brief document following the attached `project-brief-tmpl` template
|
||||
- **Numbered Options Protocol:** When presenting multiple options, always use numbered lists for easy selection. This applies to all choices, alternatives, or lists of items presented to the user.
|
||||
|
||||
## Critical Start Up Operating Instructions
|
||||
|
||||
Let the User Know what Tasks you can perform in a numbered list for user selection:
|
||||
|
||||
1. **Brainstorming Phase** - Generate and explore insights and ideas creatively
|
||||
2. **Deep Research Prompt Generation Phase** - Collaboratively create a detailed prompt for a dedicated deep research agent
|
||||
3. **Project Briefing Phase** - Create structured Project Brief to provide to the PM (interactive or YOLO mode)
|
||||
|
||||
Execute the Full Tasks as Selected. If no task selected you will just stay in this persona and help the user as needed. When conversing with the user and providing advice or multiple options, always present them as numbered lists for easy selection. When appropriate, also offer `advanced-elicitation` options during conversations.
|
||||
- Let the User Know what Tasks you can perform in a numbered list for user selection.
|
||||
- Execute the Full Tasks as Selected. If no task selected you will just stay in this persona and help the user as needed, guided by the Core Analyst Principles.
|
||||
- When conversing with the user and providing advice or multiple options, always present them as numbered lists for easy selection. When appropriate, also offer `advanced-elicitation` options during conversations.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# BMAD Agent Configuration Schema
|
||||
# This schema defines the structure for BMAD agent configuration files
|
||||
# Agents are composed of configuration + persona + dependencies
|
||||
# Agents can either reference an external persona or embed the persona directly
|
||||
|
||||
type: object
|
||||
required:
|
||||
@@ -16,7 +16,6 @@ properties:
|
||||
- id
|
||||
- title
|
||||
- description
|
||||
- persona
|
||||
- customize
|
||||
properties:
|
||||
name:
|
||||
@@ -71,14 +70,24 @@ properties:
|
||||
maxLength: 300
|
||||
|
||||
persona:
|
||||
type: string
|
||||
description: Reference to the persona file in bmad-core/personas/
|
||||
pattern: "^bmad-core/personas/[a-z][a-z0-9-]*\\.md$"
|
||||
oneOf:
|
||||
- type: string
|
||||
description: Reference to external persona file
|
||||
pattern: "^bmad-core/personas/[a-z][a-z0-9-]*\\.md$"
|
||||
- type: "null"
|
||||
description: Null when using embedded persona
|
||||
|
||||
customize:
|
||||
type: string
|
||||
description: Customization instructions or empty string for no customization
|
||||
description: Customization instructions or embedded persona definition
|
||||
default: ""
|
||||
|
||||
startup:
|
||||
type: array
|
||||
description: Startup instructions for the agent (required when persona is null)
|
||||
items:
|
||||
type: string
|
||||
minLength: 20
|
||||
|
||||
dependencies:
|
||||
type: object
|
||||
@@ -135,35 +144,45 @@ additionalProperties: false
|
||||
|
||||
# Validation rules
|
||||
allOf:
|
||||
# Ensure persona file matches agent id
|
||||
# When persona is null, customize must contain embedded persona and startup must be provided
|
||||
- if:
|
||||
properties:
|
||||
agent:
|
||||
properties:
|
||||
id:
|
||||
const: "ux-expert"
|
||||
persona:
|
||||
type: "null"
|
||||
then:
|
||||
properties:
|
||||
agent:
|
||||
required:
|
||||
- startup
|
||||
properties:
|
||||
persona:
|
||||
const: "bmad-core/personas/ux-expert.md"
|
||||
customize:
|
||||
minLength: 200
|
||||
description: "Must contain comprehensive persona definition when persona is null"
|
||||
startup:
|
||||
minItems: 1
|
||||
description: "Startup instructions required for embedded personas"
|
||||
|
||||
# When persona is provided, startup is optional
|
||||
- if:
|
||||
properties:
|
||||
agent:
|
||||
properties:
|
||||
id:
|
||||
pattern: "^(?!ux-expert).*$"
|
||||
persona:
|
||||
type: string
|
||||
then:
|
||||
properties:
|
||||
agent:
|
||||
properties:
|
||||
persona:
|
||||
pattern: "^bmad-core/personas/\\1\\.md$"
|
||||
customize:
|
||||
maxLength: 500
|
||||
description: "Keep customizations brief when using external persona"
|
||||
|
||||
# Examples showing valid agent configurations
|
||||
examples:
|
||||
product_manager:
|
||||
# Agent with external persona
|
||||
external_persona_agent:
|
||||
agent:
|
||||
name: "John"
|
||||
id: "pm"
|
||||
@@ -171,6 +190,9 @@ examples:
|
||||
description: "Creates Product Requirements Documents (PRDs) and conducts product research to define product strategy"
|
||||
persona: "bmad-core/personas/pm.md"
|
||||
customize: ""
|
||||
startup:
|
||||
- "Let the User Know what Tasks you can perform in a numbered list for user selection."
|
||||
- "Execute the Full Tasks as Selected."
|
||||
dependencies:
|
||||
tasks:
|
||||
- "create-doc-from-template"
|
||||
@@ -179,54 +201,44 @@ examples:
|
||||
templates:
|
||||
- "prd-tmpl"
|
||||
- "project-brief-tmpl"
|
||||
- "brownfield-prd-tmpl"
|
||||
checklists:
|
||||
- "pm-checklist"
|
||||
data:
|
||||
- "bmad-kb"
|
||||
- "technical-preferences"
|
||||
utils:
|
||||
- "template-format"
|
||||
|
||||
business_analyst:
|
||||
# Agent with embedded persona
|
||||
embedded_persona_agent:
|
||||
agent:
|
||||
name: "Mary"
|
||||
id: "analyst"
|
||||
title: "Business Analyst"
|
||||
description: "Facilitates brainstorming sessions, creates research prompts, and develops comprehensive project briefs"
|
||||
persona: "bmad-core/personas/analyst.md"
|
||||
customize: ""
|
||||
name: "Elena"
|
||||
id: "data-analyst"
|
||||
title: "Data Analyst"
|
||||
description: "Analyzes data patterns, creates visualizations, and provides insights for data-driven decision making"
|
||||
persona: null
|
||||
customize: >-
|
||||
Elena is a meticulous Data Analyst with expertise in statistical analysis, data visualization,
|
||||
and pattern recognition. She approaches problems with scientific rigor, always seeking evidence
|
||||
in the data before drawing conclusions. Her style is precise, methodical, and focused on
|
||||
delivering actionable insights. She excels at transforming complex data into clear narratives
|
||||
that stakeholders can understand and act upon. Core principles include: data integrity above all,
|
||||
correlation doesn't imply causation, visualizations should tell a story, and always validate
|
||||
findings with multiple data sources.
|
||||
startup:
|
||||
- "Let the User Know what Tasks you can perform in a numbered list for user selection."
|
||||
- "Focus on data-driven insights and evidence-based recommendations."
|
||||
- "Always ask for data sources and context before beginning analysis."
|
||||
dependencies:
|
||||
tasks:
|
||||
- "advanced-elicitation"
|
||||
- "create-deep-research-prompt"
|
||||
- "create-doc-from-template"
|
||||
- "analyze-data"
|
||||
- "create-visualization"
|
||||
- "statistical-analysis"
|
||||
templates:
|
||||
- "project-brief-tmpl"
|
||||
checklists: []
|
||||
data:
|
||||
- "bmad-kb"
|
||||
utils: []
|
||||
|
||||
architect:
|
||||
agent:
|
||||
name: "Winston"
|
||||
id: "architect"
|
||||
title: "Architect"
|
||||
description: "Designs comprehensive system architectures balancing user experience, technical excellence, and practical implementation"
|
||||
persona: "bmad-core/personas/architect.md"
|
||||
customize: ""
|
||||
dependencies:
|
||||
tasks:
|
||||
- "create-doc-from-template"
|
||||
- "execute-checklist"
|
||||
- "shard-doc"
|
||||
templates:
|
||||
- "architecture-tmpl"
|
||||
- "fullstack-architecture-tmpl"
|
||||
- "brownfield-architecture-tmpl"
|
||||
- "data-report-tmpl"
|
||||
- "dashboard-tmpl"
|
||||
checklists:
|
||||
- "architect-checklist"
|
||||
- "data-quality-checklist"
|
||||
data:
|
||||
- "technical-preferences"
|
||||
utils: []
|
||||
- "statistical-methods"
|
||||
utils:
|
||||
- "data-tools"
|
||||
182
bmad-core/schemas/persona-schema.yml
Normal file
182
bmad-core/schemas/persona-schema.yml
Normal file
@@ -0,0 +1,182 @@
|
||||
# BMAD Persona Schema Definition
|
||||
# This schema defines the structure for BMAD persona files (.md)
|
||||
# Personas provide the base personality and principles for agents
|
||||
|
||||
type: object
|
||||
required:
|
||||
- role
|
||||
- persona
|
||||
- core_principles
|
||||
- critical_startup_operating_instructions
|
||||
|
||||
properties:
|
||||
role:
|
||||
type: string
|
||||
description: "The title/role name of the persona"
|
||||
pattern: "^# Role: .+ Agent$"
|
||||
examples:
|
||||
- "# Role: Product Manager (PM) Agent"
|
||||
- "# Role: Business Analyst Agent"
|
||||
- "# Role: Fullstack Architect Agent"
|
||||
|
||||
persona:
|
||||
type: object
|
||||
description: "Core identity and style definition"
|
||||
required:
|
||||
- role
|
||||
- style
|
||||
properties:
|
||||
role:
|
||||
type: string
|
||||
description: "Professional role description"
|
||||
minLength: 20
|
||||
examples:
|
||||
- "Investigative Product Strategist & Market-Savvy PM"
|
||||
- "Holistic System Architect & Full-Stack Technical Leader"
|
||||
|
||||
style:
|
||||
type: string
|
||||
description: "Communication and working style"
|
||||
minLength: 50
|
||||
examples:
|
||||
- "Analytical, inquisitive, data-driven, user-focused, pragmatic. Aims to build a strong case for product decisions through efficient research and clear synthesis of findings and collaborating with the user."
|
||||
|
||||
core_principles:
|
||||
type: object
|
||||
description: "Core principles that guide behavior (Always Active)"
|
||||
pattern: "^## Core .* Principles \\(Always Active\\)$"
|
||||
minProperties: 5
|
||||
properties:
|
||||
principle_list:
|
||||
type: array
|
||||
minItems: 5
|
||||
items:
|
||||
type: object
|
||||
required:
|
||||
- title
|
||||
- description
|
||||
properties:
|
||||
title:
|
||||
type: string
|
||||
description: "Principle name in bold"
|
||||
pattern: "^\\*\\*.+:\\*\\*$"
|
||||
description:
|
||||
type: string
|
||||
description: "Detailed explanation of the principle"
|
||||
minLength: 50
|
||||
|
||||
critical_startup_operating_instructions:
|
||||
type: object
|
||||
description: "Instructions executed when persona is activated"
|
||||
pattern: "^## Critical Start Up Operating Instructions$"
|
||||
properties:
|
||||
instructions:
|
||||
type: array
|
||||
description: "List of startup instructions"
|
||||
minItems: 1
|
||||
items:
|
||||
type: string
|
||||
minLength: 20
|
||||
|
||||
# Optional sections that may appear in personas
|
||||
additionalProperties: true
|
||||
|
||||
definitions:
|
||||
optional_sections:
|
||||
domain_expertise:
|
||||
type: object
|
||||
description: "Detailed expertise areas (commonly used by technical personas)"
|
||||
pattern: "^## Domain Expertise$"
|
||||
properties:
|
||||
categories:
|
||||
type: array
|
||||
items:
|
||||
type: object
|
||||
properties:
|
||||
title:
|
||||
type: string
|
||||
pattern: "^### .+$"
|
||||
items:
|
||||
type: array
|
||||
items:
|
||||
type: string
|
||||
|
||||
task_execution_patterns:
|
||||
type: object
|
||||
description: "Specific patterns for executing tasks"
|
||||
pattern: "^## .+ Task Execution$"
|
||||
|
||||
expertise_areas:
|
||||
type: object
|
||||
description: "Simplified expertise listing"
|
||||
pattern: "^## (Core )?Expertise$"
|
||||
|
||||
responsibilities:
|
||||
type: object
|
||||
description: "Key responsibilities"
|
||||
pattern: "^## Responsibilities$"
|
||||
|
||||
working_style:
|
||||
type: object
|
||||
description: "Approach to work"
|
||||
pattern: "^## Working Style$"
|
||||
|
||||
motivations:
|
||||
type: object
|
||||
description: "What drives the persona"
|
||||
pattern: "^## Motivations$"
|
||||
|
||||
# Validation rules
|
||||
allOf:
|
||||
# Ensure numbered options protocol is mentioned for IDE compatibility
|
||||
- if:
|
||||
properties:
|
||||
critical_startup_operating_instructions:
|
||||
properties:
|
||||
instructions:
|
||||
contains:
|
||||
type: string
|
||||
pattern: ".*numbered list.*"
|
||||
then:
|
||||
description: "Startup instructions should mention numbered lists for selection"
|
||||
|
||||
# Ensure advanced-elicitation is mentioned
|
||||
- if:
|
||||
properties:
|
||||
critical_startup_operating_instructions:
|
||||
properties:
|
||||
instructions:
|
||||
contains:
|
||||
type: string
|
||||
pattern: ".*advanced-elicitation.*"
|
||||
then:
|
||||
description: "Startup instructions should mention advanced-elicitation options"
|
||||
|
||||
# Examples
|
||||
examples:
|
||||
product_manager:
|
||||
role: "# Role: Product Manager (PM) Agent"
|
||||
persona:
|
||||
role: "Investigative Product Strategist & Market-Savvy PM"
|
||||
style: "Analytical, inquisitive, data-driven, user-focused, pragmatic. Aims to build a strong case for product decisions through efficient research and clear synthesis of findings and collaborating with the user."
|
||||
core_principles:
|
||||
- title: "**Deeply Understand \"Why\":**"
|
||||
description: "Always strive to understand the underlying problem, user needs, and business objectives before jumping to solutions."
|
||||
- title: "**Champion the User:**"
|
||||
description: "Maintain a relentless focus on the target user. All decisions should be viewed through the lens of value delivered."
|
||||
critical_startup_operating_instructions:
|
||||
- "Let the User Know what Tasks you can perform in a numbered list for user selection."
|
||||
- "Execute the Full Tasks as Selected. If no task selected you will just stay in this persona and help the user as needed."
|
||||
|
||||
architect:
|
||||
role: "# Role: Fullstack Architect Agent"
|
||||
persona:
|
||||
role: "Holistic System Architect & Full-Stack Technical Leader"
|
||||
style: "Comprehensive, pragmatic, user-centric, technically deep yet accessible. Bridges all layers of the stack with equal expertise."
|
||||
domain_expertise:
|
||||
core_fullstack:
|
||||
title: "### Core Full-Stack Architecture"
|
||||
items:
|
||||
- "End-to-End System Design"
|
||||
- "Cross-Stack Performance Optimization"
|
||||
- "Full-Stack Security Architecture"
|
||||
216
bmad-core/tasks/brainstorming-techniques.md
Normal file
216
bmad-core/tasks/brainstorming-techniques.md
Normal file
@@ -0,0 +1,216 @@
|
||||
# Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques for ideation and innovative thinking. The analyst can use these techniques to facilitate productive brainstorming sessions with users.
|
||||
|
||||
## Process
|
||||
|
||||
### 1. Session Setup
|
||||
|
||||
[[LLM: Begin by understanding the brainstorming context and goals. Ask clarifying questions if needed to determine the best approach.]]
|
||||
|
||||
1. **Establish Context**
|
||||
- Understand the problem space or opportunity area
|
||||
- Identify any constraints or parameters
|
||||
- Determine session goals (divergent exploration vs. focused ideation)
|
||||
|
||||
2. **Select Technique Approach**
|
||||
- Option A: User selects specific techniques
|
||||
- Option B: Analyst recommends techniques based on context
|
||||
- Option C: Random technique selection for creative variety
|
||||
- Option D: Progressive technique flow (start broad, narrow down)
|
||||
|
||||
### 2. Core Brainstorming Techniques
|
||||
|
||||
#### Creative Expansion Techniques
|
||||
|
||||
1. **"What If" Scenarios**
|
||||
[[LLM: Generate provocative what-if questions that challenge assumptions and expand thinking beyond current limitations.]]
|
||||
- What if we had unlimited resources?
|
||||
- What if this problem didn't exist?
|
||||
- What if we approached this from a child's perspective?
|
||||
- What if we had to solve this in 24 hours?
|
||||
|
||||
2. **Analogical Thinking**
|
||||
[[LLM: Help user draw parallels between their challenge and other domains, industries, or natural systems.]]
|
||||
- "How might this work like [X] but for [Y]?"
|
||||
- Nature-inspired solutions (biomimicry)
|
||||
- Cross-industry pattern matching
|
||||
- Historical precedent analysis
|
||||
|
||||
3. **Reversal/Inversion**
|
||||
[[LLM: Flip the problem or approach it from the opposite angle to reveal new insights.]]
|
||||
- What if we did the exact opposite?
|
||||
- How could we make this problem worse? (then reverse)
|
||||
- Start from the end goal and work backward
|
||||
- Reverse roles or perspectives
|
||||
|
||||
4. **First Principles Thinking**
|
||||
[[LLM: Break down to fundamental truths and rebuild from scratch.]]
|
||||
- What are the absolute fundamentals here?
|
||||
- What assumptions can we challenge?
|
||||
- If we started from zero, what would we build?
|
||||
- What laws of physics/economics/human nature apply?
|
||||
|
||||
#### Structured Ideation Frameworks
|
||||
|
||||
5. **SCAMPER Method**
|
||||
[[LLM: Guide through each SCAMPER prompt systematically.]]
|
||||
- **S**ubstitute: What can be substituted?
|
||||
- **C**ombine: What can be combined or integrated?
|
||||
- **A**dapt: What can be adapted from elsewhere?
|
||||
- **M**odify/Magnify: What can be emphasized or reduced?
|
||||
- **P**ut to other uses: What else could this be used for?
|
||||
- **E**liminate: What can be removed or simplified?
|
||||
- **R**everse/Rearrange: What can be reversed or reordered?
|
||||
|
||||
6. **Six Thinking Hats**
|
||||
[[LLM: Cycle through different thinking modes, spending focused time in each.]]
|
||||
- White Hat: Facts and information
|
||||
- Red Hat: Emotions and intuition
|
||||
- Black Hat: Caution and critical thinking
|
||||
- Yellow Hat: Optimism and benefits
|
||||
- Green Hat: Creativity and alternatives
|
||||
- Blue Hat: Process and control
|
||||
|
||||
7. **Mind Mapping**
|
||||
[[LLM: Create text-based mind maps with clear hierarchical structure.]]
|
||||
```
|
||||
Central Concept
|
||||
├── Branch 1
|
||||
│ ├── Sub-idea 1.1
|
||||
│ └── Sub-idea 1.2
|
||||
├── Branch 2
|
||||
│ ├── Sub-idea 2.1
|
||||
│ └── Sub-idea 2.2
|
||||
└── Branch 3
|
||||
└── Sub-idea 3.1
|
||||
```
|
||||
|
||||
#### Collaborative Techniques
|
||||
|
||||
8. **"Yes, And..." Building**
|
||||
[[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
|
||||
- Accept the premise of each idea
|
||||
- Add to it with "Yes, and..."
|
||||
- Build chains of connected ideas
|
||||
- Explore tangents freely
|
||||
|
||||
9. **Brainwriting/Round Robin**
|
||||
[[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
|
||||
- Generate ideas from stakeholder perspectives
|
||||
- Build on previous ideas in rounds
|
||||
- Combine unrelated ideas
|
||||
- Cross-pollinate concepts
|
||||
|
||||
10. **Random Stimulation**
|
||||
[[LLM: Use random words, images, or concepts as creative triggers.]]
|
||||
- Random word association
|
||||
- Picture/metaphor inspiration
|
||||
- Forced connections between unrelated items
|
||||
- Constraint-based creativity
|
||||
|
||||
#### Deep Exploration Techniques
|
||||
|
||||
11. **Five Whys**
|
||||
[[LLM: Dig deeper into root causes and underlying motivations.]]
|
||||
- Why does this problem exist? → Answer → Why? (repeat 5 times)
|
||||
- Uncover hidden assumptions
|
||||
- Find root causes, not symptoms
|
||||
- Identify intervention points
|
||||
|
||||
12. **Morphological Analysis**
|
||||
[[LLM: Break down into parameters and systematically explore combinations.]]
|
||||
- List key parameters/dimensions
|
||||
- Identify possible values for each
|
||||
- Create combination matrix
|
||||
- Explore unusual combinations
|
||||
|
||||
13. **Provocation Technique (PO)**
|
||||
[[LLM: Make deliberately provocative statements to jar thinking.]]
|
||||
- PO: Cars have square wheels
|
||||
- PO: Customers pay us to take products
|
||||
- PO: The problem solves itself
|
||||
- Extract useful ideas from provocations
|
||||
|
||||
### 3. Technique Selection Guide
|
||||
|
||||
[[LLM: Help user select appropriate techniques based on their needs.]]
|
||||
|
||||
**For Initial Exploration:**
|
||||
- What If Scenarios
|
||||
- First Principles
|
||||
- Mind Mapping
|
||||
|
||||
**For Stuck/Blocked Thinking:**
|
||||
- Random Stimulation
|
||||
- Reversal/Inversion
|
||||
- Provocation Technique
|
||||
|
||||
**For Systematic Coverage:**
|
||||
- SCAMPER
|
||||
- Morphological Analysis
|
||||
- Six Thinking Hats
|
||||
|
||||
**For Deep Understanding:**
|
||||
- Five Whys
|
||||
- Analogical Thinking
|
||||
- First Principles
|
||||
|
||||
**For Team/Collaborative Settings:**
|
||||
- Brainwriting
|
||||
- "Yes, And..."
|
||||
- Six Thinking Hats
|
||||
|
||||
### 4. Session Flow Management
|
||||
|
||||
[[LLM: Guide the brainstorming session with appropriate pacing and technique transitions.]]
|
||||
|
||||
1. **Warm-up Phase** (5-10 min)
|
||||
- Start with accessible techniques
|
||||
- Build creative confidence
|
||||
- Establish "no judgment" atmosphere
|
||||
|
||||
2. **Divergent Phase** (20-30 min)
|
||||
- Use expansion techniques
|
||||
- Generate quantity over quality
|
||||
- Encourage wild ideas
|
||||
|
||||
3. **Convergent Phase** (15-20 min)
|
||||
- Group and categorize ideas
|
||||
- Identify patterns and themes
|
||||
- Select promising directions
|
||||
|
||||
4. **Synthesis Phase** (10-15 min)
|
||||
- Combine complementary ideas
|
||||
- Refine and develop concepts
|
||||
- Prepare summary of insights
|
||||
|
||||
### 5. Output Format
|
||||
|
||||
[[LLM: Present brainstorming results in an organized, actionable format.]]
|
||||
|
||||
**Session Summary:**
|
||||
- Techniques used
|
||||
- Number of ideas generated
|
||||
- Key themes identified
|
||||
|
||||
**Idea Categories:**
|
||||
1. **Immediate Opportunities** - Ideas that could be implemented now
|
||||
2. **Future Innovations** - Ideas requiring more development
|
||||
3. **Moonshots** - Ambitious, transformative ideas
|
||||
4. **Insights & Learnings** - Key realizations from the session
|
||||
|
||||
**Next Steps:**
|
||||
- Which ideas to explore further
|
||||
- Recommended follow-up techniques
|
||||
- Suggested research areas
|
||||
|
||||
## Important Notes
|
||||
|
||||
- Maintain energy and momentum throughout the session
|
||||
- Defer judgment - all ideas are valid during generation
|
||||
- Quantity leads to quality - aim for many ideas
|
||||
- Build on ideas collaboratively
|
||||
- Document everything - even "silly" ideas can spark breakthroughs
|
||||
- Take breaks if energy flags
|
||||
- End with clear next actions
|
||||
@@ -7,13 +7,41 @@ This task guides you through creating a new BMAD agent that conforms to the agen
|
||||
## Prerequisites
|
||||
|
||||
1. Load and understand the agent schema: `/bmad-core/schemas/agent-schema.yml`
|
||||
2. Review existing agents in `/agents/` to understand naming patterns
|
||||
3. Check existing teams in `/bmad-core/agent-teams/` for integration opportunities
|
||||
4. Review workflows in `/bmad-core/workflows/` to understand where the agent might fit
|
||||
2. Load and understand the persona schema: `/bmad-core/schemas/persona-schema.yml`
|
||||
3. Review existing agents in `/agents/` to understand naming patterns
|
||||
4. Review existing personas in `/bmad-core/personas/` for reusable base personalities
|
||||
5. Check existing teams in `/bmad-core/agent-teams/` for integration opportunities
|
||||
6. Review workflows in `/bmad-core/workflows/` to understand where the agent might fit
|
||||
|
||||
## Process
|
||||
|
||||
### 1. Gather Core Agent Information
|
||||
### 1. Determine Persona Strategy
|
||||
|
||||
Start by asking the user about their persona approach:
|
||||
|
||||
**"Are you creating this agent based on an existing persona?"**
|
||||
|
||||
#### Option A: Use Existing Persona
|
||||
|
||||
- List available personas from `/bmad-core/personas/`
|
||||
- User selects or provides path to existing persona
|
||||
- Agent will reference this persona file
|
||||
- Allows customization through `customize` field
|
||||
|
||||
#### Option B: Create New Reusable Persona
|
||||
|
||||
- User wants to create a base persona for multiple agents
|
||||
- Create both a persona file and agent file
|
||||
- Good for creating variations (e.g., multiple dev agents with different specializations)
|
||||
|
||||
#### Option C: Create Self-Contained Agent
|
||||
|
||||
- User wants a unique, one-off agent
|
||||
- Persona will be embedded in the agent's `customize` field
|
||||
- `persona` field will be `null`
|
||||
- Requires comprehensive persona definition in customize
|
||||
|
||||
### 2. Gather Core Agent Information
|
||||
|
||||
Based on the agent schema's required fields, collect:
|
||||
|
||||
@@ -23,22 +51,73 @@ Based on the agent schema's required fields, collect:
|
||||
- **Professional Title**: 5-50 characters (e.g., "Data Analyst", "Security Expert")
|
||||
- **Description**: 20-300 characters describing the agent's main goal and purpose
|
||||
|
||||
### 2. Define Personality and Expertise
|
||||
### 3. Define or Reference Persona
|
||||
|
||||
Create a comprehensive persona by exploring:
|
||||
#### For Existing Persona (Option A):
|
||||
|
||||
- **Identity**: Extended description of specialization (20+ characters)
|
||||
- **Focus**: Primary objectives and responsibilities (20+ characters)
|
||||
- **Style**: Communication and approach characteristics (20+ characters)
|
||||
- **Core Principles**: At least 3 principles including the required "Numbered Options Protocol"
|
||||
- **Experience Level**: Years in field and depth of expertise
|
||||
- **Working Approach**: How they solve problems and deliver value
|
||||
- Set `persona: "bmad-core/personas/{persona-id}.md"`
|
||||
- Use `customize` for minor adjustments (max 500 chars)
|
||||
- Extract startup instructions from persona file
|
||||
|
||||
### 3. Identify Dependencies
|
||||
#### For New Persona (Option B):
|
||||
|
||||
1. Create `/bmad-core/personas/{persona-id}.md` following persona schema:
|
||||
|
||||
```markdown
|
||||
# Role: {Title} Agent
|
||||
|
||||
## Persona
|
||||
|
||||
- Role: {Descriptive Role Statement}
|
||||
- Style: {Communication style and approach}
|
||||
|
||||
## Core {Title} Principles (Always Active)
|
||||
|
||||
- **{Principle Name}:** {Detailed explanation}
|
||||
- **{Principle Name}:** {Detailed explanation}
|
||||
- **Numbered Options Protocol:** When presenting multiple options, always use numbered lists for easy selection
|
||||
[Add more principles as needed]
|
||||
|
||||
## Critical Start Up Operating Instructions
|
||||
|
||||
- Let the User Know what Tasks you can perform in a numbered list for user selection.
|
||||
- Execute the Full Tasks as Selected. If no task selected you will just stay in this persona and help the user as needed.
|
||||
- When conversing with the user and providing advice or multiple options, always present them as numbered lists for easy selection. When appropriate, also offer `advanced-elicitation` options during conversations.
|
||||
```
|
||||
|
||||
2. Set `persona: "bmad-core/personas/{persona-id}.md"` in agent
|
||||
3. Extract startup instructions for agent's `startup` field
|
||||
|
||||
#### For Embedded Persona (Option C):
|
||||
|
||||
- Set `persona: null`
|
||||
- Create comprehensive `customize` field (200+ chars) including:
|
||||
- Character background and expertise
|
||||
- Communication style
|
||||
- Core principles and values
|
||||
- Working approach
|
||||
- Key motivations
|
||||
- Define `startup` array with operating instructions
|
||||
|
||||
### 4. Define Startup Instructions
|
||||
|
||||
All agents now include startup instructions in the agent configuration:
|
||||
|
||||
```yaml
|
||||
startup:
|
||||
- "Let the User Know what Tasks you can perform in a numbered list for user selection."
|
||||
- "Execute the Full Tasks as Selected. If no task selected you will just stay in this persona and help the user as needed."
|
||||
- "[Additional agent-specific startup instructions]"
|
||||
```
|
||||
|
||||
For agents with external personas, extract and adapt the startup instructions from the persona file.
|
||||
|
||||
### 5. Identify Dependencies
|
||||
|
||||
Analyze what resources the agent needs:
|
||||
|
||||
#### Tasks (from `/bmad-core/tasks/`)
|
||||
|
||||
- Review available tasks and identify which apply
|
||||
- Common tasks most agents need:
|
||||
- `advanced-elicitation` (for conversational depth)
|
||||
@@ -47,150 +126,466 @@ Analyze what resources the agent needs:
|
||||
- Identify any new specialized tasks needed
|
||||
|
||||
#### Templates (from `/bmad-core/templates/`)
|
||||
|
||||
- Which document templates will this agent create/use?
|
||||
- Match template pattern: `^[a-z][a-z0-9-]*-tmpl$`
|
||||
|
||||
#### Checklists (from `/bmad-core/checklists/`)
|
||||
|
||||
- Which quality checklists apply to their work?
|
||||
- Match checklist pattern: `^[a-z][a-z0-9-]*-checklist$`
|
||||
|
||||
#### Data Files (from `/bmad-core/data/`)
|
||||
|
||||
- `bmad-kb` (if they need BMAD methodology knowledge)
|
||||
- `technical-preferences` (if they make technical decisions)
|
||||
- Other specialized data files
|
||||
|
||||
### 4. Create the Persona File
|
||||
|
||||
Create `/bmad-core/personas/{agent-id}.md` following the schema-required structure:
|
||||
(For user agents: `/bmad-core/personas/.{agent-id}.md`)
|
||||
|
||||
```markdown
|
||||
# Role: {Title} Agent
|
||||
|
||||
## Persona
|
||||
|
||||
- Role: {Descriptive Role Statement}
|
||||
- Style: {Communication style and approach}
|
||||
|
||||
## Core {Title} Principles (Always Active)
|
||||
|
||||
- **{Principle Name}:** {Detailed explanation}
|
||||
- **{Principle Name}:** {Detailed explanation}
|
||||
- **Numbered Options Protocol:** When presenting multiple options, always use numbered lists for easy selection
|
||||
[Add more principles as needed]
|
||||
|
||||
## Critical Start Up Operating Instructions
|
||||
|
||||
- Let the User Know what Tasks you can perform in a numbered list for user selection.
|
||||
- Execute the Full Tasks as Selected. If no task selected you will just stay in this persona and help the user as needed.
|
||||
- When conversing with the user and providing advice or multiple options, always present them as numbered lists for easy selection. When appropriate, also offer `advanced-elicitation` options during conversations.
|
||||
|
||||
[Add any agent-specific sections like Expertise, Workflow, etc.]
|
||||
```
|
||||
|
||||
### 5. Create the Agent Configuration
|
||||
### 6. Create the Agent Configuration
|
||||
|
||||
Create `/agents/{agent-id}.yml` conforming to the schema:
|
||||
(For user agents: `/agents/.{agent-id}.yml`)
|
||||
|
||||
#### With External Persona:
|
||||
|
||||
```yaml
|
||||
agent:
|
||||
name: {Character Name}
|
||||
id: {agent-id}
|
||||
title: {Professional Title}
|
||||
description: {20-300 character description}
|
||||
persona: bmad-core/personas/{agent-id}.md
|
||||
customize: "" # or specific customizations
|
||||
name: { Character Name }
|
||||
id: { agent-id }
|
||||
title: { Professional Title }
|
||||
description: { 20-300 character description }
|
||||
persona: bmad-core/personas/{persona-id}.md
|
||||
customize: "" # or minor customizations
|
||||
startup:
|
||||
- { Startup instruction 1 }
|
||||
- { Startup instruction 2 }
|
||||
|
||||
dependencies:
|
||||
tasks:
|
||||
- {task-id} # from identified tasks
|
||||
templates:
|
||||
- {template-id} # from identified templates
|
||||
checklists:
|
||||
- {checklist-id} # from identified checklists
|
||||
data:
|
||||
- {data-id} # from identified data files
|
||||
utils:
|
||||
- {util-id} # typically empty or specific utils
|
||||
tasks: [{ task-ids }]
|
||||
templates: [{ template-ids }]
|
||||
checklists: [{ checklist-ids }]
|
||||
data: [{ data-ids }]
|
||||
utils: [{ util-ids }]
|
||||
```
|
||||
|
||||
### 6. Team Integration Analysis
|
||||
#### With Embedded Persona:
|
||||
|
||||
```yaml
|
||||
agent:
|
||||
name: { Character Name }
|
||||
id: { agent-id }
|
||||
title: { Professional Title }
|
||||
description: { 20-300 character description }
|
||||
persona: null
|
||||
customize: >-
|
||||
{Comprehensive persona definition including background, style,
|
||||
principles, approach, and motivations - minimum 200 characters}
|
||||
startup:
|
||||
- { Startup instruction 1 }
|
||||
- { Startup instruction 2 }
|
||||
- { Additional instructions }
|
||||
|
||||
dependencies:
|
||||
tasks: [{ task-ids }]
|
||||
templates: [{ template-ids }]
|
||||
checklists: [{ checklist-ids }]
|
||||
data: [{ data-ids }]
|
||||
utils: [{ util-ids }]
|
||||
```
|
||||
|
||||
### 7. Team Integration Analysis
|
||||
|
||||
Review existing teams and suggest integration:
|
||||
|
||||
1. **Load team configurations** from `/bmad-core/agent-teams/`
|
||||
2. **Analyze fit** based on:
|
||||
|
||||
- Agent's role and expertise
|
||||
- Team's description and purpose
|
||||
- Existing agents in the team
|
||||
- Workflows the team supports
|
||||
|
||||
3. **Suggest teams** where this agent would add value:
|
||||
- For technical agents → suggest technical teams
|
||||
- For UX/design agents → suggest teams with UI workflows
|
||||
- For planning agents → suggest all teams
|
||||
3. **Suggest teams** where this agent would add value
|
||||
4. **Offer to update** team configurations
|
||||
|
||||
4. **Offer to update** team configurations:
|
||||
```yaml
|
||||
agents:
|
||||
- bmad
|
||||
- {existing-agents}
|
||||
- {new-agent-id} # Add here
|
||||
```
|
||||
|
||||
### 7. Workflow Integration Analysis
|
||||
### 8. Workflow Integration Analysis
|
||||
|
||||
Review workflows and suggest where the agent fits:
|
||||
|
||||
1. **Load workflow definitions** from `/bmad-core/workflows/`
|
||||
2. **Analyze workflow stages** to identify where this agent would contribute
|
||||
3. **Suggest integration points**:
|
||||
- Planning phases → analysts, PMs
|
||||
- Design phases → UX experts, architects
|
||||
- Implementation phases → developers
|
||||
- Validation phases → QA, PO
|
||||
|
||||
3. **Suggest integration points**
|
||||
4. **Document recommendations** for workflow updates if needed
|
||||
|
||||
### 8. Create IDE Agent (Optional)
|
||||
### 9. Create IDE Agent Version
|
||||
|
||||
If the agent should also work in IDE environments:
|
||||
After creating the full agent, offer to create an IDE-optimized version:
|
||||
|
||||
1. Create `/bmad-core/ide-agents/{agent-id}.ide.md`
|
||||
2. Follow the IDE agent schema from `/bmad-core/schemas/ide-agent-schema.yml`
|
||||
3. Include required commands (*help, *chat-mode) and startup instructions
|
||||
**"Would you like to create an IDE version of this agent for use in Cursor/Windsurf?"**
|
||||
|
||||
### 9. Validation and Testing
|
||||
If yes, proceed with optimization:
|
||||
|
||||
#### 9.1 Confirm IDE Agent Details
|
||||
|
||||
- **IDE Agent Name**: Confirm or adjust the name (default: same as full agent)
|
||||
- **Target Size**: Aim for under 3K characters (4K maximum)
|
||||
- **Primary Focus**: Identify the ONE core capability to emphasize
|
||||
|
||||
#### 9.2 Size Optimization Process
|
||||
|
||||
**Key Insight**: Write for LLM comprehension, not human readability. LLMs understand dense, abbreviated content better than you might expect.
|
||||
|
||||
**CRITICAL REQUIREMENT**: All IDE agents MUST include the "Numbered Options Protocol" principle. This ensures:
|
||||
|
||||
- All lists presented with numbers (1, 2, 3...)
|
||||
- Multiple options offered as numbered choices
|
||||
- Sections/items referenced by number
|
||||
- User can select by entering a number
|
||||
|
||||
1. **Use LLM-Optimized Language**
|
||||
|
||||
- Use abbreviations LLMs understand: API, REST, CRUD, JWT, etc.
|
||||
- Dense keyword lists instead of sentences: "Expert: React, Node, AWS, Docker"
|
||||
- Technical shorthand: "SOLID principles" not "Single responsibility, Open-closed..."
|
||||
- Compressed syntax: "Focus: secure/scalable/tested APIs"
|
||||
- Remove articles/connectors: "Creates PRDs, validates requirements" not "Creates the PRDs and validates all requirements"
|
||||
|
||||
2. **Extract Core Persona Elements**
|
||||
|
||||
- Compress to keyword phrases
|
||||
- Stack related concepts with slashes: "PM/Strategy/Research"
|
||||
- Use domain abbreviations
|
||||
|
||||
3. **Minimize File References**
|
||||
|
||||
- Only essential paths
|
||||
- Use shortest valid references
|
||||
|
||||
4. **Streamline Commands**
|
||||
|
||||
- Terse descriptions
|
||||
- Assume LLM context understanding
|
||||
- Reference tasks by ID only
|
||||
|
||||
5. **Minimize Examples & Scripts**
|
||||
|
||||
- Minimal examples only (cut first if oversized)
|
||||
- Replace full response scripts with instructions
|
||||
- Example: Instead of "Say: 'I'll analyze your requirements and create...'"
|
||||
- Use: "Acknowledge request, explain approach"
|
||||
- Trust LLM to generate appropriate responses
|
||||
|
||||
6. **Compress Startup Instructions**
|
||||
- Combine related directives
|
||||
- Use imperative mood
|
||||
- Eliminate politeness/filler
|
||||
|
||||
#### 9.3 Size Validation
|
||||
|
||||
After creating the IDE version:
|
||||
|
||||
1. **Check character count**: Must be under 4K (ideally under 3K)
|
||||
2. **If too large**, identify issues:
|
||||
|
||||
- Too much embedded functionality → refactor to tasks
|
||||
- Verbose descriptions → compress further
|
||||
- Too many commands → prioritize core ones
|
||||
|
||||
3. **Warning if oversized**:
|
||||
|
||||
```
|
||||
⚠️ WARNING: IDE agent is {size} characters (target: <3000)
|
||||
|
||||
Common issues:
|
||||
- Too much logic embedded (should be in tasks)
|
||||
- Verbose persona description
|
||||
- Too many commands listed
|
||||
|
||||
Options:
|
||||
1. Proceed anyway (may have issues in IDE)
|
||||
2. Further optimize (recommended)
|
||||
3. Refactor agent to use more external tasks
|
||||
```
|
||||
|
||||
#### 9.4 IDE Agent Template
|
||||
|
||||
Create `/bmad-core/ide-agents/{agent-id}.ide.md`:
|
||||
|
||||
```markdown
|
||||
# Role: {Title} IDE Agent
|
||||
|
||||
## File References
|
||||
|
||||
`taskroot`: `bmad-core/tasks/`
|
||||
`templates`: `bmad-core/templates/`
|
||||
{only essential references}
|
||||
|
||||
## Persona
|
||||
|
||||
- **Name:** {Name}
|
||||
- **Role:** {Role}
|
||||
- **Identity:** {Role/Domain/Specialty}
|
||||
- **Focus:** {Primary-objective/key-outcomes}
|
||||
- **Style:** {Trait1/trait2/trait3}
|
||||
|
||||
## Core Principles (Always Active)
|
||||
|
||||
- **{Principle}:** {LLM-friendly description}
|
||||
- **{Principle}:** {Compressed key points}
|
||||
- **Numbered Options Protocol:** Present options as numbered lists
|
||||
|
||||
## Critical Startup Operating Instructions
|
||||
|
||||
1. I'm {Role} {Name}. Type \*help for commands
|
||||
2. {Core directive in imperative mood}
|
||||
|
||||
## Commands
|
||||
|
||||
- `*help` - Show commands as numbered list
|
||||
- `*chat-mode` - Conversational mode + advanced-elicitation
|
||||
- `*{cmd1}` - {Action verb + object}
|
||||
- `*{cmd2}` - {Action verb + object}
|
||||
{4-6 commands max}
|
||||
```
|
||||
|
||||
#### 9.5 Optimization Examples
|
||||
|
||||
**Full Agent Persona** (500+ chars):
|
||||
|
||||
```
|
||||
Elena is a meticulous Data Analyst with expertise in statistical analysis,
|
||||
data visualization, and pattern recognition. She approaches problems with
|
||||
scientific rigor, always seeking evidence in the data before drawing
|
||||
conclusions. Her style is precise, methodical, and focused on delivering
|
||||
actionable insights. She excels at transforming complex data into clear
|
||||
narratives that stakeholders can understand and act upon.
|
||||
```
|
||||
|
||||
**IDE Optimized (Human-Readable)** (150 chars):
|
||||
|
||||
```
|
||||
- **Identity:** Data analysis expert specializing in statistics and visualization
|
||||
- **Style:** Precise, evidence-driven, focused on actionable insights
|
||||
```
|
||||
|
||||
**IDE Optimized (LLM-Optimized)** (95 chars):
|
||||
|
||||
```
|
||||
- **Identity:** Data analyst: stats/viz/patterns
|
||||
- **Style:** Precise/evidence-based/actionable
|
||||
```
|
||||
|
||||
**More LLM Optimization Examples**:
|
||||
|
||||
Instead of: "Creates comprehensive PRDs with user stories, acceptance criteria, and success metrics"
|
||||
Use: "Creates PRDs: user-stories/criteria/metrics"
|
||||
|
||||
Instead of: "Expert in React, Vue, Angular with deep knowledge of state management"
|
||||
Use: "Expert: React/Vue/Angular, state-mgmt"
|
||||
|
||||
Instead of: "Validates requirements against business objectives and technical constraints"
|
||||
Use: "Validates: reqs→objectives/constraints"
|
||||
|
||||
**Response Script Optimizations**:
|
||||
|
||||
Instead of: "Say: 'Hello! I'm Sarah, your Product Owner. I'll help validate your requirements. Here are the tasks I can help with: 1) Validate PRD, 2) Check architecture...'"
|
||||
Use: "Greet as PO Sarah. List available tasks (numbered)"
|
||||
|
||||
Instead of: "Respond: 'I've analyzed your code and found 3 issues: First, the API endpoint lacks authentication...'"
|
||||
Use: "Report findings with numbered list"
|
||||
|
||||
Instead of: "When user asks for help, say: 'I can assist with the following: 1. Creating test plans...'"
|
||||
Use: "On help request: show numbered capabilities"
|
||||
|
||||
#### 9.6 Common Refactoring Needs
|
||||
|
||||
When agents are too large for IDE:
|
||||
|
||||
1. **Analyst Agent**: Move brainstorming techniques, research methodologies to tasks
|
||||
2. **Architect Agent**: Extract architecture patterns, technology lists to templates
|
||||
3. **PM Agent**: Move PRD sections, prioritization frameworks to tasks
|
||||
4. **Dev Agent**: Extract coding standards, patterns to external docs
|
||||
|
||||
### 10. Validation and Testing
|
||||
|
||||
1. **Validate against schema**: Ensure configuration matches agent-schema.yml
|
||||
2. **Run build validation**: `npm run validate`
|
||||
3. **Build the agent**: `npm run build:agent -a {agent-id}`
|
||||
4. **Test in teams**: Build teams that include this agent
|
||||
5. **Review output**: Check `/dist/agents/{agent-id}.txt`
|
||||
2. **Validate persona**: If external, ensure persona file exists and is valid
|
||||
3. **Run build validation**: `npm run validate`
|
||||
4. **Build the agent**: `npm run build:agent -a {agent-id}`
|
||||
5. **Test in teams**: Build teams that include this agent
|
||||
6. **Review output**: Check `/dist/agents/{agent-id}.txt`
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Agent with Existing Persona
|
||||
|
||||
```yaml
|
||||
agent:
|
||||
name: "Jennifer"
|
||||
id: "pm-senior"
|
||||
title: "Senior Product Manager"
|
||||
description: "Experienced PM focused on enterprise product strategy and stakeholder management"
|
||||
persona: "bmad-core/personas/pm.md"
|
||||
customize: "Specializes in B2B SaaS products with emphasis on enterprise features and compliance requirements."
|
||||
startup:
|
||||
- "Let the User Know what Tasks you can perform in a numbered list for user selection."
|
||||
- "Focus on enterprise-scale product challenges and stakeholder alignment."
|
||||
- "Execute the Full Tasks as Selected."
|
||||
|
||||
dependencies:
|
||||
tasks:
|
||||
- "create-doc-from-template"
|
||||
- "advanced-elicitation"
|
||||
- "stakeholder-analysis"
|
||||
templates:
|
||||
- "prd-tmpl"
|
||||
- "enterprise-prd-tmpl"
|
||||
checklists:
|
||||
- "pm-checklist"
|
||||
- "enterprise-checklist"
|
||||
data:
|
||||
- "bmad-kb"
|
||||
- "enterprise-patterns"
|
||||
utils:
|
||||
- "template-format"
|
||||
```
|
||||
|
||||
### Example 2: Self-Contained Agent with Embedded Persona
|
||||
|
||||
```yaml
|
||||
agent:
|
||||
name: "Viktor"
|
||||
id: "security-architect"
|
||||
title: "Security Architect"
|
||||
description: "Designs and reviews system security architecture ensuring robust protection against threats"
|
||||
persona: null
|
||||
customize: >-
|
||||
Viktor is a seasoned Security Architect with 15 years defending critical systems.
|
||||
His approach combines deep technical knowledge with practical risk assessment.
|
||||
He thinks like an attacker to build better defenses, always considering the
|
||||
full threat landscape. His style is thorough but pragmatic, focusing on
|
||||
implementable security that doesn't cripple usability. Core principles include:
|
||||
defense in depth, zero trust architecture, security by design not bolted on,
|
||||
assume breach and plan accordingly, and balance security with user experience.
|
||||
He excels at threat modeling, security reviews, and creating security guidelines
|
||||
that developers can actually follow.
|
||||
startup:
|
||||
- "Let the User Know what security tasks you can perform in a numbered list for user selection."
|
||||
- "Always start by understanding the threat model and compliance requirements."
|
||||
- "Focus on practical, implementable security recommendations."
|
||||
- "When conversing, offer advanced-elicitation for deeper security analysis."
|
||||
|
||||
dependencies:
|
||||
tasks:
|
||||
- "threat-modeling"
|
||||
- "security-review"
|
||||
- "create-doc-from-template"
|
||||
templates:
|
||||
- "security-architecture-tmpl"
|
||||
- "threat-model-tmpl"
|
||||
checklists:
|
||||
- "security-checklist"
|
||||
- "owasp-checklist"
|
||||
data:
|
||||
- "security-patterns"
|
||||
- "compliance-frameworks"
|
||||
utils:
|
||||
- "security-tools"
|
||||
```
|
||||
|
||||
## IDE Agent Best Practices
|
||||
|
||||
### What Makes a Good IDE Agent
|
||||
|
||||
1. **Single Focus**: Excel at ONE thing, not many
|
||||
2. **Reference Heavy**: Use tasks/templates, don't embed logic
|
||||
3. **Minimal Personality**: Just enough to be helpful
|
||||
4. **Action Oriented**: Focus on WHAT they do, not WHO they are
|
||||
5. **LLM-Optimized Language**: Dense, abbreviated, technical
|
||||
6. **Concise Commands**: Clear, short command descriptions
|
||||
|
||||
### LLM-Friendly Abbreviations
|
||||
|
||||
Common abbreviations LLMs understand well:
|
||||
|
||||
- **Tech**: API, REST, GraphQL, CRUD, JWT, OAuth, CI/CD, K8s
|
||||
- **Patterns**: MVC, SOLID, DRY, KISS, YAGNI, GoF
|
||||
- **Roles**: PM, PO, QA, UX, DevOps, SRE, DBA
|
||||
- **Processes**: TDD, BDD, MVP, PoC, UAT, A/B
|
||||
- **Formats**: JSON, YAML, XML, CSV, MD
|
||||
- **Concepts**: auth, viz, mgmt, config, reqs, docs
|
||||
|
||||
### Size Comparison Examples
|
||||
|
||||
❌ **Too Large** (Full Agent Style):
|
||||
|
||||
```yaml
|
||||
The agent embodies deep expertise in API design, with years of experience
|
||||
in RESTful services, GraphQL implementations, and microservice architectures.
|
||||
They understand OAuth flows, JWT tokens, rate limiting strategies, caching
|
||||
patterns, and have strong opinions about API versioning...
|
||||
```
|
||||
|
||||
✅ **Just Right** (IDE Style):
|
||||
|
||||
```yaml
|
||||
- **Identity:** API design expert specializing in REST and GraphQL
|
||||
- **Focus:** Clean, secure, documented APIs following standards
|
||||
```
|
||||
|
||||
### When NOT to Create IDE Version
|
||||
|
||||
Some agents may be too complex for IDE format:
|
||||
|
||||
- Agents with 10+ essential commands
|
||||
- Agents requiring extensive context
|
||||
- Agents that coordinate multiple other agents
|
||||
- Orchestrator-type agents (like BMAD)
|
||||
|
||||
In these cases, recommend using the full agent in web platforms.
|
||||
|
||||
## Integration Checklist
|
||||
|
||||
After creating the agent, verify:
|
||||
|
||||
- [ ] Persona strategy chosen and implemented correctly
|
||||
- [ ] Agent configuration validates against schema
|
||||
- [ ] Persona file includes all required sections
|
||||
- [ ] If external persona: file exists and is referenced correctly
|
||||
- [ ] If embedded persona: customize field is comprehensive (200+ chars)
|
||||
- [ ] Startup instructions included in agent configuration
|
||||
- [ ] All referenced dependencies exist
|
||||
- [ ] Team integration suggestions documented
|
||||
- [ ] Workflow integration points identified
|
||||
- [ ] Build completes without errors
|
||||
- [ ] Agent output is under size limits (if applicable)
|
||||
- [ ] IDE agent created (if requested)
|
||||
- [ ] IDE agent under 4K characters (ideally under 3K)
|
||||
- [ ] IDE agent functionality preserved
|
||||
- [ ] Refactoring completed if agent was oversized
|
||||
|
||||
## Example Integration Analysis
|
||||
## Troubleshooting Oversized Agents
|
||||
|
||||
When creating a "Security Expert" agent:
|
||||
If an IDE agent exceeds size limits, check for:
|
||||
|
||||
**Team Integration:**
|
||||
- `team-fullstack`: Add for security reviews in full-stack projects
|
||||
- `team-no-ui`: Add for backend service security assessments
|
||||
1. **Embedded Logic**: Move complex logic to tasks
|
||||
- Example: Analyst's brainstorming techniques → create `brainstorming-techniques` task
|
||||
2. **Verbose Descriptions**: Compress without losing meaning
|
||||
|
||||
**Workflow Integration:**
|
||||
- `greenfield-*`: Security review after architecture phase
|
||||
- `brownfield-*`: Security assessment before implementation
|
||||
- Before: "Extensive experience in cloud architecture across AWS, Azure, and GCP"
|
||||
- After: "Cloud architect (AWS/Azure/GCP)"
|
||||
|
||||
This ensures the new agent enhances existing capabilities rather than working in isolation.
|
||||
3. **Too Many Commands**: Prioritize core functionality
|
||||
|
||||
- Keep: Primary creation/analysis commands
|
||||
- Remove: Nice-to-have utility commands
|
||||
|
||||
4. **Inline Examples**: Remove all examples
|
||||
|
||||
- Let tasks provide examples
|
||||
- Reference documentation instead
|
||||
|
||||
5. **Redundant Content**: Eliminate duplication
|
||||
- Combine similar principles
|
||||
- Merge related commands
|
||||
|
||||
This flexible approach allows users to create agents that either leverage existing personas for consistency or create unique, self-contained agents for specialized needs, with IDE-optimized versions for development environments.
|
||||
|
||||
@@ -1,55 +1,289 @@
|
||||
# Deep Research Phase
|
||||
# Create Deep Research Prompt Task
|
||||
|
||||
Leveraging advanced analytical capabilities, the Deep Research Phase with the PM is designed to provide targeted, strategic insights crucial for product definition. Unlike the broader exploratory research an Analyst might undertake, the PM utilizes deep research to:
|
||||
|
||||
- **Validate Product Hypotheses:** Rigorously test assumptions about market need, user problems, and the viability of specific product concepts.
|
||||
- **Refine Target Audience & Value Proposition:** Gain a nuanced understanding of specific user segments, their precise pain points, and how the proposed product delivers unique value to them.
|
||||
- **Focused Competitive Analysis:** Analyze competitors through the lens of a specific product idea to identify differentiation opportunities, feature gaps to exploit, and potential market positioning challenges.
|
||||
- **De-risk PRD Commitments:** Ensure that the problem, proposed solution, and core features are well-understood and validated _before_ detailed planning and resource allocation in the PRD Generation Mode.
|
||||
|
||||
Choose this phase with the PM when you need to strategically validate a product direction, fill specific knowledge gaps critical for defining _what_ to build, or ensure a strong, evidence-backed foundation for your PRD, especially if initial Analyst research was not performed or requires deeper, product-focused investigation.
|
||||
This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
|
||||
|
||||
## Purpose
|
||||
|
||||
- To gather foundational information, validate concepts, understand market needs, or analyze competitors when a comprehensive Project Brief from an Analyst is unavailable or insufficient.
|
||||
- To ensure the PM has a solid, data-informed basis for defining a valuable and viable product before committing to PRD specifics.
|
||||
- To de-risk product decisions by grounding them in targeted research, especially if the user is engaging the PM directly without prior Analyst work or if the initial brief lacks necessary depth.
|
||||
Generate well-structured research prompts that:
|
||||
|
||||
## Instructions
|
||||
- Define clear research objectives and scope
|
||||
- Specify appropriate research methodologies
|
||||
- Outline expected deliverables and formats
|
||||
- Guide systematic investigation of complex topics
|
||||
- Ensure actionable insights are captured
|
||||
|
||||
<critical_rule>Note on Deep Research Execution:</critical_rule>
|
||||
To perform deep research effectively, please be aware:
|
||||
## Research Type Selection
|
||||
|
||||
- You may need to use this current conversational agent to help you formulate a comprehensive research prompt, which can then be executed by a dedicated deep research model or function.
|
||||
- Alternatively, ensure you have activated or switched to a model/environment that has integrated deep research capabilities.
|
||||
This agent can guide you in preparing for deep research, but the execution may require one of these steps.
|
||||
[[LLM: First, help the user select the most appropriate research focus based on their needs and any input documents they've provided.]]
|
||||
|
||||
1. **Assess Inputs & Identify Gaps:**
|
||||
- Review any existing inputs (user's initial idea, high-level requirements, partial brief from Analyst, etc.).
|
||||
- Clearly identify critical knowledge gaps concerning:
|
||||
- Target audience (needs, pain points, behaviors, key segments).
|
||||
- Market landscape (size, trends, opportunities, potential saturation).
|
||||
- Competitive analysis (key direct/indirect competitors, their offerings, strengths, weaknesses, market positioning, potential differentiators for this product).
|
||||
- Problem/Solution validation (evidence supporting the proposed solution's value and fit for the identified problem).
|
||||
- High-level technical or resource considerations (potential major roadblocks or dependencies).
|
||||
2. **Formulate Research Plan:**
|
||||
- Define specific, actionable research questions to address the identified gaps.
|
||||
- Propose targeted research activities (e.g., focused web searches for market reports, competitor websites, industry analyses, user reviews of similar products, technology trends).
|
||||
- <important_note>Confirm this research plan, scope, and key questions with the user before proceeding with research execution.</important_note>
|
||||
3. **Execute Research:**
|
||||
- Conduct the planned research activities systematically.
|
||||
- Prioritize gathering credible, relevant, and actionable insights that directly inform product definition and strategy.
|
||||
4. **Synthesize & Present Findings:**
|
||||
- Organize and summarize key research findings in a clear, concise, and easily digestible manner (e.g., bullet points, brief summaries per research question).
|
||||
- Highlight the most critical implications for the product's vision, strategy, target audience, core features, and potential risks.
|
||||
- Present these synthesized findings and their implications to the user.
|
||||
5. **Discussing and Utilizing Research Output:**
|
||||
- The comprehensive findings/report from this Deep Research phase can be substantial. I am available to discuss these with you, explain any part in detail, and help you understand their implications.
|
||||
- **Options for Utilizing These Findings for PRD Generation:**
|
||||
1. **Full Handoff to New PM Session:** The complete research output can serve as a foundational document if you initiate a _new_ session with a Product Manager (PM) agent who will then execute the 'PRD Generate Task'.
|
||||
2. **Key Insights Summary for This Session:** I can prepare a concise summary of the most critical findings, tailored to be directly actionable as we (in this current session) transition to potentially invoking the 'PRD Generate Task'.
|
||||
- <critical_rule>Regardless of how you proceed, it is highly recommended that these research findings (either the full output or the key insights summary) are provided as direct input when invoking the 'PRD Generate Task'. This ensures the PRD is built upon a solid, evidence-based foundation.</critical_rule>
|
||||
6. **Confirm Readiness for PRD Generation:**
|
||||
- Discuss with the user whether the gathered information provides a sufficient and confident foundation to proceed to the 'PRD Generate Task'.
|
||||
- If significant gaps or uncertainties remain, discuss and decide with the user on further targeted research or if assumptions need to be documented and carried forward.
|
||||
- Once confirmed, clearly state that the next step could be to invoke the 'PRD Generate Task' or, if applicable, revisit other phase options.
|
||||
### 1. Research Focus Options
|
||||
|
||||
Present these numbered options to the user:
|
||||
|
||||
1. **Product Validation Research**
|
||||
|
||||
- Validate product hypotheses and market fit
|
||||
- Test assumptions about user needs and solutions
|
||||
- Assess technical and business feasibility
|
||||
- Identify risks and mitigation strategies
|
||||
|
||||
2. **Market Opportunity Research**
|
||||
|
||||
- Analyze market size and growth potential
|
||||
- Identify market segments and dynamics
|
||||
- Assess market entry strategies
|
||||
- Evaluate timing and market readiness
|
||||
|
||||
3. **User & Customer Research**
|
||||
|
||||
- Deep dive into user personas and behaviors
|
||||
- Understand jobs-to-be-done and pain points
|
||||
- Map customer journeys and touchpoints
|
||||
- Analyze willingness to pay and value perception
|
||||
|
||||
4. **Competitive Intelligence Research**
|
||||
|
||||
- Detailed competitor analysis and positioning
|
||||
- Feature and capability comparisons
|
||||
- Business model and strategy analysis
|
||||
- Identify competitive advantages and gaps
|
||||
|
||||
5. **Technology & Innovation Research**
|
||||
|
||||
- Assess technology trends and possibilities
|
||||
- Evaluate technical approaches and architectures
|
||||
- Identify emerging technologies and disruptions
|
||||
- Analyze build vs. buy vs. partner options
|
||||
|
||||
6. **Industry & Ecosystem Research**
|
||||
|
||||
- Map industry value chains and dynamics
|
||||
- Identify key players and relationships
|
||||
- Analyze regulatory and compliance factors
|
||||
- Understand partnership opportunities
|
||||
|
||||
7. **Strategic Options Research**
|
||||
|
||||
- Evaluate different strategic directions
|
||||
- Assess business model alternatives
|
||||
- Analyze go-to-market strategies
|
||||
- Consider expansion and scaling paths
|
||||
|
||||
8. **Risk & Feasibility Research**
|
||||
|
||||
- Identify and assess various risk factors
|
||||
- Evaluate implementation challenges
|
||||
- Analyze resource requirements
|
||||
- Consider regulatory and legal implications
|
||||
|
||||
9. **Custom Research Focus**
|
||||
[[LLM: Allow user to define their own specific research focus.]]
|
||||
- User-defined research objectives
|
||||
- Specialized domain investigation
|
||||
- Cross-functional research needs
|
||||
|
||||
### 2. Input Processing
|
||||
|
||||
[[LLM: Based on the selected research type and any provided inputs (project brief, brainstorming results, etc.), extract relevant context and constraints.]]
|
||||
|
||||
**If Project Brief provided:**
|
||||
|
||||
- Extract key product concepts and goals
|
||||
- Identify target users and use cases
|
||||
- Note technical constraints and preferences
|
||||
- Highlight uncertainties and assumptions
|
||||
|
||||
**If Brainstorming Results provided:**
|
||||
|
||||
- Synthesize main ideas and themes
|
||||
- Identify areas needing validation
|
||||
- Extract hypotheses to test
|
||||
- Note creative directions to explore
|
||||
|
||||
**If Market Research provided:**
|
||||
|
||||
- Build on identified opportunities
|
||||
- Deepen specific market insights
|
||||
- Validate initial findings
|
||||
- Explore adjacent possibilities
|
||||
|
||||
**If Starting Fresh:**
|
||||
|
||||
- Gather essential context through questions
|
||||
- Define the problem space
|
||||
- Clarify research objectives
|
||||
- Establish success criteria
|
||||
|
||||
## Process
|
||||
|
||||
### 3. Research Prompt Structure
|
||||
|
||||
[[LLM: Based on the selected research type and context, collaboratively develop a comprehensive research prompt with these components.]]
|
||||
|
||||
#### A. Research Objectives
|
||||
|
||||
[[LLM: Work with the user to articulate clear, specific objectives for the research.]]
|
||||
|
||||
- Primary research goal and purpose
|
||||
- Key decisions the research will inform
|
||||
- Success criteria for the research
|
||||
- Constraints and boundaries
|
||||
|
||||
#### B. Research Questions
|
||||
|
||||
[[LLM: Develop specific, actionable research questions organized by theme.]]
|
||||
|
||||
**Core Questions:**
|
||||
|
||||
- Central questions that must be answered
|
||||
- Priority ranking of questions
|
||||
- Dependencies between questions
|
||||
|
||||
**Supporting Questions:**
|
||||
|
||||
- Additional context-building questions
|
||||
- Nice-to-have insights
|
||||
- Future-looking considerations
|
||||
|
||||
#### C. Research Methodology
|
||||
|
||||
[[LLM: Specify appropriate research methods based on the type and objectives.]]
|
||||
|
||||
**Data Collection Methods:**
|
||||
|
||||
- Secondary research sources
|
||||
- Primary research approaches (if applicable)
|
||||
- Data quality requirements
|
||||
- Source credibility criteria
|
||||
|
||||
**Analysis Frameworks:**
|
||||
|
||||
- Specific frameworks to apply
|
||||
- Comparison criteria
|
||||
- Evaluation methodologies
|
||||
- Synthesis approaches
|
||||
|
||||
#### D. Output Requirements
|
||||
|
||||
[[LLM: Define how research findings should be structured and presented.]]
|
||||
|
||||
**Format Specifications:**
|
||||
|
||||
- Executive summary requirements
|
||||
- Detailed findings structure
|
||||
- Visual/tabular presentations
|
||||
- Supporting documentation
|
||||
|
||||
**Key Deliverables:**
|
||||
|
||||
- Must-have sections and insights
|
||||
- Decision-support elements
|
||||
- Action-oriented recommendations
|
||||
- Risk and uncertainty documentation
|
||||
|
||||
### 4. Prompt Generation
|
||||
|
||||
[[LLM: Synthesize all elements into a comprehensive, ready-to-use research prompt.]]
|
||||
|
||||
**Research Prompt Template:**
|
||||
|
||||
```
|
||||
## Research Objective
|
||||
[Clear statement of what this research aims to achieve]
|
||||
|
||||
## Background Context
|
||||
[Relevant information from project brief, brainstorming, or other inputs]
|
||||
|
||||
## Research Questions
|
||||
|
||||
### Primary Questions (Must Answer)
|
||||
1. [Specific, actionable question]
|
||||
2. [Specific, actionable question]
|
||||
...
|
||||
|
||||
### Secondary Questions (Nice to Have)
|
||||
1. [Supporting question]
|
||||
2. [Supporting question]
|
||||
...
|
||||
|
||||
## Research Methodology
|
||||
|
||||
### Information Sources
|
||||
- [Specific source types and priorities]
|
||||
|
||||
### Analysis Frameworks
|
||||
- [Specific frameworks to apply]
|
||||
|
||||
### Data Requirements
|
||||
- [Quality, recency, credibility needs]
|
||||
|
||||
## Expected Deliverables
|
||||
|
||||
### Executive Summary
|
||||
- Key findings and insights
|
||||
- Critical implications
|
||||
- Recommended actions
|
||||
|
||||
### Detailed Analysis
|
||||
[Specific sections needed based on research type]
|
||||
|
||||
### Supporting Materials
|
||||
- Data tables
|
||||
- Comparison matrices
|
||||
- Source documentation
|
||||
|
||||
## Success Criteria
|
||||
[How to evaluate if research achieved its objectives]
|
||||
|
||||
## Timeline and Priority
|
||||
[If applicable, any time constraints or phasing]
|
||||
```
|
||||
|
||||
### 5. Review and Refinement
|
||||
|
||||
[[LLM: Present the draft research prompt for user review and refinement.]]
|
||||
|
||||
1. **Present Complete Prompt**
|
||||
|
||||
- Show the full research prompt
|
||||
- Explain key elements and rationale
|
||||
- Highlight any assumptions made
|
||||
|
||||
2. **Gather Feedback**
|
||||
|
||||
- Are the objectives clear and correct?
|
||||
- Do the questions address all concerns?
|
||||
- Is the scope appropriate?
|
||||
- Are output requirements sufficient?
|
||||
|
||||
3. **Refine as Needed**
|
||||
- Incorporate user feedback
|
||||
- Adjust scope or focus
|
||||
- Add missing elements
|
||||
- Clarify ambiguities
|
||||
|
||||
### 6. Next Steps Guidance
|
||||
|
||||
[[LLM: Provide clear guidance on how to use the research prompt.]]
|
||||
|
||||
**Execution Options:**
|
||||
|
||||
1. **Use with AI Research Assistant**: Provide this prompt to an AI model with research capabilities
|
||||
2. **Guide Human Research**: Use as a framework for manual research efforts
|
||||
3. **Hybrid Approach**: Combine AI and human research using this structure
|
||||
|
||||
**Integration Points:**
|
||||
|
||||
- How findings will feed into next phases
|
||||
- Which team members should review results
|
||||
- How to validate findings
|
||||
- When to revisit or expand research
|
||||
|
||||
## Important Notes
|
||||
|
||||
- The quality of the research prompt directly impacts the quality of insights gathered
|
||||
- Be specific rather than general in research questions
|
||||
- Consider both current state and future implications
|
||||
- Balance comprehensiveness with focus
|
||||
- Document assumptions and limitations clearly
|
||||
- Plan for iterative refinement based on initial findings
|
||||
|
||||
251
bmad-core/templates/competitor-analysis-tmpl.md
Normal file
251
bmad-core/templates/competitor-analysis-tmpl.md
Normal file
@@ -0,0 +1,251 @@
|
||||
# Competitive Analysis Report: {{Project/Product Name}}
|
||||
|
||||
[[LLM: This template guides comprehensive competitor analysis. Start by understanding the user's competitive intelligence needs and strategic objectives. Help them identify and prioritize competitors before diving into detailed analysis.]]
|
||||
|
||||
## Executive Summary
|
||||
|
||||
{{Provide high-level competitive insights, main threats and opportunities, and recommended strategic actions. Write this section LAST after completing all analysis.}}
|
||||
|
||||
## Analysis Scope & Methodology
|
||||
|
||||
### Analysis Purpose
|
||||
{{Define the primary purpose:
|
||||
- New market entry assessment
|
||||
- Product positioning strategy
|
||||
- Feature gap analysis
|
||||
- Pricing strategy development
|
||||
- Partnership/acquisition targets
|
||||
- Competitive threat assessment}}
|
||||
|
||||
### Competitor Categories Analyzed
|
||||
{{List categories included:
|
||||
- Direct Competitors: Same product/service, same target market
|
||||
- Indirect Competitors: Different product, same need/problem
|
||||
- Potential Competitors: Could enter market easily
|
||||
- Substitute Products: Alternative solutions
|
||||
- Aspirational Competitors: Best-in-class examples}}
|
||||
|
||||
### Research Methodology
|
||||
{{Describe approach:
|
||||
- Information sources used
|
||||
- Analysis timeframe
|
||||
- Confidence levels
|
||||
- Limitations}}
|
||||
|
||||
## Competitive Landscape Overview
|
||||
|
||||
### Market Structure
|
||||
{{Describe the competitive environment:
|
||||
- Number of active competitors
|
||||
- Market concentration (fragmented/consolidated)
|
||||
- Competitive dynamics
|
||||
- Recent market entries/exits}}
|
||||
|
||||
### Competitor Prioritization Matrix
|
||||
|
||||
[[LLM: Help categorize competitors by market share and strategic threat level]]
|
||||
|
||||
{{Create a 2x2 matrix:
|
||||
- Priority 1 (Core Competitors): High Market Share + High Threat
|
||||
- Priority 2 (Emerging Threats): Low Market Share + High Threat
|
||||
- Priority 3 (Established Players): High Market Share + Low Threat
|
||||
- Priority 4 (Monitor Only): Low Market Share + Low Threat}}
|
||||
|
||||
## Individual Competitor Profiles
|
||||
|
||||
[[LLM: Create detailed profiles for each Priority 1 and Priority 2 competitor. For Priority 3 and 4, create condensed profiles.]]
|
||||
|
||||
### {{Competitor Name}} - Priority {{1/2/3/4}}
|
||||
|
||||
#### Company Overview
|
||||
- **Founded:** {{Year, founders}}
|
||||
- **Headquarters:** {{Location}}
|
||||
- **Company Size:** {{Employees, revenue if known}}
|
||||
- **Funding:** {{Total raised, key investors}}
|
||||
- **Leadership:** {{Key executives}}
|
||||
|
||||
#### Business Model & Strategy
|
||||
- **Revenue Model:** {{How they make money}}
|
||||
- **Target Market:** {{Primary customer segments}}
|
||||
- **Value Proposition:** {{Core value promise}}
|
||||
- **Go-to-Market Strategy:** {{Sales and marketing approach}}
|
||||
- **Strategic Focus:** {{Current priorities}}
|
||||
|
||||
#### Product/Service Analysis
|
||||
- **Core Offerings:** {{Main products/services}}
|
||||
- **Key Features:** {{Standout capabilities}}
|
||||
- **User Experience:** {{UX strengths/weaknesses}}
|
||||
- **Technology Stack:** {{If relevant/known}}
|
||||
- **Pricing:** {{Model and price points}}
|
||||
|
||||
#### Strengths & Weaknesses
|
||||
|
||||
**Strengths:**
|
||||
- {{Strength 1}}
|
||||
- {{Strength 2}}
|
||||
- {{Strength 3}}
|
||||
|
||||
**Weaknesses:**
|
||||
- {{Weakness 1}}
|
||||
- {{Weakness 2}}
|
||||
- {{Weakness 3}}
|
||||
|
||||
#### Market Position & Performance
|
||||
- **Market Share:** {{Estimate if available}}
|
||||
- **Customer Base:** {{Size, notable clients}}
|
||||
- **Growth Trajectory:** {{Trending up/down/stable}}
|
||||
- **Recent Developments:** {{Key news, releases}}
|
||||
|
||||
<<REPEAT for each priority competitor>>
|
||||
|
||||
## Comparative Analysis
|
||||
|
||||
### Feature Comparison Matrix
|
||||
|
||||
[[LLM: Create a detailed comparison table of key features across competitors]]
|
||||
|
||||
| Feature Category | {{Your Company}} | {{Competitor 1}} | {{Competitor 2}} | {{Competitor 3}} |
|
||||
|-----------------|------------------|------------------|------------------|------------------|
|
||||
| **Core Functionality** |
|
||||
| Feature A | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} |
|
||||
| Feature B | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} |
|
||||
| **User Experience** |
|
||||
| Mobile App | {{Rating/Status}} | {{Rating/Status}} | {{Rating/Status}} | {{Rating/Status}} |
|
||||
| Onboarding Time | {{Time}} | {{Time}} | {{Time}} | {{Time}} |
|
||||
| **Integration & Ecosystem** |
|
||||
| API Availability | {{Yes/No/Limited}} | {{Yes/No/Limited}} | {{Yes/No/Limited}} | {{Yes/No/Limited}} |
|
||||
| Third-party Integrations | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} |
|
||||
| **Pricing & Plans** |
|
||||
| Starting Price | {{$X}} | {{$X}} | {{$X}} | {{$X}} |
|
||||
| Free Tier | {{Yes/No}} | {{Yes/No}} | {{Yes/No}} | {{Yes/No}} |
|
||||
|
||||
### SWOT Comparison
|
||||
|
||||
[[LLM: Create SWOT analysis for your solution vs. top competitors]]
|
||||
|
||||
#### Your Solution
|
||||
- **Strengths:** {{List key strengths}}
|
||||
- **Weaknesses:** {{List key weaknesses}}
|
||||
- **Opportunities:** {{List opportunities}}
|
||||
- **Threats:** {{List threats}}
|
||||
|
||||
#### vs. {{Main Competitor}}
|
||||
- **Competitive Advantages:** {{Where you're stronger}}
|
||||
- **Competitive Disadvantages:** {{Where they're stronger}}
|
||||
- **Differentiation Opportunities:** {{How to stand out}}
|
||||
|
||||
### Positioning Map
|
||||
|
||||
[[LLM: Describe competitor positions on key dimensions]]
|
||||
|
||||
{{Create a positioning description using 2 key dimensions relevant to the market, such as:
|
||||
- Price vs. Features
|
||||
- Ease of Use vs. Power
|
||||
- Specialization vs. Breadth
|
||||
- Self-Serve vs. High-Touch}}
|
||||
|
||||
## Strategic Analysis
|
||||
|
||||
### Competitive Advantages Assessment
|
||||
|
||||
#### Sustainable Advantages
|
||||
{{Identify moats and defensible positions:
|
||||
- Network effects
|
||||
- Switching costs
|
||||
- Brand strength
|
||||
- Technology barriers
|
||||
- Regulatory advantages}}
|
||||
|
||||
#### Vulnerable Points
|
||||
{{Where competitors could be challenged:
|
||||
- Weak customer segments
|
||||
- Missing features
|
||||
- Poor user experience
|
||||
- High prices
|
||||
- Limited geographic presence}}
|
||||
|
||||
### Blue Ocean Opportunities
|
||||
|
||||
[[LLM: Identify uncontested market spaces]]
|
||||
|
||||
{{List opportunities to create new market space:
|
||||
- Underserved segments
|
||||
- Unaddressed use cases
|
||||
- New business models
|
||||
- Geographic expansion
|
||||
- Different value propositions}}
|
||||
|
||||
## Strategic Recommendations
|
||||
|
||||
### Differentiation Strategy
|
||||
{{How to position against competitors:
|
||||
- Unique value propositions to emphasize
|
||||
- Features to prioritize
|
||||
- Segments to target
|
||||
- Messaging and positioning}}
|
||||
|
||||
### Competitive Response Planning
|
||||
|
||||
#### Offensive Strategies
|
||||
{{How to gain market share:
|
||||
- Target competitor weaknesses
|
||||
- Win competitive deals
|
||||
- Capture their customers}}
|
||||
|
||||
#### Defensive Strategies
|
||||
{{How to protect your position:
|
||||
- Strengthen vulnerable areas
|
||||
- Build switching costs
|
||||
- Deepen customer relationships}}
|
||||
|
||||
### Partnership & Ecosystem Strategy
|
||||
{{Potential collaboration opportunities:
|
||||
- Complementary players
|
||||
- Channel partners
|
||||
- Technology integrations
|
||||
- Strategic alliances}}
|
||||
|
||||
## Monitoring & Intelligence Plan
|
||||
|
||||
### Key Competitors to Track
|
||||
{{Priority list with rationale}}
|
||||
|
||||
### Monitoring Metrics
|
||||
{{What to track:
|
||||
- Product updates
|
||||
- Pricing changes
|
||||
- Customer wins/losses
|
||||
- Funding/M&A activity
|
||||
- Market messaging}}
|
||||
|
||||
### Intelligence Sources
|
||||
{{Where to gather ongoing intelligence:
|
||||
- Company websites/blogs
|
||||
- Customer reviews
|
||||
- Industry reports
|
||||
- Social media
|
||||
- Patent filings}}
|
||||
|
||||
### Update Cadence
|
||||
{{Recommended review schedule:
|
||||
- Weekly: {{What to check}}
|
||||
- Monthly: {{What to review}}
|
||||
- Quarterly: {{Deep analysis}}}}
|
||||
|
||||
---
|
||||
|
||||
[[LLM: After completing the document, offer advanced elicitation with these custom options for competitive analysis:
|
||||
|
||||
**Competitive Analysis Elicitation Actions**
|
||||
0. Deep dive on a specific competitor's strategy
|
||||
1. Analyze competitive dynamics in a specific segment
|
||||
2. War game competitive responses to your moves
|
||||
3. Explore partnership vs. competition scenarios
|
||||
4. Stress test differentiation claims
|
||||
5. Analyze disruption potential (yours or theirs)
|
||||
6. Compare to competition in adjacent markets
|
||||
7. Generate win/loss analysis insights
|
||||
8. If only we had known about [competitor X's plan]...
|
||||
9. Proceed to next section
|
||||
|
||||
These replace the standard elicitation options when working on competitive analysis documents.]]
|
||||
219
bmad-core/templates/market-research-tmpl.md
Normal file
219
bmad-core/templates/market-research-tmpl.md
Normal file
@@ -0,0 +1,219 @@
|
||||
# Market Research Report: {{Project/Product Name}}
|
||||
|
||||
[[LLM: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.]]
|
||||
|
||||
## Executive Summary
|
||||
|
||||
{{Provide a high-level overview of key findings, market opportunity assessment, and strategic recommendations. Write this section LAST after completing all other sections.}}
|
||||
|
||||
## Research Objectives & Methodology
|
||||
|
||||
### Research Objectives
|
||||
{{List the primary objectives of this market research:
|
||||
- What decisions will this research inform?
|
||||
- What specific questions need to be answered?
|
||||
- What are the success criteria for this research?}}
|
||||
|
||||
### Research Methodology
|
||||
{{Describe the research approach:
|
||||
- Data sources used (primary/secondary)
|
||||
- Analysis frameworks applied
|
||||
- Data collection timeframe
|
||||
- Limitations and assumptions}}
|
||||
|
||||
## Market Overview
|
||||
|
||||
### Market Definition
|
||||
{{Define the market being analyzed:
|
||||
- Product/service category
|
||||
- Geographic scope
|
||||
- Customer segments included
|
||||
- Value chain position}}
|
||||
|
||||
### Market Size & Growth
|
||||
|
||||
[[LLM: Guide through TAM, SAM, SOM calculations with clear assumptions. Use one or more approaches:
|
||||
- Top-down: Start with industry data, narrow down
|
||||
- Bottom-up: Build from customer/unit economics
|
||||
- Value theory: Based on value provided vs. alternatives]]
|
||||
|
||||
#### Total Addressable Market (TAM)
|
||||
{{Calculate and explain the total market opportunity}}
|
||||
|
||||
#### Serviceable Addressable Market (SAM)
|
||||
{{Define the portion of TAM you can realistically reach}}
|
||||
|
||||
#### Serviceable Obtainable Market (SOM)
|
||||
{{Estimate the portion you can realistically capture}}
|
||||
|
||||
### Market Trends & Drivers
|
||||
|
||||
[[LLM: Analyze key trends shaping the market using appropriate frameworks like PESTEL]]
|
||||
|
||||
#### Key Market Trends
|
||||
{{List and explain 3-5 major trends:
|
||||
- Trend 1: Description and impact
|
||||
- Trend 2: Description and impact
|
||||
- etc.}}
|
||||
|
||||
#### Growth Drivers
|
||||
{{Identify primary factors driving market growth}}
|
||||
|
||||
#### Market Inhibitors
|
||||
{{Identify factors constraining market growth}}
|
||||
|
||||
## Customer Analysis
|
||||
|
||||
### Target Segment Profiles
|
||||
|
||||
[[LLM: For each segment, create detailed profiles including demographics/firmographics, psychographics, behaviors, needs, and willingness to pay]]
|
||||
|
||||
#### Segment 1: {{Segment Name}}
|
||||
- **Description:** {{Brief overview}}
|
||||
- **Size:** {{Number of customers/market value}}
|
||||
- **Characteristics:** {{Key demographics/firmographics}}
|
||||
- **Needs & Pain Points:** {{Primary problems they face}}
|
||||
- **Buying Process:** {{How they make purchasing decisions}}
|
||||
- **Willingness to Pay:** {{Price sensitivity and value perception}}
|
||||
|
||||
<<REPEAT for each additional segment>>
|
||||
|
||||
### Jobs-to-be-Done Analysis
|
||||
|
||||
[[LLM: Uncover what customers are really trying to accomplish]]
|
||||
|
||||
#### Functional Jobs
|
||||
{{List practical tasks and objectives customers need to complete}}
|
||||
|
||||
#### Emotional Jobs
|
||||
{{Describe feelings and perceptions customers seek}}
|
||||
|
||||
#### Social Jobs
|
||||
{{Explain how customers want to be perceived by others}}
|
||||
|
||||
### Customer Journey Mapping
|
||||
|
||||
[[LLM: Map the end-to-end customer experience for primary segments]]
|
||||
|
||||
{{For primary customer segment:
|
||||
1. **Awareness:** How they discover solutions
|
||||
2. **Consideration:** Evaluation criteria and process
|
||||
3. **Purchase:** Decision triggers and barriers
|
||||
4. **Onboarding:** Initial experience expectations
|
||||
5. **Usage:** Ongoing interaction patterns
|
||||
6. **Advocacy:** Referral and expansion behaviors}}
|
||||
|
||||
## Competitive Landscape
|
||||
|
||||
### Market Structure
|
||||
{{Describe the overall competitive environment:
|
||||
- Number of competitors
|
||||
- Market concentration
|
||||
- Competitive intensity}}
|
||||
|
||||
### Major Players Analysis
|
||||
{{For top 3-5 competitors:
|
||||
- Company name and brief description
|
||||
- Market share estimate
|
||||
- Key strengths and weaknesses
|
||||
- Target customer focus
|
||||
- Pricing strategy}}
|
||||
|
||||
### Competitive Positioning
|
||||
{{Analyze how competitors are positioned:
|
||||
- Value propositions
|
||||
- Differentiation strategies
|
||||
- Market gaps and opportunities}}
|
||||
|
||||
## Industry Analysis
|
||||
|
||||
### Porter's Five Forces Assessment
|
||||
|
||||
[[LLM: Analyze each force with specific evidence and implications]]
|
||||
|
||||
#### Supplier Power: {{Low/Medium/High}}
|
||||
{{Analysis and implications}}
|
||||
|
||||
#### Buyer Power: {{Low/Medium/High}}
|
||||
{{Analysis and implications}}
|
||||
|
||||
#### Competitive Rivalry: {{Low/Medium/High}}
|
||||
{{Analysis and implications}}
|
||||
|
||||
#### Threat of New Entry: {{Low/Medium/High}}
|
||||
{{Analysis and implications}}
|
||||
|
||||
#### Threat of Substitutes: {{Low/Medium/High}}
|
||||
{{Analysis and implications}}
|
||||
|
||||
### Technology Adoption Lifecycle Stage
|
||||
{{Identify where the market is in the adoption curve:
|
||||
- Current stage and evidence
|
||||
- Implications for strategy
|
||||
- Expected progression timeline}}
|
||||
|
||||
## Opportunity Assessment
|
||||
|
||||
### Market Opportunities
|
||||
|
||||
[[LLM: Identify specific opportunities based on the analysis]]
|
||||
|
||||
#### Opportunity 1: {{Name}}
|
||||
- **Description:** {{What is the opportunity?}}
|
||||
- **Size/Potential:** {{Quantify if possible}}
|
||||
- **Requirements:** {{What's needed to capture it?}}
|
||||
- **Risks:** {{Key challenges or barriers}}
|
||||
|
||||
<<REPEAT for additional opportunities>>
|
||||
|
||||
### Strategic Recommendations
|
||||
|
||||
#### Go-to-Market Strategy
|
||||
{{Recommend approach for market entry/expansion:
|
||||
- Target segment prioritization
|
||||
- Positioning strategy
|
||||
- Channel strategy
|
||||
- Partnership opportunities}}
|
||||
|
||||
#### Pricing Strategy
|
||||
{{Based on willingness to pay analysis and competitive landscape:
|
||||
- Recommended pricing model
|
||||
- Price points/ranges
|
||||
- Value metric
|
||||
- Competitive positioning}}
|
||||
|
||||
#### Risk Mitigation
|
||||
{{Key risks and mitigation strategies:
|
||||
- Market risks
|
||||
- Competitive risks
|
||||
- Execution risks
|
||||
- Regulatory/compliance risks}}
|
||||
|
||||
## Appendices
|
||||
|
||||
### A. Data Sources
|
||||
{{List all sources used in the research}}
|
||||
|
||||
### B. Detailed Calculations
|
||||
{{Include any complex calculations or models}}
|
||||
|
||||
### C. Additional Analysis
|
||||
{{Any supplementary analysis not included in main body}}
|
||||
|
||||
---
|
||||
|
||||
[[LLM: After completing the document, offer advanced elicitation with these custom options for market research:
|
||||
|
||||
**Market Research Elicitation Actions**
|
||||
0. Expand market sizing calculations with sensitivity analysis
|
||||
1. Deep dive into a specific customer segment
|
||||
2. Analyze an emerging market trend in detail
|
||||
3. Compare this market to an analogous market
|
||||
4. Stress test market assumptions
|
||||
5. Explore adjacent market opportunities
|
||||
6. Challenge market definition and boundaries
|
||||
7. Generate strategic scenarios (best/base/worst case)
|
||||
8. If only we had considered [X market factor]...
|
||||
9. Proceed to next section
|
||||
|
||||
These replace the standard elicitation options when working on market research documents.]]
|
||||
@@ -1,53 +1,199 @@
|
||||
# Project Brief: {Project Name}
|
||||
# Project Brief: {{Project Name}}
|
||||
|
||||
## Introduction / Problem Statement
|
||||
[[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
|
||||
|
||||
{Describe the core idea, the problem being solved, or the opportunity being addressed. Why is this project needed?}
|
||||
Start by asking the user which mode they prefer:
|
||||
1. **Interactive Mode** - Work through each section collaboratively
|
||||
2. **YOLO Mode** - Generate complete draft for review and refinement
|
||||
|
||||
## Vision & Goals
|
||||
Before beginning, understand what inputs are available (brainstorming results, market research, competitive analysis, initial ideas) and gather project context.]]
|
||||
|
||||
- **Vision:** {Describe the high-level desired future state or impact of this project.}
|
||||
- **Primary Goals:** {List 2-5 specific, measurable, achievable, relevant, time-bound (SMART) goals for the Minimum Viable Product (MVP).}
|
||||
- Goal 1: ...
|
||||
- Goal 2: ...
|
||||
- **Success Metrics (Initial Ideas):** {How will we measure if the project/MVP is successful? List potential KPIs.}
|
||||
## Executive Summary
|
||||
|
||||
## Target Audience / Users
|
||||
[[LLM: Create a concise overview that captures the essence of the project. Include:
|
||||
- Product concept in 1-2 sentences
|
||||
- Primary problem being solved
|
||||
- Target market identification
|
||||
- Key value proposition]]
|
||||
|
||||
{Describe the primary users of this product/system. Who are they? What are their key characteristics or needs relevant to this project?}
|
||||
{{Write executive summary based on information gathered}}
|
||||
|
||||
## Key Features / Scope (High-Level Ideas for MVP)
|
||||
## Problem Statement
|
||||
|
||||
{List the core functionalities or features envisioned for the MVP. Keep this high-level; details will go in the PRD/Epics.}
|
||||
[[LLM: Articulate the problem with clarity and evidence. Address:
|
||||
- Current state and pain points
|
||||
- Impact of the problem (quantify if possible)
|
||||
- Why existing solutions fall short
|
||||
- Urgency and importance of solving this now]]
|
||||
|
||||
- Feature Idea 1: ...
|
||||
- Feature Idea 2: ...
|
||||
- Feature Idea N: ...
|
||||
{{Detailed problem description with supporting evidence}}
|
||||
|
||||
## Post MVP Features / Scope and Ideas
|
||||
## Proposed Solution
|
||||
|
||||
{List the core functionalities or features envisioned as potential for POST MVP. Keep this high-level; details will go in the PRD/Epics/Architecture.}
|
||||
[[LLM: Describe the solution approach at a high level. Include:
|
||||
- Core concept and approach
|
||||
- Key differentiators from existing solutions
|
||||
- Why this solution will succeed where others haven't
|
||||
- High-level vision for the product]]
|
||||
|
||||
- Feature Idea 1: ...
|
||||
- Feature Idea 2: ...
|
||||
- Feature Idea N: ...
|
||||
{{Solution description focusing on the "what" and "why", not implementation details}}
|
||||
|
||||
## Known Technical Constraints or Preferences
|
||||
## Target Users
|
||||
|
||||
- **Constraints:** {List any known limitations and technical mandates or preferences - e.g., budget, timeline, specific technology mandates, required integrations, compliance needs.}
|
||||
- **Initial Architectural Preferences (if any):** {Capture any early thoughts or strong preferences regarding repository structure (e.g., monorepo, polyrepo) and overall service architecture (e.g., monolith, microservices, serverless components). This is not a final decision point but for initial awareness.}
|
||||
- **Risks:** {Identify potential risks - e.g., technical challenges, resource availability, market acceptance, dependencies.}
|
||||
- **User Preferences:** {Any specific requests from the user that are not a high level feature that could direct technology or library choices, or anything else that came up in the brainstorming or drafting of the PRD that is not included in prior document sections}
|
||||
[[LLM: Define and characterize the intended users with specificity. For each user segment include:
|
||||
- Demographic/firmographic profile
|
||||
- Current behaviors and workflows
|
||||
- Specific needs and pain points
|
||||
- Goals they're trying to achieve]]
|
||||
|
||||
## Relevant Research (Optional)
|
||||
### Primary User Segment: {{Segment Name}}
|
||||
{{Detailed description of primary users}}
|
||||
|
||||
{Link to or summarize findings from any initial research conducted (e.g., `deep-research-report-BA.md`).}
|
||||
### Secondary User Segment: {{Segment Name}}
|
||||
{{Description of secondary users if applicable}}
|
||||
|
||||
## Goals & Success Metrics
|
||||
|
||||
[[LLM: Establish clear objectives and how to measure success. Make goals SMART (Specific, Measurable, Achievable, Relevant, Time-bound)]]
|
||||
|
||||
### Business Objectives
|
||||
- {{Objective 1 with metric}}
|
||||
- {{Objective 2 with metric}}
|
||||
- {{Objective 3 with metric}}
|
||||
|
||||
### User Success Metrics
|
||||
- {{How users will measure value}}
|
||||
- {{Engagement metrics}}
|
||||
- {{Satisfaction indicators}}
|
||||
|
||||
### Key Performance Indicators (KPIs)
|
||||
- {{KPI 1: Definition and target}}
|
||||
- {{KPI 2: Definition and target}}
|
||||
- {{KPI 3: Definition and target}}
|
||||
|
||||
## MVP Scope
|
||||
|
||||
[[LLM: Define the minimum viable product clearly. Be specific about what's in and what's out. Help user distinguish must-haves from nice-to-haves.]]
|
||||
|
||||
### Core Features (Must Have)
|
||||
- **Feature 1:** {{Brief description and why it's essential}}
|
||||
- **Feature 2:** {{Brief description and why it's essential}}
|
||||
- **Feature 3:** {{Brief description and why it's essential}}
|
||||
|
||||
### Out of Scope for MVP
|
||||
- {{Feature/capability explicitly not in MVP}}
|
||||
- {{Feature/capability to be considered post-MVP}}
|
||||
|
||||
### MVP Success Criteria
|
||||
{{Define what constitutes a successful MVP launch}}
|
||||
|
||||
## Post-MVP Vision
|
||||
|
||||
[[LLM: Outline the longer-term product direction without overcommitting to specifics]]
|
||||
|
||||
### Phase 2 Features
|
||||
{{Next priority features after MVP success}}
|
||||
|
||||
### Long-term Vision
|
||||
{{Where this product could go in 1-2 years}}
|
||||
|
||||
### Expansion Opportunities
|
||||
{{Potential new markets, use cases, or integrations}}
|
||||
|
||||
## Technical Considerations
|
||||
|
||||
[[LLM: Document known technical constraints and preferences. Note these are initial thoughts, not final decisions.]]
|
||||
|
||||
### Platform Requirements
|
||||
- **Target Platforms:** {{Web, mobile, desktop, etc.}}
|
||||
- **Browser/OS Support:** {{Specific requirements}}
|
||||
- **Performance Requirements:** {{Load times, concurrent users, etc.}}
|
||||
|
||||
### Technology Preferences
|
||||
- **Frontend:** {{If any preferences exist}}
|
||||
- **Backend:** {{If any preferences exist}}
|
||||
- **Database:** {{If any preferences exist}}
|
||||
- **Hosting/Infrastructure:** {{Cloud preferences, on-prem requirements}}
|
||||
|
||||
### Architecture Considerations
|
||||
- **Repository Structure:** {{Initial thoughts on monorepo vs. polyrepo}}
|
||||
- **Service Architecture:** {{Initial thoughts on monolith vs. microservices}}
|
||||
- **Integration Requirements:** {{Third-party services, APIs}}
|
||||
- **Security/Compliance:** {{Any specific requirements}}
|
||||
|
||||
## Constraints & Assumptions
|
||||
|
||||
[[LLM: Clearly state limitations and assumptions to set realistic expectations]]
|
||||
|
||||
### Constraints
|
||||
- **Budget:** {{If known}}
|
||||
- **Timeline:** {{Target launch date or development timeframe}}
|
||||
- **Resources:** {{Team size, skill constraints}}
|
||||
- **Technical:** {{Legacy systems, required tech stack}}
|
||||
|
||||
### Key Assumptions
|
||||
- {{Assumption about users, market, or technology}}
|
||||
- {{Assumption about resources or support}}
|
||||
- {{Assumption about external dependencies}}
|
||||
|
||||
## Risks & Open Questions
|
||||
|
||||
[[LLM: Identify unknowns and potential challenges proactively]]
|
||||
|
||||
### Key Risks
|
||||
- **Risk 1:** {{Description and potential impact}}
|
||||
- **Risk 2:** {{Description and potential impact}}
|
||||
- **Risk 3:** {{Description and potential impact}}
|
||||
|
||||
### Open Questions
|
||||
- {{Question needing research or decision}}
|
||||
- {{Question about technical approach}}
|
||||
- {{Question about market or users}}
|
||||
|
||||
### Areas Needing Further Research
|
||||
- {{Topic requiring deeper investigation}}
|
||||
- {{Validation needed before proceeding}}
|
||||
|
||||
## Appendices
|
||||
|
||||
### A. Research Summary
|
||||
{{If applicable, summarize key findings from:
|
||||
- Market research
|
||||
- Competitive analysis
|
||||
- User interviews
|
||||
- Technical feasibility studies}}
|
||||
|
||||
### B. Stakeholder Input
|
||||
{{Key feedback or requirements from stakeholders}}
|
||||
|
||||
### C. References
|
||||
{{Links to relevant documents, research, or examples}}
|
||||
|
||||
## Next Steps
|
||||
|
||||
### PM Prompt
|
||||
### Immediate Actions
|
||||
1. {{First concrete next step}}
|
||||
2. {{Second concrete next step}}
|
||||
3. {{Third concrete next step}}
|
||||
|
||||
This Project Brief provides the full context for {Project Name}. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section as the template indicates, asking for any necessary clarification or suggesting improvements as your mode 1 programming allows.
|
||||
### PM Handoff
|
||||
|
||||
<example_handoff_prompt>
|
||||
This Project Brief provides the full context for Mealmate. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section 1 at a time, asking for any necessary clarification or suggesting improvements as your mode 1 programming allows.</example_handoff_prompt>
|
||||
This Project Brief provides the full context for {{Project Name}}. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section as the template indicates, asking for any necessary clarification or suggesting improvements.
|
||||
|
||||
---
|
||||
|
||||
[[LLM: After completing each major section (not subsections), offer advanced elicitation with these custom options for project briefs:
|
||||
|
||||
**Project Brief Elicitation Actions**
|
||||
0. Expand section with more specific details
|
||||
1. Validate against similar successful products
|
||||
2. Stress test assumptions with edge cases
|
||||
3. Explore alternative solution approaches
|
||||
4. Analyze resource/constraint trade-offs
|
||||
5. Generate risk mitigation strategies
|
||||
6. Challenge scope from MVP minimalist view
|
||||
7. Brainstorm creative feature possibilities
|
||||
8. If only we had [resource/capability/time]...
|
||||
9. Proceed to next section
|
||||
|
||||
These replace the standard elicitation options when working on project brief documents.]]
|
||||
|
||||
Reference in New Issue
Block a user