cursor, correted roo, and windsurf rules readded and will update on project build

.bmad-core/agents/bmad-master.md

@@ -67,7 +67,7 @@ dependencies:
     - index-docs
     - shard-doc
   templates:
-    - agent-tmplv2
+    - agent-tmpl
     - architecture-tmpl
     - brownfield-architecture-tmpl
     - brownfield-prd-tmpl

.bmad-core/web-bundles/agents/analyst.txt

@@ -7,27 +7,30 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
-   - `==================== START: folder#filename ====================`
-   - `==================== END: folder#filename ====================`
+
+- `==================== START: folder#filename ====================`
+- `==================== END: folder#filename ====================`
 
 When you need to reference a resource mentioned in your instructions:
-   - Look for the corresponding START/END tags
-   - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
-   - If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
+- Look for the corresponding START/END tags
+- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
+- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   ```yaml
-   dependencies:
-     utils:
-       - template-format
-     tasks:
-       - create-story
-   ```
+**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
 
-   These references map directly to bundle sections:
-   - `utils: template-format` → Look for `==================== START: utils#template-format ====================`
-   - `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
+```yaml
+dependencies:
+  utils:
+    - template-format
+  tasks:
+    - create-story
+```
+
+These references map directly to bundle sections:
+
+- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
+- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -51,6 +54,8 @@ agent:
   name: Mary
   id: analyst
   title: Business Analyst
+  icon: 📊
+  whenToUse: "Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery"
   customization:
 
 persona:
@@ -157,7 +162,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 
 #### Structured Ideation Frameworks
 
-5. **SCAMPER Method**
+1. **SCAMPER Method**
    [[LLM: Guide through each SCAMPER prompt systematically.]]
    - **S** = Substitute: What can be substituted?
    - **C** = Combine: What can be combined or integrated?
@@ -165,9 +170,9 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
    - **M** = Modify/Magnify: What can be emphasized or reduced?
    - **P** = Put to other uses: What else could this be used for?
    - **E** = Eliminate: What can be removed or simplified?
-   - **R** = Reverse/Rearrange: What can be reversed or reordered?
+   - **R**= Reverse/Rearrange: What can be reversed or reordered?
 
-6. **Six Thinking Hats**
+2. **Six Thinking Hats**
    [[LLM: Cycle through different thinking modes, spending focused time in each.]]
    - White Hat: Facts and information
    - Red Hat: Emotions and intuition
@@ -176,10 +181,10 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
    - Green Hat: Creativity and alternatives
    - Blue Hat: Process and control
 
-7. **Mind Mapping**
+3. **Mind Mapping**
    [[LLM: Create text-based mind maps with clear hierarchical structure.]]
 
-   ```text
+   ```plaintext
    Central Concept
    ├── Branch 1
    │   ├── Sub-idea 1.1
@@ -193,21 +198,21 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 
 #### Collaborative Techniques
 
-8. **"Yes, And..." Building**
+1. **"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**
+2. **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**
+3. **Random Stimulation**
     [[LLM: Use random words, images, or concepts as creative triggers.]]
     - Random word association
     - Picture/metaphor inspiration
@@ -216,21 +221,21 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 
 #### Deep Exploration Techniques
 
-11. **Five Whys**
+1. **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**
+2. **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)**
+3. **Provocation Technique (PO)**
     [[LLM: Make deliberately provocative statements to jar thinking.]]
     - PO: Cars have square wheels
     - PO: Customers pay us to take products
@@ -242,26 +247,31 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 [[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
@@ -295,17 +305,20 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 [[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
@@ -511,7 +524,7 @@ Present these numbered options to the user:
 
 **Research Prompt Template:**
 
-```
+```markdown
 ## Research Objective
 [Clear statement of what this research aims to achieve]
 
@@ -791,6 +804,7 @@ Choose an action (0-9 - 9 to bypass - HELP for explanation of these options):
 [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
 
 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
 
@@ -799,6 +813,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
 ## Executive Summary
 
 [[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
@@ -809,6 +824,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
 ## Problem Statement
 
 [[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
@@ -819,6 +835,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
 ## Proposed Solution
 
 [[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
@@ -829,15 +846,18 @@ Before beginning, understand what inputs are available (brainstorming results, m
 ## Target Users
 
 [[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]]
 
 ### Primary User Segment: {{Segment Name}}
+
 {{Detailed description of primary users}}
 
 ### Secondary User Segment: {{Segment Name}}
+
 {{Description of secondary users if applicable}}
 
 ## Goals & Success Metrics
@@ -845,16 +865,19 @@ Before beginning, understand what inputs are available (brainstorming results, m
 [[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}}
@@ -864,15 +887,18 @@ Before beginning, understand what inputs are available (brainstorming results, m
 [[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
@@ -880,12 +906,15 @@ Before beginning, understand what inputs are available (brainstorming results, m
 [[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
@@ -893,17 +922,20 @@ Before beginning, understand what inputs are available (brainstorming results, m
 [[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}}
@@ -914,12 +946,14 @@ Before beginning, understand what inputs are available (brainstorming results, m
 [[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}}
@@ -929,37 +963,45 @@ Before beginning, understand what inputs are available (brainstorming results, m
 [[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
 
 ### Immediate Actions
+
 1. {{First concrete next step}}
 2. {{Second concrete next step}}
 3. {{Third concrete next step}}
@@ -972,8 +1014,8 @@ This Project Brief provides the full context for {{Project Name}}. Please start
 
 [[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
+**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
@@ -999,13 +1041,17 @@ These replace the standard elicitation options when working on project brief doc
 ## 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
@@ -1014,7 +1060,9 @@ These replace the standard elicitation options when working on project brief doc
 ## Market Overview
 
 ### Market Definition
+
 {{Define the market being analyzed:
+
 - Product/service category
 - Geographic scope
 - Customer segments included
@@ -1023,17 +1071,21 @@ These replace the standard elicitation options when working on project brief doc
 ### 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
@@ -1041,15 +1093,19 @@ These replace the standard elicitation options when working on project brief doc
 [[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
@@ -1059,6 +1115,7 @@ These replace the standard elicitation options when working on project brief doc
 [[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}}
@@ -1073,12 +1130,15 @@ These replace the standard elicitation options when working on project brief doc
 [[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
@@ -1086,6 +1146,7 @@ These replace the standard elicitation options when working on project brief doc
 [[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
@@ -1096,13 +1157,17 @@ These replace the standard elicitation options when working on project brief doc
 ## 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
@@ -1110,7 +1175,9 @@ These replace the standard elicitation options when working on project brief doc
 - Pricing strategy}}
 
 ### Competitive Positioning
+
 {{Analyze how competitors are positioned:
+
 - Value propositions
 - Differentiation strategies
 - Market gaps and opportunities}}
@@ -1122,22 +1189,29 @@ These replace the standard elicitation options when working on project brief doc
 [[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}}
@@ -1149,6 +1223,7 @@ These replace the standard elicitation options when working on project brief doc
 [[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?}}
@@ -1159,21 +1234,27 @@ These replace the standard elicitation options when working on project brief doc
 ### 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
@@ -1182,20 +1263,23 @@ These replace the standard elicitation options when working on project brief doc
 ## 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
+**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
@@ -1221,7 +1305,9 @@ These replace the standard elicitation options when working on market research d
 ## Analysis Scope & Methodology
 
 ### Analysis Purpose
+
 {{Define the primary purpose:
+
 - New market entry assessment
 - Product positioning strategy
 - Feature gap analysis
@@ -1230,7 +1316,9 @@ These replace the standard elicitation options when working on market research d
 - 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
@@ -1238,7 +1326,9 @@ These replace the standard elicitation options when working on market research d
 - Aspirational Competitors: Best-in-class examples}}
 
 ### Research Methodology
+
 {{Describe approach:
+
 - Information sources used
 - Analysis timeframe
 - Confidence levels
@@ -1247,7 +1337,9 @@ These replace the standard elicitation options when working on market research d
 ## Competitive Landscape Overview
 
 ### Market Structure
+
 {{Describe the competitive environment:
+
 - Number of active competitors
 - Market concentration (fragmented/consolidated)
 - Competitive dynamics
@@ -1258,6 +1350,7 @@ These replace the standard elicitation options when working on market research d
 [[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
@@ -1270,6 +1363,7 @@ These replace the standard elicitation options when working on market research d
 ### {{Competitor Name}} - Priority {{1/2/3/4}}
 
 #### Company Overview
+
 - **Founded:** {{Year, founders}}
 - **Headquarters:** {{Location}}
 - **Company Size:** {{Employees, revenue if known}}
@@ -1277,6 +1371,7 @@ These replace the standard elicitation options when working on market research d
 - **Leadership:** {{Key executives}}
 
 #### Business Model & Strategy
+
 - **Revenue Model:** {{How they make money}}
 - **Target Market:** {{Primary customer segments}}
 - **Value Proposition:** {{Core value promise}}
@@ -1284,6 +1379,7 @@ These replace the standard elicitation options when working on market research d
 - **Strategic Focus:** {{Current priorities}}
 
 #### Product/Service Analysis
+
 - **Core Offerings:** {{Main products/services}}
 - **Key Features:** {{Standout capabilities}}
 - **User Experience:** {{UX strengths/weaknesses}}
@@ -1293,16 +1389,19 @@ These replace the standard elicitation options when working on market research d
 #### 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}}
@@ -1316,32 +1415,34 @@ These replace the standard elicitation options when working on market research d
 
 [[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}} |
+| 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}} |
+| 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}}
@@ -1351,6 +1452,7 @@ These replace the standard elicitation options when working on market research d
 [[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
@@ -1361,7 +1463,9 @@ These replace the standard elicitation options when working on market research d
 ### Competitive Advantages Assessment
 
 #### Sustainable Advantages
+
 {{Identify moats and defensible positions:
+
 - Network effects
 - Switching costs
 - Brand strength
@@ -1369,7 +1473,9 @@ These replace the standard elicitation options when working on market research d
 - Regulatory advantages}}
 
 #### Vulnerable Points
+
 {{Where competitors could be challenged:
+
 - Weak customer segments
 - Missing features
 - Poor user experience
@@ -1381,6 +1487,7 @@ These replace the standard elicitation options when working on market research d
 [[LLM: Identify uncontested market spaces]]
 
 {{List opportunities to create new market space:
+
 - Underserved segments
 - Unaddressed use cases
 - New business models
@@ -1390,7 +1497,9 @@ These replace the standard elicitation options when working on market research d
 ## Strategic Recommendations
 
 ### Differentiation Strategy
+
 {{How to position against competitors:
+
 - Unique value propositions to emphasize
 - Features to prioritize
 - Segments to target
@@ -1399,19 +1508,25 @@ These replace the standard elicitation options when working on market research d
 ### 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
@@ -1420,10 +1535,13 @@ These replace the standard elicitation options when working on market research d
 ## Monitoring & Intelligence Plan
 
 ### Key Competitors to Track
+
 {{Priority list with rationale}}
 
 ### Monitoring Metrics
+
 {{What to track:
+
 - Product updates
 - Pricing changes
 - Customer wins/losses
@@ -1431,7 +1549,9 @@ These replace the standard elicitation options when working on market research d
 - Market messaging}}
 
 ### Intelligence Sources
+
 {{Where to gather ongoing intelligence:
+
 - Company websites/blogs
 - Customer reviews
 - Industry reports
@@ -1439,7 +1559,9 @@ These replace the standard elicitation options when working on market research d
 - Patent filings}}
 
 ### Update Cadence
+
 {{Recommended review schedule:
+
 - Weekly: {{What to check}}
 - Monthly: {{What to review}}
 - Quarterly: {{Deep analysis}}}}
@@ -1448,8 +1570,8 @@ These replace the standard elicitation options when working on market research d
 
 [[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
+**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
@@ -1511,7 +1633,7 @@ Templates in the BMAD method use standardized markup for AI processing. These co
 
 - **{{placeholders}}**: Variables to be replaced with actual content
 - **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **<<REPEAT>>** sections: Content blocks that may be repeated as needed
+- **REPEAT** sections: Content blocks that may be repeated as needed
 - **^^CONDITION^^** blocks: Conditional content included only if criteria are met
 - **@{examples}**: Example content for guidance (never output to users)
 

.bmad-core/web-bundles/agents/architect.txt

@@ -7,27 +7,30 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
-   - `==================== START: folder#filename ====================`
-   - `==================== END: folder#filename ====================`
+
+- `==================== START: folder#filename ====================`
+- `==================== END: folder#filename ====================`
 
 When you need to reference a resource mentioned in your instructions:
-   - Look for the corresponding START/END tags
-   - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
-   - If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
+- Look for the corresponding START/END tags
+- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
+- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   ```yaml
-   dependencies:
-     utils:
-       - template-format
-     tasks:
-       - create-story
-   ```
+**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
 
-   These references map directly to bundle sections:
-   - `utils: template-format` → Look for `==================== START: utils#template-format ====================`
-   - `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
+```yaml
+dependencies:
+  utils:
+    - template-format
+  tasks:
+    - create-story
+```
+
+These references map directly to bundle sections:
+
+- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
+- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -51,6 +54,8 @@ agent:
   name: Winston
   id: architect
   title: Architect
+  icon: 🏗️
+  whenToUse: "Use for system design, architecture documents, technology selection, API design, and infrastructure planning"
   customization:
 
 persona:
@@ -469,7 +474,7 @@ Present these numbered options to the user:
 
 **Research Prompt Template:**
 
-```
+```markdown
 ## Research Objective
 [Clear statement of what this research aims to achieve]
 
@@ -593,34 +598,35 @@ If the project includes a significant user interface, a separate Frontend Archit
 
 1. Review the PRD and brainstorming brief for any mentions of:
 
-   - Starter templates (e.g., Create React App, Next.js, Vue CLI, Angular CLI, etc.)
-   - Existing projects or codebases being used as a foundation
-   - Boilerplate projects or scaffolding tools
-   - Previous projects to be cloned or adapted
+- Starter templates (e.g., Create React App, Next.js, Vue CLI, Angular CLI, etc.)
+- Existing projects or codebases being used as a foundation
+- Boilerplate projects or scaffolding tools
+- Previous projects to be cloned or adapted
 
 2. If a starter template or existing project is mentioned:
 
-   - Ask the user to provide access via one of these methods:
-     - Link to the starter template documentation
-     - Upload/attach the project files (for small projects)
-     - Share a link to the project repository (GitHub, GitLab, etc.)
-   - Analyze the starter/existing project to understand:
-     - Pre-configured technology stack and versions
-     - Project structure and organization patterns
-     - Built-in scripts and tooling
-     - Existing architectural patterns and conventions
-     - Any limitations or constraints imposed by the starter
-   - Use this analysis to inform and align your architecture decisions
+- Ask the user to provide access via one of these methods:
+  - Link to the starter template documentation
+  - Upload/attach the project files (for small projects)
+  - Share a link to the project repository (GitHub, GitLab, etc.)
+- Analyze the starter/existing project to understand:
+  - Pre-configured technology stack and versions
+  - Project structure and organization patterns
+  - Built-in scripts and tooling
+  - Existing architectural patterns and conventions
+  - Any limitations or constraints imposed by the starter
+- Use this analysis to inform and align your architecture decisions
 
 3. If no starter template is mentioned but this is a greenfield project:
 
-   - Suggest appropriate starter templates based on the tech stack preferences
-   - Explain the benefits (faster setup, best practices, community support)
-   - Let the user decide whether to use one
+- Suggest appropriate starter templates based on the tech stack preferences
+- Explain the benefits (faster setup, best practices, community support)
+- Let the user decide whether to use one
 
 4. If the user confirms no starter template will be used:
-   - Proceed with architecture design from scratch
-   - Note that manual setup will be required for all tooling and configuration
+
+- Proceed with architecture design from scratch
+- Note that manual setup will be required for all tooling and configuration
 
 Document the decision here before proceeding with the architecture design. In none, just say N/A
 
@@ -796,10 +802,12 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
 2. Consider the repository structure (monorepo/polyrepo) from PRD
 3. Define clear boundaries and interfaces between components
 4. For each component, specify:
-   - Primary responsibility
-   - Key interfaces/APIs exposed
-   - Dependencies on other components
-   - Technology specifics based on tech stack choices
+
+- Primary responsibility
+- Key interfaces/APIs exposed
+- Dependencies on other components
+- Technology specifics based on tech stack choices
+
 5. Create component diagrams where helpful
 6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
 
@@ -1308,15 +1316,15 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
 
 1. If project has UI components:
 
-   - Recommend engaging Design Architect agent
-   - Use "Frontend Architecture Mode"
-   - Provide this document as input
+- Recommend engaging Design Architect agent
+- Use "Frontend Architecture Mode"
+- Provide this document as input
 
 2. For all projects:
 
-   - Review with Product Owner
-   - Begin story implementation with Dev agent
-   - Set up infrastructure with DevOps agent
+- Review with Product Owner
+- Begin story implementation with Dev agent
+- Set up infrastructure with DevOps agent
 
 3. Include specific prompts for next agents if needed]]
 
@@ -1374,7 +1382,8 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
      - Routing configuration
      - Testing setup and patterns
      - Build and development scripts
-   - Use this analysis to ensure your frontend architecture aligns with the starter's patterns
+
+- Use this analysis to ensure your frontend architecture aligns with the starter's patterns
 
 3. If no frontend starter is mentioned but this is a new UI, ensure we know what the ui language and framework is:
 
@@ -1538,23 +1547,23 @@ This unified approach combines what would traditionally be separate backend and
 
 1. Review the PRD and other documents for mentions of:
 
-   - Fullstack starter templates (e.g., T3 Stack, MEAN/MERN starters, Django + React templates)
-   - Monorepo templates (e.g., Nx, Turborepo starters)
-   - Platform-specific starters (e.g., Vercel templates, AWS Amplify starters)
-   - Existing projects being extended or cloned
+- Fullstack starter templates (e.g., T3 Stack, MEAN/MERN starters, Django + React templates)
+- Monorepo templates (e.g., Nx, Turborepo starters)
+- Platform-specific starters (e.g., Vercel templates, AWS Amplify starters)
+- Existing projects being extended or cloned
 
 2. If starter templates or existing projects are mentioned:
 
-   - Ask the user to provide access (links, repos, or files)
-   - Analyze to understand pre-configured choices and constraints
-   - Note any architectural decisions already made
-   - Identify what can be modified vs what must be retained
+- Ask the user to provide access (links, repos, or files)
+- Analyze to understand pre-configured choices and constraints
+- Note any architectural decisions already made
+- Identify what can be modified vs what must be retained
 
 3. If no starter is mentioned but this is greenfield:
 
-   - Suggest appropriate fullstack starters based on tech preferences
-   - Consider platform-specific options (Vercel, AWS, etc.)
-   - Let user decide whether to use one
+- Suggest appropriate fullstack starters based on tech preferences
+- Consider platform-specific options (Vercel, AWS, etc.)
+- Let user decide whether to use one
 
 4. Document the decision and any constraints it imposes
 
@@ -1853,10 +1862,12 @@ servers:
 2. Consider both frontend and backend components
 3. Define clear boundaries and interfaces between components
 4. For each component, specify:
-   - Primary responsibility
-   - Key interfaces/APIs exposed
-   - Dependencies on other components
-   - Technology specifics based on tech stack choices
+
+- Primary responsibility
+- Key interfaces/APIs exposed
+- Dependencies on other components
+- Technology specifics based on tech stack choices
+
 5. Create component diagrams where helpful
 6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
 
@@ -3117,11 +3128,13 @@ IMPORTANT: If any required documents are missing or inaccessible, immediately as
 
 PROJECT TYPE DETECTION:
 First, determine the project type by checking:
+
 - Does the architecture include a frontend/UI component?
 - Is there a frontend-architecture.md document?
 - Does the PRD mention user interfaces or frontend requirements?
 
 If this is a backend-only or service-only project:
+
 - Skip sections marked with [[FRONTEND ONLY]]
 - Focus extra attention on API design, service architecture, and integration patterns
 - Note in your final report that frontend sections were skipped due to project type
@@ -3551,7 +3564,7 @@ Templates in the BMAD method use standardized markup for AI processing. These co
 
 - **{{placeholders}}**: Variables to be replaced with actual content
 - **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **<<REPEAT>>** sections: Content blocks that may be repeated as needed
+- **REPEAT** sections: Content blocks that may be repeated as needed
 - **^^CONDITION^^** blocks: Conditional content included only if criteria are met
 - **@{examples}**: Example content for guidance (never output to users)
 

.bmad-core/web-bundles/agents/bmad-orchestrator.txt

@@ -7,27 +7,30 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
-   - `==================== START: folder#filename ====================`
-   - `==================== END: folder#filename ====================`
-   
+
+- `==================== START: folder#filename ====================`
+- `==================== END: folder#filename ====================`
+
 When you need to reference a resource mentioned in your instructions:
-   - Look for the corresponding START/END tags
-   - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
-   - If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
+- Look for the corresponding START/END tags
+- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
+- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   ```yaml
-   dependencies:
-     utils:
-       - template-format
-     tasks:
-       - create-story
-   ```
+**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
 
-   These references map directly to bundle sections:
-   - `utils: template-format` → Look for `==================== START: utils#template-format ====================`
-   - `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
+```yaml
+dependencies:
+  utils:
+    - template-format
+  tasks:
+    - create-story
+```
+
+These references map directly to bundle sections:
+
+- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
+- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -45,6 +48,8 @@ agent:
   name: BMad Orchestrator
   id: bmad-orchestrator
   title: BMAD Master Orchestrator
+  icon: 🎭
+  whenToUse: "Use for workflow coordination, multi-agent tasks, role switching guidance, and when unsure which specialist to consult"
 
 persona:
   role: Master Orchestrator & BMAD Method Expert
@@ -118,268 +123,208 @@ dependencies:
 ==================== END: agents#bmad-orchestrator ====================
 
 ==================== START: tasks#create-agent ====================
-# Create IDE Agent Task
+# Create Agent Task
 
-This task guides you through creating a new BMAD IDE agent that conforms to the IDE agent schema and integrates effectively with workflows and teams.
-
-**Note for User-Created IDE Agents**: If creating a custom IDE agent for your own use (not part of the core BMAD system), prefix the agent ID with a period (e.g., `.api-expert`) to ensure it's gitignored and won't conflict with repository updates.
+This task guides you through creating a new BMAD agent following the standard template.
 
 ## Prerequisites
 
-1. Load and understand the IDE agent schema: `/bmad-core/schemas/ide-agent-schema.yml`
-2. Review existing IDE agents in `/bmad-core/ide-agents/` for patterns and conventions
-3. Review workflows in `/bmad-core/workflows/` to identify integration opportunities
-4. Consider if this agent should also have a full agent counterpart
+- Agent template: `.bmad-core/templates/agent-tmpl.md`
+- Target directory: `.bmad-core/agents/`
 
-## Process
+## Steps
 
-### 1. Define Agent Core Identity
+### 1. Gather Agent Information
 
-Based on the schema's required fields:
+Collect the following information from the user:
 
-- **Role**: Must end with "IDE Agent" (pattern: `^.+ IDE Agent$`)
-  - Example: "API Specialist IDE Agent", "Test Engineer IDE Agent"
-- **Agent ID**: Following pattern `^[a-z][a-z0-9-]*$`
-  - For user agents: prefix with period (`.api-expert`)
-- **Primary Purpose**: Define ONE focused capability
+- **Agent ID**: Unique identifier (lowercase, hyphens allowed, e.g., `data-analyst`)
+- **Agent Name**: Display name (e.g., `Data Analyst`)
+- **Agent Title**: Professional title (e.g., `Data Analysis Specialist`)
+- **Role Description**: Brief description of the agent's primary role
+- **Communication Style**: How the agent communicates (e.g., `analytical, data-driven, clear`)
+- **Identity**: Detailed description of who this agent is
+- **Focus Areas**: Primary areas of expertise and focus
+- **Core Principles**: 3-5 guiding principles for the agent
+- **Customization**: Optional specific behaviors or overrides
 
-### 2. Create File References
+### 2. Define Agent Capabilities
 
-All IDE agents must include (per schema):
+**IMPORTANT**:
+
+- If your agent will perform any actions → You MUST create corresponding tasks in `.bmad-core/tasks/`
+- If your agent will create any documents → You MUST create templates in `.bmad-core/templates/` AND include the `create-doc` task
+
+Determine:
+
+- **Custom Commands**: Agent-specific commands beyond the defaults
+- **Required Tasks**: Tasks from `.bmad-core/tasks/` the agent needs
+  - For any action the agent performs, a corresponding task file must exist
+  - Always include `create-doc` if the agent creates any documents
+- **Required Templates**: Templates from `.bmad-core/templates/` the agent uses
+  - For any document the agent can create, a template must exist
+- **Required Checklists**: Checklists the agent references
+- **Required Data**: Data files the agent needs access to
+- **Required Utils**: Utility files the agent uses
+
+### 3. Handle Missing Dependencies
+
+**Protocol for Missing Tasks/Templates:**
+
+1. Check if each required task/template exists
+2. For any missing items:
+   - Create a basic version following the appropriate template
+   - Track what was created in a list
+3. Continue with agent creation
+4. At the end, present a summary of all created items
+
+**Track Created Items:**
+
+```
+Created during agent setup:
+- Tasks:
+  - [ ] task-name-1.md
+  - [ ] task-name-2.md
+- Templates:
+  - [ ] template-name-1.md
+  - [ ] template-name-2.md
+```
+
+### 4. Create Agent File
+
+1. Copy the template from `.bmad-core/templates/agent-tmpl.md`
+2. Replace all placeholders with gathered information:
+
+   - `[AGENT_ID]` → agent id
+   - `[AGENT_NAME]` → agent name
+   - `[AGENT_TITLE]` → agent title
+   - `[AGENT_ROLE_DESCRIPTION]` → role description
+   - `[COMMUNICATION_STYLE]` → communication style
+   - `[AGENT_IDENTITY_DESCRIPTION]` → identity description
+   - `[PRIMARY_FOCUS_AREAS]` → focus areas
+   - `[PRINCIPLE_X]` → core principles
+   - `[OPTIONAL_CUSTOMIZATION]` → customization (or remove if none)
+   - `[DEFAULT_MODE_DESCRIPTION]` → description of default chat mode
+   - `[STARTUP_INSTRUCTIONS]` → what the agent should do on activation
+   - Add custom commands, tasks, templates, etc.
+
+3. Save as `.bmad-core/agents/[agent-id].md`
+
+### 4. Validate Agent
+
+Ensure:
+
+- All placeholders are replaced
+- Dependencies (tasks, templates, etc.) actually exist
+- Commands are properly formatted
+- YAML structure is valid
+
+### 5. Build and Test
+
+1. Run `npm run build:agents` to include in builds
+2. Test agent activation and commands
+3. Verify all dependencies load correctly
+
+### 6. Final Summary
+
+Present to the user:
+
+```
+✅ Agent Created: [agent-name]
+   Location: .bmad-core/agents/[agent-id].md
+
+📝 Dependencies Created:
+   Tasks:
+   - ✅ task-1.md - [brief description]
+   - ✅ task-2.md - [brief description]
+
+   Templates:
+   - ✅ template-1.md - [brief description]
+   - ✅ template-2.md - [brief description]
+
+⚠️  Next Steps:
+   1. Review and customize the created tasks/templates
+   2. Run npm run build:agents
+   3. Test the agent thoroughly
+```
+
+## Template Reference
+
+The agent template structure:
+
+- **activation-instructions**: How the AI should interpret the file
+- **agent**: Basic agent metadata
+- **persona**: Character and behavior definition
+- **startup**: Initial actions on activation
+- **commands**: Available commands (always include defaults)
+- **dependencies**: Required resources organized by type
+
+## Example Usage
 
 ```yaml
-taskroot: "bmad-core/tasks/"  # Required constant
-templates: "bmad-core/templates/"  # Optional but common
-checklists: "bmad-core/checklists/"  # Optional
-default-template: "bmad-core/templates/{template-name}"  # If agent creates documents
+agent:
+  name: Data Analyst
+  id: data-analyst
+  title: Data Analysis Specialist
+
+persona:
+  role: Expert in data analysis, visualization, and insights extraction
+  style: analytical, data-driven, clear, methodical
+  identity: I am a seasoned data analyst who transforms raw data into actionable insights
+  focus: data exploration, statistical analysis, visualization, reporting
+
+  core_principles:
+    - Data integrity and accuracy above all
+    - Clear communication of complex findings
+    - Actionable insights over raw numbers
 ```
 
-Additional custom references as needed (e.g., `story-path`, `coding-standards`)
+## Creating Missing Dependencies
 
-### 3. Define Persona (Schema Required Fields)
+When a required task or template doesn't exist:
 
-Create concise persona following schema structure:
+1. **For Missing Tasks**: Create using `.bmad-core/templates/task-template.md`
 
-- **Name**: Character name (e.g., "Alex", "Dana")
-- **Role**: Professional role title
-- **Identity**: Extended specialization (20+ chars)
-- **Focus**: Primary objectives (20+ chars)
-- **Style**: Communication approach (20+ chars)
+   - Name it descriptively (e.g., `analyze-metrics.md`)
+   - Define clear steps for the action
+   - Include any required inputs/outputs
 
-Keep descriptions brief for IDE efficiency!
+2. **For Missing Templates**: Create a basic structure
 
-### 4. Core Principles (Minimum 3 Required)
+   - Name it descriptively (e.g., `metrics-report-template.md`)
+   - Include placeholders for expected content
+   - Add sections relevant to the document type
 
-Must include these based on schema validation:
+3. **Always Track**: Keep a list of everything created to report at the end
 
-1. **Numbered Options Protocol** (REQUIRED): "When presenting multiple options, always use numbered lists for easy selection"
-2. **[Domain-Specific Principle]**: Related to agent's expertise
-3. **[Quality/Efficiency Principle]**: How they ensure excellence
-4. Additional principles as needed (keep concise)
+## Important Reminders
 
-### 5. Critical Startup Operating Instructions
+### Tasks and Templates Requirement
 
-First instruction MUST announce name/role and mention *help (schema requirement):
+- **Every agent action needs a task**: If an agent can "analyze data", there must be an `analyze-data.md` task
+- **Every document type needs a template**: If an agent can create reports, there must be a `report-template.md`
+- **Document creation requires**: Both the template AND the `create-doc` task in dependencies
 
-```markdown
-1. Announce your name and role, and let the user know they can say *help at any time to list the commands on your first response as a reminder even if their initial request is a question, wrapping the question. For Example 'I am {role} {name}, {response}... Also remember, you can enter `*help` to see a list of commands at any time.'
+### Example Dependencies
+
+```yaml
+dependencies:
+  tasks:
+    - create-doc # Required if agent creates any documents
+    - analyze-requirements # Custom task for this agent
+    - generate-report # Another custom task
+  templates:
+    - requirements-doc # Template for requirements documents
+    - analysis-report # Template for analysis reports
 ```
 
-Add 2-5 additional startup instructions specific to the agent's role.
+## Notes
 
-### 6. Commands (Minimum 2 Required)
-
-Required commands per schema:
-
-```markdown
-- `*help` - Show these available commands as a numbered list offering selection
-- `*chat-mode` - Enter conversational mode, staying in character while offering `advanced-elicitation` when providing advice or multiple options. Ends if other task or command is given
-```
-
-Add role-specific commands:
-- Use pattern: `^\\*[a-z][a-z0-9-]*( \\{[^}]+\\})?$`
-- Include clear descriptions (10+ chars)
-- Reference tasks when appropriate
-
-### 7. Workflow Integration Analysis
-
-Analyze where this IDE agent fits in workflows:
-
-1. **Load workflow definitions** from `/bmad-core/workflows/`
-2. **Identify integration points**:
-   - Which workflow phases benefit from this agent?
-   - Can they replace or augment existing workflow steps?
-   - Do they enable new workflow capabilities?
-
-3. **Suggest workflow enhancements**:
-   - For technical agents → development/implementation phases
-   - For testing agents → validation phases
-   - For design agents → planning/design phases
-   - For specialized agents → specific workflow steps
-
-4. **Document recommendations**:
-   ```markdown
-   ## Workflow Integration
-   
-   This agent enhances the following workflows:
-   - `greenfield-service`: API design phase (between architecture and implementation)
-   - `brownfield-service`: API refactoring and modernization
-   - User can specify: {custom workflow integration}
-   ```
-
-### 8. Team Integration Suggestions
-
-Consider which teams benefit from this IDE agent:
-
-1. **Analyze team compositions** in `/bmad-core/agent-teams/`
-2. **Suggest team additions**:
-   - Technical specialists → development teams
-   - Quality specialists → full-stack teams
-   - Domain experts → relevant specialized teams
-
-3. **Document integration**:
-   ```markdown
-   ## Team Integration
-   
-   Recommended teams for this agent:
-   - `team-fullstack`: Provides specialized {domain} expertise
-   - `team-no-ui`: Enhances backend {capability}
-   - User proposed: {custom team integration}
-   ```
-
-### 9. Create the IDE Agent File
-
-Create `/bmad-core/ide-agents/{agent-id}.ide.md` following schema structure:
-(For user agents: `/bmad-core/ide-agents/.{agent-id}.ide.md`)
-
-```markdown
-# Role: {Title} IDE Agent
-
-## File References
-
-`taskroot`: `bmad-core/tasks/`
-`templates`: `bmad-core/templates/`
-{additional references}
-
-## Persona
-
-- **Name:** {Name}
-- **Role:** {Role}
-- **Identity:** {20+ char description}
-- **Focus:** {20+ char objectives}
-- **Style:** {20+ char communication style}
-
-## Core Principles (Always Active)
-
-- **{Principle}:** {Description}
-- **{Principle}:** {Description}
-- **Numbered Options Protocol:** When presenting multiple options, always use numbered lists for easy selection
-
-## Critical Startup Operating Instructions
-
-1. Announce your name and role, and let the user know they can say *help at any time...
-2. {Additional startup instruction}
-3. {Additional startup instruction}
-
-## Commands
-
-- `*help` - Show these available commands as a numbered list offering selection
-- `*chat-mode` - Enter conversational mode, staying in character while offering `advanced-elicitation`...
-- `*{command}` - {Description of what it does}
-{additional commands}
-
-{Optional sections like Expertise, Workflow, Protocol, etc.}
-```
-
-### 10. Validation and Testing
-
-1. **Schema Validation**: Ensure all required fields are present
-2. **Pattern Validation**: Check role name, command patterns
-3. **Size Optimization**: Keep concise for IDE efficiency
-4. **Command Testing**: Verify all commands are properly formatted
-5. **Integration Testing**: Test in actual IDE environment
-
-## Example: API Specialist IDE Agent
-
-```markdown
-# Role: API Specialist IDE Agent
-
-## File References
-
-`taskroot`: `bmad-core/tasks/`
-`templates`: `bmad-core/templates/`
-`default-template`: `bmad-core/templates/api-spec-tmpl`
-
-## Persona
-
-- **Name:** Alex
-- **Role:** API Specialist
-- **Identity:** REST API design expert specializing in scalable, secure service interfaces
-- **Focus:** Creating clean, well-documented APIs that follow industry best practices
-- **Style:** Direct, example-driven, focused on practical implementation patterns
-
-## Core Principles (Always Active)
-
-- **API-First Design:** Every endpoint designed with consumer needs in mind
-- **Security by Default:** Authentication and authorization built into every design
-- **Documentation Excellence:** APIs are only as good as their documentation
-- **Numbered Options Protocol:** When presenting multiple options, always use numbered lists for easy selection
-
-## Critical Startup Operating Instructions
-
-1. Announce your name and role, and let the user know they can say *help at any time to list the commands on your first response as a reminder even if their initial request is a question, wrapping the question. For Example 'I am API Specialist Alex, {response}... Also remember, you can enter `*help` to see a list of commands at any time.'
-2. Assess the API design context (REST, GraphQL, gRPC)
-3. Focus on practical, implementable solutions
-
-## Commands
-
-- `*help` - Show these available commands as a numbered list offering selection
-- `*chat-mode` - Enter conversational mode, staying in character while offering `advanced-elicitation` when providing advice or multiple options. Ends if other task or command is given
-- `*design-api` - Design REST API endpoints for specified requirements
-- `*create-spec` - Create OpenAPI specification using default template
-- `*review-api` - Review existing API design for best practices
-- `*security-check` - Analyze API security considerations
-
-## Workflow Integration
-
-This agent enhances the following workflows:
-- `greenfield-service`: API design phase after architecture
-- `brownfield-service`: API modernization and refactoring
-- `greenfield-fullstack`: API contract definition between frontend/backend
-
-## Team Integration
-
-Recommended teams for this agent:
-- `team-fullstack`: API contract expertise
-- `team-no-ui`: Backend API specialization
-- Any team building service-oriented architectures
-```
-
-## IDE Agent Creation Checklist
-
-- [ ] Role name ends with "IDE Agent"
-- [ ] All schema-required fields present
-- [ ] Includes required File References
-- [ ] Persona has all 5 required fields
-- [ ] Minimum 3 Core Principles including Numbered Options Protocol
-- [ ] First startup instruction announces name/role with *help
-- [ ] Includes *help and *chat-mode commands
-- [ ] Commands follow pattern requirements
-- [ ] Workflow integration documented
-- [ ] Team integration suggestions provided
-- [ ] Validates against ide-agent-schema.yml
-- [ ] Concise and focused on single expertise
-
-## Best Practices
-
-1. **Stay Focused**: IDE agents should excel at ONE thing
-2. **Reference Tasks**: Don't duplicate task content
-3. **Minimal Personality**: Just enough to be helpful
-4. **Clear Commands**: Make it obvious what each command does
-5. **Integration First**: Consider how agent enhances existing workflows
-6. **Schema Compliance**: Always validate against the schema
-
-This schema-driven approach ensures IDE agents are consistent, integrated, and valuable additions to the BMAD ecosystem.
+- Keep agent definitions focused and specific
+- Ensure dependencies are minimal and necessary
+- Test thoroughly before distribution
+- Follow existing agent patterns for consistency
+- Remember: No task = agent can't do it, No template = agent can't create it
 ==================== END: tasks#create-agent ====================
 
 ==================== START: tasks#create-team ====================
@@ -430,6 +375,7 @@ Based on the schema requirements:
 Based on team purpose, recommend agents:
 
 **For Planning & Strategy Teams:**
+
 - `bmad` (required orchestrator)
 - `analyst` - Requirements gathering and research
 - `pm` - Product strategy and documentation
@@ -437,6 +383,7 @@ Based on team purpose, recommend agents:
 - `architect` - Technical planning (if technical planning needed)
 
 **For Design & UX Teams:**
+
 - `bmad` (required orchestrator)
 - `ux-expert` - User experience design
 - `architect` - Frontend architecture
@@ -444,14 +391,16 @@ Based on team purpose, recommend agents:
 - `po` - Design validation
 
 **For Development Teams:**
-- `bmad` (required orchestrator)
+
+- `bmad-orchestrator` (required)
 - `sm` - Sprint coordination
 - `dev` - Implementation
 - `qa` - Quality assurance
 - `architect` - Technical guidance
 
 **For Full-Stack Teams:**
-- `bmad` (required orchestrator)
+
+- `bmad-orchestrator` (required)
 - `analyst` - Initial planning
 - `pm` - Product management
 - `ux-expert` - UI/UX design (if UI work included)
@@ -469,6 +418,7 @@ Based on team purpose, recommend agents:
 Based on the schema's workflow enum values and team composition:
 
 1. **Analyze team capabilities** against available workflows:
+
    - `brownfield-fullstack` - Requires full team with UX
    - `brownfield-service` - Backend-focused team
    - `brownfield-ui` - UI/UX-focused team
@@ -477,6 +427,7 @@ Based on the schema's workflow enum values and team composition:
    - `greenfield-ui` - Frontend team for new UIs
 
 2. **Match workflows to agents**:
+
    - UI workflows require `ux-expert`
    - Service workflows benefit from `architect` and `dev`
    - All workflows benefit from planning agents (`analyst`, `pm`)
@@ -498,13 +449,13 @@ bundle:
 
 agents:
   - bmad # Required orchestrator
-  - {agent-id-1}
-  - {agent-id-2}
+  - { agent-id-1 }
+  - { agent-id-2 }
   # ... additional agents
 
 workflows:
-  - {workflow-1} # From enum list
-  - {workflow-2}
+  - { workflow-1 } # From enum list
+  - { workflow-2 }
   # ... additional workflows
 ```
 
@@ -513,10 +464,10 @@ workflows:
 Before finalizing, verify:
 
 1. **Role Coverage**: Does the team have all necessary skills for its workflows?
-2. **Size Optimization**: 
+2. **Size Optimization**:
    - Minimum: 2 agents (bmad + 1)
    - Recommended: 3-7 agents
-   - Maximum with wildcard: bmad + "*"
+   - Maximum with wildcard: bmad + "\*"
 3. **Workflow Alignment**: Can the selected agents execute all workflows?
 4. **Schema Compliance**: Configuration matches all schema requirements
 
@@ -544,8 +495,8 @@ Document how this team integrates with existing system:
 bundle:
   name: "Team API"
   description: >-
-    Specialized team for API and backend service development. Focuses on 
-    robust service architecture, implementation, and testing without UI 
+    Specialized team for API and backend service development. Focuses on
+    robust service architecture, implementation, and testing without UI
     components. Ideal for microservices, REST APIs, and backend systems.
 
 agents:
@@ -567,8 +518,8 @@ workflows:
 bundle:
   name: "Team Prototype"
   description: >-
-    Agile team for rapid prototyping and proof of concept development. 
-    Combines planning, design, and implementation for quick iterations 
+    Agile team for rapid prototyping and proof of concept development.
+    Combines planning, design, and implementation for quick iterations
     on new ideas and experimental features.
 
 agents:
@@ -650,7 +601,7 @@ Request from the user:
 
 #### 1.3 Create Planning Document
 
-**STOP HERE AND CREATE PLAN FIRST**
+IMPORTANT: STOP HERE AND CREATE PLAN FIRST
 
 Create `expansion-packs/{pack-name}/plan.md` with:
 
@@ -696,7 +647,7 @@ Create `expansion-packs/{pack-name}/plan.md` with:
 User approval received: [ ] Yes
 ```
 
-**Wait for user approval before proceeding to Phase 2**
+Important: Wait for user approval before proceeding to Phase 2
 
 ### Phase 2: Component Design
 
@@ -753,7 +704,7 @@ For each checklist:
 
 ### Phase 3: Implementation
 
-**Only proceed after plan.md is approved**
+IMPORTANT: Only proceed after plan.md is approved
 
 #### 3.1 Create Directory Structure
 
@@ -838,7 +789,7 @@ post_install_message: |
 
 ### Phase 4: Content Creation
 
-**Work through plan.md checklist systematically**
+IMPORTANT: Work through plan.md checklist systematically!
 
 #### 4.1 Create Orchestrator First
 
@@ -919,12 +870,6 @@ For each required data file:
 - **Example**:
 ```
 
-{sample content}
-
-```
-
-```
-
 ## Example: Healthcare Expansion Pack
 
 ```text
@@ -973,38 +918,38 @@ Required user data files:
 
 ### Planning Phase
 
-6. "Here's the proposed plan. Please review and approve before we continue."
+1. "Here's the proposed plan. Please review and approve before we continue."
 
 ### Orchestrator Design
 
-7. "What key commands should the {pack-name} orchestrator support?"
-8. "What's the typical workflow from start to finish?"
-9. "How should it integrate with core BMAD agents?"
+1. "What key commands should the {pack-name} orchestrator support?"
+2. "What's the typical workflow from start to finish?"
+3. "How should it integrate with core BMAD agents?"
 
 ### Agent Planning
 
-10. "For agent '{name}', what is their specific expertise?"
-11. "What tasks will this agent reference? (I'll create them)"
-12. "What templates will this agent use? (I'll create them)"
-13. "What data files will this agent need? (You'll provide these)"
+1. "For agent '{name}', what is their specific expertise?"
+2. "What tasks will this agent reference? (I'll create them)"
+3. "What templates will this agent use? (I'll create them)"
+4. "What data files will this agent need? (You'll provide these)"
 
 ### Task Design
 
-14. "Describe the '{task}' process step-by-step"
-15. "What information is needed to complete this task?"
-16. "What should the output look like?"
+1. "Describe the '{task}' process step-by-step"
+2. "What information is needed to complete this task?"
+3. "What should the output look like?"
 
 ### Template Creation
 
-17. "What sections should the '{template}' document have?"
-18. "Are there any required formats or standards?"
-19. "Can you provide an example of a completed document?"
+1. "What sections should the '{template}' document have?"
+2. "Are there any required formats or standards?"
+3. "Can you provide an example of a completed document?"
 
 ### Data Requirements
 
-20. "For {data-file}, what information should it contain?"
-21. "What format should this data be in?"
-22. "Can you provide a sample?"
+1. "For {data-file}, what information should it contain?"
+2. "What format should this data be in?"
+3. "Can you provide a sample?"
 
 ## Important Considerations
 
@@ -1297,11 +1242,11 @@ The actual list depends on which team bundle is loaded. When responding to this
 
 Example response format:
 
-```
+```text
 Available workflows for [Team Name]:
 1. [workflow-id] - [Brief description based on workflow type]
 2. [workflow-id] - [Brief description based on workflow type]
-...
+[... etc. ...]
 
 Use /workflow-start {number or id} to begin a workflow.
 ```
@@ -1318,7 +1263,7 @@ Shows current workflow progress, completed artifacts, and next steps.
 
 Example response:
 
-```
+```text
 Current Workflow: Greenfield Full-Stack Development
 Stage: Product Planning (2 of 6)
 Completed:
@@ -1338,7 +1283,7 @@ Resumes a workflow from where it left off, useful when starting a new chat.
 
 User can provide completed artifacts:
 
-```
+```text
 User: /workflow-resume greenfield-fullstack
       I have completed: project-brief, PRD
 BMad: I see you've completed Discovery and part of Product Planning.
@@ -1406,7 +1351,7 @@ When user returns after interruption:
 
 Example:
 
-```
+```text
 User: I'm working on a new app. Here's my PRD and architecture doc.
 BMad: I see you have a PRD and architecture document. Based on these artifacts,
       it looks like you're following the greenfield-fullstack workflow and have completed
@@ -1429,7 +1374,7 @@ When transitioning between agents, pass:
 
 Example transition:
 
-```
+```text
 BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
       the next step is UX Strategy with Sally.
 
@@ -1489,7 +1434,7 @@ Templates in the BMAD method use standardized markup for AI processing. These co
 
 - **{{placeholders}}**: Variables to be replaced with actual content
 - **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **<<REPEAT>>** sections: Content blocks that may be repeated as needed
+- **REPEAT** sections: Content blocks that may be repeated as needed
 - **^^CONDITION^^** blocks: Conditional content included only if criteria are met
 - **@{examples}**: Example content for guidance (never output to users)
 

.bmad-core/web-bundles/agents/dev.txt

@@ -7,27 +7,30 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
-   - `==================== START: folder#filename ====================`
-   - `==================== END: folder#filename ====================`
-   
+
+- `==================== START: folder#filename ====================`
+- `==================== END: folder#filename ====================`
+
 When you need to reference a resource mentioned in your instructions:
-   - Look for the corresponding START/END tags
-   - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
-   - If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
+- Look for the corresponding START/END tags
+- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
+- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   ```yaml
-   dependencies:
-     utils:
-       - template-format
-     tasks:
-       - create-story
-   ```
+**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
 
-   These references map directly to bundle sections:
-   - `utils: template-format` → Look for `==================== START: utils#template-format ====================`
-   - `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
+```yaml
+dependencies:
+  utils:
+    - template-format
+  tasks:
+    - create-story
+```
+
+These references map directly to bundle sections:
+
+- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
+- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -45,6 +48,8 @@ agent:
   name: James
   id: dev
   title: Full Stack Developer
+  icon: 💻
+  whenToUse: "Use for code implementation, debugging, refactoring, and development best practices"
   customization:
 
 persona:

.bmad-core/web-bundles/agents/pm.txt

@@ -7,27 +7,30 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
-   - `==================== START: folder#filename ====================`
-   - `==================== END: folder#filename ====================`
-   
+
+- `==================== START: folder#filename ====================`
+- `==================== END: folder#filename ====================`
+
 When you need to reference a resource mentioned in your instructions:
-   - Look for the corresponding START/END tags
-   - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
-   - If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
+- Look for the corresponding START/END tags
+- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
+- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   ```yaml
-   dependencies:
-     utils:
-       - template-format
-     tasks:
-       - create-story
-   ```
+**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
 
-   These references map directly to bundle sections:
-   - `utils: template-format` → Look for `==================== START: utils#template-format ====================`
-   - `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
+```yaml
+dependencies:
+  utils:
+    - template-format
+  tasks:
+    - create-story
+```
+
+These references map directly to bundle sections:
+
+- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
+- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -51,6 +54,8 @@ agent:
   name: John
   id: pm
   title: Product Manager
+  icon: 📋
+  whenToUse: "Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication"
   customization:
 
 persona:
@@ -443,7 +448,7 @@ Present these numbered options to the user:
 
 **Research Prompt Template:**
 
-```
+```markdown
 ## Research Objective
 [Clear statement of what this research aims to achieve]
 
@@ -766,8 +771,8 @@ Create a single focused story following this structure:
 
 #### User Story
 
-As a {{user type}},  
-I want {{specific action/capability}},  
+As a {{user type}},
+I want {{specific action/capability}},
 So that {{clear benefit/value}}.
 
 #### Story Context
@@ -1946,11 +1951,11 @@ After presenting the report, ask if the user wants:
 
 ### Critical Deficiencies
 
-_To be populated during validation_
+(To be populated during validation)
 
 ### Recommendations
 
-_To be populated during validation_
+(To be populated during validation)
 
 ### Final Decision
 
@@ -2158,7 +2163,7 @@ Templates in the BMAD method use standardized markup for AI processing. These co
 
 - **{{placeholders}}**: Variables to be replaced with actual content
 - **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **<<REPEAT>>** sections: Content blocks that may be repeated as needed
+- **REPEAT** sections: Content blocks that may be repeated as needed
 - **^^CONDITION^^** blocks: Conditional content included only if criteria are met
 - **@{examples}**: Example content for guidance (never output to users)
 

.bmad-core/web-bundles/agents/po.txt

@@ -7,27 +7,30 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
-   - `==================== START: folder#filename ====================`
-   - `==================== END: folder#filename ====================`
-   
+
+- `==================== START: folder#filename ====================`
+- `==================== END: folder#filename ====================`
+
 When you need to reference a resource mentioned in your instructions:
-   - Look for the corresponding START/END tags
-   - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
-   - If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
+- Look for the corresponding START/END tags
+- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
+- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   ```yaml
-   dependencies:
-     utils:
-       - template-format
-     tasks:
-       - create-story
-   ```
+**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
 
-   These references map directly to bundle sections:
-   - `utils: template-format` → Look for `==================== START: utils#template-format ====================`
-   - `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
+```yaml
+dependencies:
+  utils:
+    - template-format
+  tasks:
+    - create-story
+```
+
+These references map directly to bundle sections:
+
+- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
+- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -51,6 +54,8 @@ agent:
   name: Sarah
   id: po
   title: Product Owner
+  icon: 📝
+  whenToUse: "Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions"
   customization:
 
 persona:
@@ -675,8 +680,8 @@ Create a single focused story following this structure:
 
 #### User Story
 
-As a {{user type}},  
-I want {{specific action/capability}},  
+As a {{user type}},
+I want {{specific action/capability}},
 So that {{clear benefit/value}}.
 
 #### Story Context
@@ -1241,7 +1246,7 @@ Generate a comprehensive validation report that adapts to project type:
 After presenting the report, ask if the user wants:
 
 - Detailed analysis of any failed sections
-- Specific story resequencing suggestions
+- Specific story reordering suggestions
 - Risk mitigation strategies
 - [BROWNFIELD] Integration risk deep-dive]]
 
@@ -1262,11 +1267,11 @@ After presenting the report, ask if the user wants:
 
 ### Critical Deficiencies
 
-_To be populated during validation_
+(To be populated during validation)
 
 ### Recommendations
 
-_To be populated during validation_
+(To be populated during validation)
 
 ### Final Decision
 
@@ -1469,7 +1474,7 @@ Templates in the BMAD method use standardized markup for AI processing. These co
 
 - **{{placeholders}}**: Variables to be replaced with actual content
 - **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **<<REPEAT>>** sections: Content blocks that may be repeated as needed
+- **REPEAT** sections: Content blocks that may be repeated as needed
 - **^^CONDITION^^** blocks: Conditional content included only if criteria are met
 - **@{examples}**: Example content for guidance (never output to users)
 

.bmad-core/web-bundles/agents/qa.txt

@@ -7,27 +7,30 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
-   - `==================== START: folder#filename ====================`
-   - `==================== END: folder#filename ====================`
-   
+
+- `==================== START: folder#filename ====================`
+- `==================== END: folder#filename ====================`
+
 When you need to reference a resource mentioned in your instructions:
-   - Look for the corresponding START/END tags
-   - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
-   - If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
+- Look for the corresponding START/END tags
+- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
+- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   ```yaml
-   dependencies:
-     utils:
-       - template-format
-     tasks:
-       - create-story
-   ```
+**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
 
-   These references map directly to bundle sections:
-   - `utils: template-format` → Look for `==================== START: utils#template-format ====================`
-   - `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
+```yaml
+dependencies:
+  utils:
+    - template-format
+  tasks:
+    - create-story
+```
+
+These references map directly to bundle sections:
+
+- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
+- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -51,6 +54,8 @@ agent:
   name: Quinn
   id: qa
   title: Quality Assurance Test Architect
+  icon: 🧪
+  whenToUse: "Use for test planning, test case creation, quality assurance, bug reporting, and testing strategy"
   customization:
 
 persona:
@@ -103,7 +108,7 @@ Templates in the BMAD method use standardized markup for AI processing. These co
 
 - **{{placeholders}}**: Variables to be replaced with actual content
 - **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **<<REPEAT>>** sections: Content blocks that may be repeated as needed
+- **REPEAT** sections: Content blocks that may be repeated as needed
 - **^^CONDITION^^** blocks: Conditional content included only if criteria are met
 - **@{examples}**: Example content for guidance (never output to users)
 

.bmad-core/web-bundles/agents/sm.txt

@@ -7,27 +7,30 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
-   - `==================== START: folder#filename ====================`
-   - `==================== END: folder#filename ====================`
-   
+
+- `==================== START: folder#filename ====================`
+- `==================== END: folder#filename ====================`
+
 When you need to reference a resource mentioned in your instructions:
-   - Look for the corresponding START/END tags
-   - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
-   - If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
+- Look for the corresponding START/END tags
+- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
+- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   ```yaml
-   dependencies:
-     utils:
-       - template-format
-     tasks:
-       - create-story
-   ```
+**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
 
-   These references map directly to bundle sections:
-   - `utils: template-format` → Look for `==================== START: utils#template-format ====================`
-   - `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
+```yaml
+dependencies:
+  utils:
+    - template-format
+  tasks:
+    - create-story
+```
+
+These references map directly to bundle sections:
+
+- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
+- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -51,6 +54,8 @@ agent:
   name: Bob
   id: sm
   title: Scrum Master
+  icon: 🏃
+  whenToUse: "Use for story creation, epic management, retrospectives in party-mode, and agile process guidance"
   customization:
 
 persona:
@@ -637,7 +642,7 @@ Templates in the BMAD method use standardized markup for AI processing. These co
 
 - **{{placeholders}}**: Variables to be replaced with actual content
 - **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **<<REPEAT>>** sections: Content blocks that may be repeated as needed
+- **REPEAT** sections: Content blocks that may be repeated as needed
 - **^^CONDITION^^** blocks: Conditional content included only if criteria are met
 - **@{examples}**: Example content for guidance (never output to users)
 

.bmad-core/web-bundles/agents/ux-expert.txt

@@ -7,27 +7,30 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
-   - `==================== START: folder#filename ====================`
-   - `==================== END: folder#filename ====================`
-   
+
+- `==================== START: folder#filename ====================`
+- `==================== END: folder#filename ====================`
+
 When you need to reference a resource mentioned in your instructions:
-   - Look for the corresponding START/END tags
-   - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
-   - If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
+- Look for the corresponding START/END tags
+- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
+- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
 
-   ```yaml
-   dependencies:
-     utils:
-       - template-format
-     tasks:
-       - create-story
-   ```
+**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
 
-   These references map directly to bundle sections:
-   - `utils: template-format` → Look for `==================== START: utils#template-format ====================`
-   - `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
+```yaml
+dependencies:
+  utils:
+    - template-format
+  tasks:
+    - create-story
+```
+
+These references map directly to bundle sections:
+
+- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
+- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -51,6 +54,8 @@ agent:
   name: Sally
   id: ux-expert
   title: UX Expert
+  icon: 🎨
+  whenToUse: "Use for UI/UX design, wireframes, prototypes, front-end specifications, and user experience optimization"
   customization:
 
 persona:
@@ -353,7 +358,7 @@ Present these numbered options to the user:
 
 **Research Prompt Template:**
 
-```
+```markdown
 ## Research Objective
 [Clear statement of what this research aims to achieve]
 
@@ -1061,7 +1066,7 @@ Templates in the BMAD method use standardized markup for AI processing. These co
 
 - **{{placeholders}}**: Variables to be replaced with actual content
 - **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **<<REPEAT>>** sections: Content blocks that may be repeated as needed
+- **REPEAT** sections: Content blocks that may be repeated as needed
 - **^^CONDITION^^** blocks: Conditional content included only if criteria are met
 - **@{examples}**: Example content for guidance (never output to users)