refactor: standardize formatting and improve readability across core documents (#211)

### CHANGES

- Add newlines and spacing for improved readability
- Standardize instructional text for consistency
- Renumber lists within tasks for better clarity
- Add language identifiers to various code blocks
- Update placeholder text for improved consistency
- Adjust descriptions and wording in multiple files
- Update VS Code settings and dictionary words

.bmad-core/checklists/architect-checklist.md

@@ -17,11 +17,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

.bmad-core/checklists/pm-checklist.md

@@ -363,11 +363,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
 

.bmad-core/checklists/po-master-checklist.md

@@ -407,7 +407,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]]
 
@@ -428,11 +428,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
 

.bmad-core/tasks/brainstorming-techniques.md

@@ -53,17 +53,17 @@ 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**ubstitute: What can be substituted?
+   - **S** = Substitute: What can be substituted?
-   - **C**ombine: What can be combined or integrated?
+   - **C** = Combine: What can be combined or integrated?
-   - **A**dapt: What can be adapted from elsewhere?
+   - **A** = Adapt: What can be adapted from elsewhere?
-   - **M**odify/Magnify: What can be emphasized or reduced?
+   - **M** = Modify/Magnify: What can be emphasized or reduced?
-   - **P**ut to other uses: What else could this be used for?
+   - **P** = Put to other uses: What else could this be used for?
-   - **E**liminate: What can be removed or simplified?
+   - **E** = Eliminate: What can be removed or simplified?
-   - **R**everse/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
@@ -72,9 +72,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.]]
-   ```
+
+   ```plaintext
    Central Concept
    ├── Branch 1
    │   ├── Sub-idea 1.1
@@ -88,21 +89,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
@@ -111,21 +112,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
@@ -137,26 +138,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
@@ -190,17 +196,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

.bmad-core/tasks/create-deep-research-prompt.md

@@ -187,7 +187,7 @@ Present these numbered options to the user:
 
 **Research Prompt Template:**
 
-```
+```markdown
 ## Research Objective
 [Clear statement of what this research aims to achieve]
 

.bmad-core/tasks/create-expansion-pack.md

@@ -39,7 +39,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:
 
@@ -85,7 +85,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
 
@@ -142,7 +142,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
 
@@ -227,7 +227,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
 
@@ -308,12 +308,6 @@ For each required data file:
 - **Example**:
 ```
 
-{sample content}
-
-```
-
-```
-
 ## Example: Healthcare Expansion Pack
 
 ```text
@@ -362,38 +356,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?"
+1. "What key commands should the {pack-name} orchestrator support?"
-8. "What's the typical workflow from start to finish?"
+2. "What's the typical workflow from start to finish?"
-9. "How should it integrate with core BMAD agents?"
+3. "How should it integrate with core BMAD agents?"
 
 ### Agent Planning
 
-10. "For agent '{name}', what is their specific expertise?"
+1. "For agent '{name}', what is their specific expertise?"
-11. "What tasks will this agent reference? (I'll create them)"
+2. "What tasks will this agent reference? (I'll create them)"
-12. "What templates will this agent use? (I'll create them)"
+3. "What templates will this agent use? (I'll create them)"
-13. "What data files will this agent need? (You'll provide these)"
+4. "What data files will this agent need? (You'll provide these)"
 
 ### Task Design
 
-14. "Describe the '{task}' process step-by-step"
+1. "Describe the '{task}' process step-by-step"
-15. "What information is needed to complete this task?"
+2. "What information is needed to complete this task?"
-16. "What should the output look like?"
+3. "What should the output look like?"
 
 ### Template Creation
 
-17. "What sections should the '{template}' document have?"
+1. "What sections should the '{template}' document have?"
-18. "Are there any required formats or standards?"
+2. "Are there any required formats or standards?"
-19. "Can you provide an example of a completed document?"
+3. "Can you provide an example of a completed document?"
 
 ### Data Requirements
 
-20. "For {data-file}, what information should it contain?"
+1. "For {data-file}, what information should it contain?"
-21. "What format should this data be in?"
+2. "What format should this data be in?"
-22. "Can you provide a sample?"
+3. "Can you provide a sample?"
 
 ## Important Considerations
 

.bmad-core/tasks/create-ide-agent.md

@@ -77,6 +77,7 @@ Required commands per schema:
 ```
 
 Add role-specific commands:
+
 - Use pattern: `^\\*[a-z][a-z0-9-]*( \\{[^}]+\\})?$`
 - Include clear descriptions (10+ chars)
 - Reference tasks when appropriate
@@ -98,6 +99,7 @@ Analyze where this IDE agent fits in workflows:
    - For specialized agents → specific workflow steps
 
 4. **Document recommendations**:
+
    ```markdown
    ## Workflow Integration
 
@@ -118,6 +120,7 @@ Consider which teams benefit from this IDE agent:
    - Domain experts → relevant specialized teams
 
 3. **Document integration**:
+
    ```markdown
    ## Team Integration
 

.bmad-core/tasks/create-team.md

@@ -45,6 +45,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
@@ -52,6 +53,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
@@ -59,6 +61,7 @@ Based on team purpose, recommend agents:
 - `po` - Design validation
 
 **For Development Teams:**
+
 - `bmad` (required orchestrator)
 - `sm` - Sprint coordination
 - `dev` - Implementation
@@ -66,6 +69,7 @@ Based on team purpose, recommend agents:
 - `architect` - Technical guidance
 
 **For Full-Stack Teams:**
+
 - `bmad` (required orchestrator)
 - `analyst` - Initial planning
 - `pm` - Product management

.bmad-core/templates/architecture-tmpl.md

@@ -45,6 +45,7 @@ If the project includes a significant user interface, a separate Frontend Archit
 - 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
 
@@ -222,10 +223,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
+
 5. Create component diagrams where helpful
 6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
 

.bmad-core/templates/competitor-analysis-tmpl.md

@@ -9,7 +9,9 @@
 ## Analysis Scope & Methodology
 
 ### Analysis Purpose
+
 {{Define the primary purpose:
+
 - New market entry assessment
 - Product positioning strategy
 - Feature gap analysis
@@ -18,7 +20,9 @@
 - 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
@@ -26,7 +30,9 @@
 - Aspirational Competitors: Best-in-class examples}}
 
 ### Research Methodology
+
 {{Describe approach:
+
 - Information sources used
 - Analysis timeframe
 - Confidence levels
@@ -35,7 +41,9 @@
 ## Competitive Landscape Overview
 
 ### Market Structure
+
 {{Describe the competitive environment:
+
 - Number of active competitors
 - Market concentration (fragmented/consolidated)
 - Competitive dynamics
@@ -46,6 +54,7 @@
 [[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
@@ -58,6 +67,7 @@
 ### {{Competitor Name}} - Priority {{1/2/3/4}}
 
 #### Company Overview
+
 - **Founded:** {{Year, founders}}
 - **Headquarters:** {{Location}}
 - **Company Size:** {{Employees, revenue if known}}
@@ -65,6 +75,7 @@
 - **Leadership:** {{Key executives}}
 
 #### Business Model & Strategy
+
 - **Revenue Model:** {{How they make money}}
 - **Target Market:** {{Primary customer segments}}
 - **Value Proposition:** {{Core value promise}}
@@ -72,6 +83,7 @@
 - **Strategic Focus:** {{Current priorities}}
 
 #### Product/Service Analysis
+
 - **Core Offerings:** {{Main products/services}}
 - **Key Features:** {{Standout capabilities}}
 - **User Experience:** {{UX strengths/weaknesses}}
@@ -81,16 +93,19 @@
 #### 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}}
@@ -105,7 +120,7 @@
 [[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}}     |
@@ -124,12 +139,14 @@
 [[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}}
@@ -139,6 +156,7 @@
 [[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
@@ -149,7 +167,9 @@
 ### Competitive Advantages Assessment
 
 #### Sustainable Advantages
+
 {{Identify moats and defensible positions:
+
 - Network effects
 - Switching costs
 - Brand strength
@@ -157,7 +177,9 @@
 - Regulatory advantages}}
 
 #### Vulnerable Points
+
 {{Where competitors could be challenged:
+
 - Weak customer segments
 - Missing features
 - Poor user experience
@@ -169,6 +191,7 @@
 [[LLM: Identify uncontested market spaces]]
 
 {{List opportunities to create new market space:
+
 - Underserved segments
 - Unaddressed use cases
 - New business models
@@ -178,7 +201,9 @@
 ## Strategic Recommendations
 
 ### Differentiation Strategy
+
 {{How to position against competitors:
+
 - Unique value propositions to emphasize
 - Features to prioritize
 - Segments to target
@@ -187,19 +212,25 @@
 ### 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
@@ -208,10 +239,13 @@
 ## Monitoring & Intelligence Plan
 
 ### Key Competitors to Track
+
 {{Priority list with rationale}}
 
 ### Monitoring Metrics
+
 {{What to track:
+
 - Product updates
 - Pricing changes
 - Customer wins/losses
@@ -219,7 +253,9 @@
 - Market messaging}}
 
 ### Intelligence Sources
+
 {{Where to gather ongoing intelligence:
+
 - Company websites/blogs
 - Customer reviews
 - Industry reports
@@ -227,7 +263,9 @@
 - Patent filings}}
 
 ### Update Cadence
+
 {{Recommended review schedule:
+
 - Weekly: {{What to check}}
 - Monthly: {{What to review}}
 - Quarterly: {{Deep analysis}}}}
@@ -236,8 +274,8 @@
 
 [[LLM: After completing the document, offer advanced elicitation with these custom options for competitive analysis:
 
-**Competitive Analysis Elicitation Actions**
+**Competitive Analysis Elicitation Actions** 0. Deep dive on a specific competitor's strategy
-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

.bmad-core/templates/front-end-architecture-tmpl.md

@@ -29,6 +29,7 @@
      - Routing configuration
      - Testing setup and patterns
      - Build and development scripts
+
 - 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:

.bmad-core/templates/fullstack-architecture-tmpl.md

@@ -333,10 +333,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
+
 5. Create component diagrams where helpful
 6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
 

.bmad-core/templates/market-research-tmpl.md

@@ -9,13 +9,17 @@
 ## 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
@@ -24,7 +28,9 @@
 ## Market Overview
 
 ### Market Definition
+
 {{Define the market being analyzed:
+
 - Product/service category
 - Geographic scope
 - Customer segments included
@@ -33,17 +39,21 @@
 ### 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
@@ -51,15 +61,19 @@
 [[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
@@ -69,6 +83,7 @@
 [[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}}
@@ -83,12 +98,15 @@
 [[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
@@ -96,6 +114,7 @@
 [[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
@@ -106,13 +125,17 @@
 ## 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
@@ -120,7 +143,9 @@
 - Pricing strategy}}
 
 ### Competitive Positioning
+
 {{Analyze how competitors are positioned:
+
 - Value propositions
 - Differentiation strategies
 - Market gaps and opportunities}}
@@ -132,22 +157,29 @@
 [[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}}
@@ -159,6 +191,7 @@
 [[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?}}
@@ -169,21 +202,27 @@
 ### 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
@@ -192,20 +231,23 @@
 ## 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**
+**Market Research Elicitation Actions** 0. Expand market sizing calculations with sensitivity analysis
-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

.bmad-core/templates/project-brief-tmpl.md

@@ -3,6 +3,7 @@
 [[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
 
@@ -11,6 +12,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
@@ -21,6 +23,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
@@ -31,6 +34,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
@@ -41,15 +45,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
@@ -57,16 +64,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}}
@@ -76,15 +86,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
@@ -92,12 +105,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
@@ -105,17 +121,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}}
@@ -126,12 +145,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}}
@@ -141,37 +162,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}}
@@ -184,8 +213,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**
+**Project Brief Elicitation Actions** 0. Expand section with more specific details
-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

.bmad-core/templates/web-agent-startup-instructions-template.md

@@ -7,10 +7,12 @@ 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 ====================`
 
 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
@@ -26,6 +28,7 @@ When you need to reference a resource mentioned in your instructions:
 ```
 
 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 ====================`
 

.bmad-core/utils/template-format.md

@@ -6,7 +6,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/utils/workflow-management.md

@@ -41,11 +41,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.
 ```
@@ -62,7 +62,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:
@@ -82,7 +82,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.
@@ -150,7 +150,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
@@ -173,7 +173,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.
 

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

@@ -159,13 +159,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 
 5. **SCAMPER Method**
    [[LLM: Guide through each SCAMPER prompt systematically.]]
-   - **S**ubstitute: What can be substituted?
+   - **S** = Substitute: What can be substituted?
-   - **C**ombine: What can be combined or integrated?
+   - **C** = Combine: What can be combined or integrated?
-   - **A**dapt: What can be adapted from elsewhere?
+   - **A** = Adapt: What can be adapted from elsewhere?
-   - **M**odify/Magnify: What can be emphasized or reduced?
+   - **M** = Modify/Magnify: What can be emphasized or reduced?
-   - **P**ut to other uses: What else could this be used for?
+   - **P** = Put to other uses: What else could this be used for?
-   - **E**liminate: What can be removed or simplified?
+   - **E** = Eliminate: What can be removed or simplified?
-   - **R**everse/Rearrange: What can be reversed or reordered?
+   - **R** = Reverse/Rearrange: What can be reversed or reordered?
 
 6. **Six Thinking Hats**
    [[LLM: Cycle through different thinking modes, spending focused time in each.]]
@@ -178,7 +178,8 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 
 7. **Mind Mapping**
    [[LLM: Create text-based mind maps with clear hierarchical structure.]]
-   ```
+
+   ```text
    Central Concept
    ├── Branch 1
    │   ├── Sub-idea 1.1

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

@@ -7,6 +7,7 @@ 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 ====================`
 
@@ -296,13 +297,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 
 5. **SCAMPER Method**
    [[LLM: Guide through each SCAMPER prompt systematically.]]
-   - **S**ubstitute: What can be substituted?
+   - **S** = Substitute: What can be substituted?
-   - **C**ombine: What can be combined or integrated?
+   - **C** = Combine: What can be combined or integrated?
-   - **A**dapt: What can be adapted from elsewhere?
+   - **A** = Adapt: What can be adapted from elsewhere?
-   - **M**odify/Magnify: What can be emphasized or reduced?
+   - **M** = Modify/Magnify: What can be emphasized or reduced?
-   - **P**ut to other uses: What else could this be used for?
+   - **P** = Put to other uses: What else could this be used for?
-   - **E**liminate: What can be removed or simplified?
+   - **E** = Eliminate: What can be removed or simplified?
-   - **R**everse/Rearrange: What can be reversed or reordered?
+   - **R** = Reverse/Rearrange: What can be reversed or reordered?
 
 6. **Six Thinking Hats**
    [[LLM: Cycle through different thinking modes, spending focused time in each.]]
@@ -8677,7 +8678,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]]
 

.bmad-core/web-bundles/teams/team-all.txt

@@ -7,6 +7,7 @@ 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 ====================`
 
@@ -2101,13 +2102,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 
 5. **SCAMPER Method**
    [[LLM: Guide through each SCAMPER prompt systematically.]]
-   - **S**ubstitute: What can be substituted?
+   - **S** = Substitute: What can be substituted?
-   - **C**ombine: What can be combined or integrated?
+   - **C** = Combine: What can be combined or integrated?
-   - **A**dapt: What can be adapted from elsewhere?
+   - **A** = Adapt: What can be adapted from elsewhere?
-   - **M**odify/Magnify: What can be emphasized or reduced?
+   - **M** = Modify/Magnify: What can be emphasized or reduced?
-   - **P**ut to other uses: What else could this be used for?
+   - **P** = Put to other uses: What else could this be used for?
-   - **E**liminate: What can be removed or simplified?
+   - **E** = Eliminate: What can be removed or simplified?
-   - **R**everse/Rearrange: What can be reversed or reordered?
+   - **R** = Reverse/Rearrange: What can be reversed or reordered?
 
 6. **Six Thinking Hats**
    [[LLM: Cycle through different thinking modes, spending focused time in each.]]
@@ -8455,7 +8456,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]]
 

.bmad-core/web-bundles/teams/team-fullstack.txt

@@ -7,6 +7,7 @@ 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 ====================`
 
@@ -1927,13 +1928,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 
 5. **SCAMPER Method**
    [[LLM: Guide through each SCAMPER prompt systematically.]]
-   - **S**ubstitute: What can be substituted?
+   - **S** = Substitute: What can be substituted?
-   - **C**ombine: What can be combined or integrated?
+   - **C** = Combine: What can be combined or integrated?
-   - **A**dapt: What can be adapted from elsewhere?
+   - **A** = Adapt: What can be adapted from elsewhere?
-   - **M**odify/Magnify: What can be emphasized or reduced?
+   - **M** = Modify/Magnify: What can be emphasized or reduced?
-   - **P**ut to other uses: What else could this be used for?
+   - **P** = Put to other uses: What else could this be used for?
-   - **E**liminate: What can be removed or simplified?
+   - **E** = Eliminate: What can be removed or simplified?
-   - **R**everse/Rearrange: What can be reversed or reordered?
+   - **R** = Reverse/Rearrange: What can be reversed or reordered?
 
 6. **Six Thinking Hats**
    [[LLM: Cycle through different thinking modes, spending focused time in each.]]
@@ -8652,7 +8653,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]]
 

.bmad-core/web-bundles/teams/team-no-ui.txt

@@ -7,6 +7,7 @@ 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 ====================`
 
@@ -1849,13 +1850,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 
 5. **SCAMPER Method**
    [[LLM: Guide through each SCAMPER prompt systematically.]]
-   - **S**ubstitute: What can be substituted?
+   - **S** = Substitute: What can be substituted?
-   - **C**ombine: What can be combined or integrated?
+   - **C** = Combine: What can be combined or integrated?
-   - **A**dapt: What can be adapted from elsewhere?
+   - **A** = Adapt: What can be adapted from elsewhere?
-   - **M**odify/Magnify: What can be emphasized or reduced?
+   - **M** = Modify/Magnify: What can be emphasized or reduced?
-   - **P**ut to other uses: What else could this be used for?
+   - **P** = Put to other uses: What else could this be used for?
-   - **E**liminate: What can be removed or simplified?
+   - **E** = Eliminate: What can be removed or simplified?
-   - **R**everse/Rearrange: What can be reversed or reordered?
+   - **R** = Reverse/Rearrange: What can be reversed or reordered?
 
 6. **Six Thinking Hats**
    [[LLM: Cycle through different thinking modes, spending focused time in each.]]
@@ -8099,7 +8100,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]]
 

.vscode/settings.json

@@ -2,26 +2,42 @@
 	"cSpell.words": [
 		"agentic",
 		"Axios",
+		"biomimicry",
 		"BMAD",
+		"Brainwriting",
 		"Centricity",
+		"cicd",
 		"dataclass",
 		"docstrings",
 		"emergently",
 		"explorative",
+		"fintech",
+		"firmographic",
+		"firmographics",
 		"frontends",
+		"gamedev",
 		"golint",
 		"Goroutines",
+		"hotspots",
 		"HSTS",
 		"httpx",
 		"Immer",
 		"implementability",
 		"Inclusivity",
 		"Luxon",
+		"MERN",
+		"mgmt",
+		"Nuxt",
+		"overcommitting",
 		"pasteable",
+		"pentest",
+		"PESTEL",
 		"Pino",
 		"Polyrepo",
+		"psychographics",
 		"Pydantic",
 		"pyproject",
+		"reqs",
 		"rescope",
 		"roadmaps",
 		"roleplay",
@@ -29,12 +45,28 @@
 		"Serilog",
 		"shadcn",
 		"structlog",
+		"subfolders",
+		"Supabase",
 		"Systemization",
 		"taskroot",
 		"Testcontainers",
 		"tmpl",
+		"tmplv",
+		"touchpoints",
+		"trpc",
+		"Turborepo",
+		"Underserved",
+		"unredacted",
 		"VARCHAR",
 		"venv",
-		"WCAG"
+		"vercel",
-	]
+		"Vite",
+		"WCAG",
+		"wireframes"
+	],
+	"markdownlint.config": {
+		"MD033": {
+			"allowed_elements": ["br", "div", "img", "rule", "sub"]
+		}
+	}
 }

README.md

@@ -241,4 +241,3 @@ Created by Brian (BMad) Madison
 [![Contributors](https://contrib.rocks/image?repo=bmadcode/bmad-method)](https://github.com/bmadcode/bmad-method/graphs/contributors)
 
 <sub>Built with ❤️ for the AI-assisted development community</sub>
-