feat: Update build artifacts with TDD methodology expansion pack

2025-09-02 15:29:18 +07:00 · 2025-09-02 15:29:18 +07:00 · 873ba8789c
parent 93cabd19e9
commit 873ba8789c
37 changed files with 20991 additions and 69 deletions
--- a/dist/agents/analyst.txt
+++ b/dist/agents/analyst.txt
@ -105,6 +105,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -226,6 +227,7 @@ Choose a number (0-8) or 9 to proceed:

 ==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task

 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@ -508,6 +510,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que

 ==================== START: .bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -613,6 +616,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document an Existing Project

 ## Purpose
@ -959,10 +963,11 @@ Apply the advanced elicitation task after major sections to refine based on user
 ==================== END: .bmad-core/tasks/document-project.md ====================

 ==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
-<!-- Powered by BMAD™ Core -->
---
+## <!-- Powered by BMAD™ Core -->
+
 docOutputLocation: docs/brainstorming-session-results.md
 template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
+
 ---

 # Facilitate Brainstorming Session Task
@ -2050,6 +2055,7 @@ sections:

 ==================== START: .bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMAD™ Knowledge Base

 ## Overview
@ -2860,6 +2866,7 @@ Use the **expansion-creator** pack to build your own:

 ==================== START: .bmad-core/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Brainstorming Techniques Data

 ## Creative Expansion
--- a/dist/agents/architect.txt
+++ b/dist/agents/architect.txt
@ -106,6 +106,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task

 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@ -388,6 +389,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que

 ==================== START: .bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -493,6 +495,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document an Existing Project

 ## Purpose
@ -840,6 +843,7 @@ Apply the advanced elicitation task after major sections to refine based on user

 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -3113,6 +3117,7 @@ sections:

 ==================== START: .bmad-core/checklists/architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Architect Solution Validation Checklist

 This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
@ -3555,6 +3560,7 @@ After presenting the report, ask the user if they would like detailed analysis o

 ==================== START: .bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # User-Defined Preferred Patterns and Preferences

 None Listed
--- a/dist/agents/bmad-master.txt
+++ b/dist/agents/bmad-master.txt
@ -128,6 +128,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -249,6 +250,7 @@ Choose a number (0-8) or 9 to proceed:

 ==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Brownfield Epic Task

 ## Purpose
@ -413,6 +415,7 @@ The epic creation is successful when:

 ==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Brownfield Story Task

 ## Purpose
@ -564,6 +567,7 @@ The story creation is successful when:

 ==================== START: .bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Correct Course Task

 ## Purpose
@ -638,6 +642,7 @@ The story creation is successful when:

 ==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task

 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@ -920,6 +925,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que

 ==================== START: .bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -1025,6 +1031,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-core/tasks/create-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Next Story Task

 ## Purpose
@ -1141,6 +1148,7 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`

 ==================== START: .bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document an Existing Project

 ## Purpose
@ -1488,6 +1496,7 @@ Apply the advanced elicitation task after major sections to refine based on user

 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -1577,10 +1586,11 @@ The LLM will:
 ==================== END: .bmad-core/tasks/execute-checklist.md ====================

 ==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
-<!-- Powered by BMAD™ Core -->
---
+## <!-- Powered by BMAD™ Core -->
+
 docOutputLocation: docs/brainstorming-session-results.md
 template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
+
 ---

 # Facilitate Brainstorming Session Task
@ -1718,6 +1728,7 @@ Generate structured document with these sections:

 ==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create AI Frontend Prompt Task

 ## Purpose
@ -1773,6 +1784,7 @@ You will now synthesize the inputs and the above principles into a final, compre

 ==================== START: .bmad-core/tasks/index-docs.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Index Documentation Task

 ## Purpose
@ -1950,6 +1962,7 @@ Would you like to proceed with documentation indexing? Please provide the requir

 ==================== START: .bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document Sharding Task

 ## Purpose
@ -6097,6 +6110,7 @@ sections:

 ==================== START: .bmad-core/checklists/architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Architect Solution Validation Checklist

 This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
@ -6539,6 +6553,7 @@ After presenting the report, ask the user if they would like detailed analysis o

 ==================== START: .bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Change Navigation Checklist

 **Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
@ -6725,6 +6740,7 @@ Keep it action-oriented and forward-looking.]]

 ==================== START: .bmad-core/checklists/pm-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Product Manager (PM) Requirements Checklist

 This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
@ -7099,6 +7115,7 @@ After presenting the report, ask if the user wants:

 ==================== START: .bmad-core/checklists/po-master-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Product Owner (PO) Master Validation Checklist

 This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
@ -7535,6 +7552,7 @@ After presenting the report, ask if the user wants:

 ==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Definition of Done (DoD) Checklist

 ## Instructions for Developer Agent
@ -7633,6 +7651,7 @@ Be honest - it's better to flag issues now than have them discovered later.]]

 ==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Draft Checklist

 The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
@ -7790,6 +7809,7 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro

 ==================== START: .bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMAD™ Knowledge Base

 ## Overview
@ -8600,6 +8620,7 @@ Use the **expansion-creator** pack to build your own:

 ==================== START: .bmad-core/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Brainstorming Techniques Data

 ## Creative Expansion
@ -8640,6 +8661,7 @@ Use the **expansion-creator** pack to build your own:

 ==================== START: .bmad-core/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Elicitation Methods Data

 ## Core Reflective Methods
@ -8798,6 +8820,7 @@ Use the **expansion-creator** pack to build your own:

 ==================== START: .bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # User-Defined Preferred Patterns and Preferences

 None Listed
--- a/dist/agents/bmad-orchestrator.txt
+++ b/dist/agents/bmad-orchestrator.txt
@ -168,6 +168,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -289,6 +290,7 @@ Choose a number (0-8) or 9 to proceed:

 ==================== START: .bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -394,6 +396,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # KB Mode Interaction Task

 ## Purpose
@ -473,6 +476,7 @@ Or ask me about anything else related to BMad-Method!

 ==================== START: .bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMAD™ Knowledge Base

 ## Overview
@ -1283,6 +1287,7 @@ Use the **expansion-creator** pack to build your own:

 ==================== START: .bmad-core/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Elicitation Methods Data

 ## Core Reflective Methods
@ -1441,6 +1446,7 @@ Use the **expansion-creator** pack to build your own:

 ==================== START: .bmad-core/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Workflow Management

 Enables BMad orchestrator to manage and execute team workflows.
--- a/dist/agents/dev.txt
+++ b/dist/agents/dev.txt
@ -55,18 +55,22 @@ agent:
  id: dev
  title: Full Stack Developer
  icon: 💻
-  whenToUse: Use for code implementation, debugging, refactoring, and development best practices
+  whenToUse: Use for code implementation, debugging, refactoring, Test-Driven Development (TDD) Green/Refactor phases, and development best practices
  customization: null
 persona:
  role: Expert Senior Software Engineer & Implementation Specialist
  style: Extremely concise, pragmatic, detail-oriented, solution-focused
-  identity: Expert who implements stories by reading requirements and executing tasks sequentially with comprehensive testing
-  focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
+  identity: Expert who implements stories by reading requirements and executing tasks sequentially with comprehensive testing. Practices Test-Driven Development when enabled.
+  focus: Executing story tasks with precision, TDD Green/Refactor phase execution, updating Dev Agent Record sections only, maintaining minimal context overhead
 core_principles:
  - CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
+  - CRITICAL: ALWAYS check current folder structure before starting your story tasks, don't create new working directory if it already exists. Create new one when you're sure it's a brand new project.
  - CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
  - CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
  - Numbered Options - Always use numbered lists when presenting choices to the user
+  - TDD Discipline - When TDD enabled, implement minimal code to pass failing tests (Green phase)
+  - Test-First Validation - Never implement features without corresponding failing tests in TDD mode
+  - Refactoring Safety - Collaborate with QA during refactor phase, keep all tests green
 commands:
  - help: Show numbered list of the following commands to allow selection
  - develop-story:
@ -75,9 +79,23 @@ commands:
          - CRITICAL: ONLY UPDATE THE STORY FILE WITH UPDATES TO SECTIONS INDICATED BELOW. DO NOT MODIFY ANY OTHER SECTIONS.
          - CRITICAL: You are ONLY authorized to edit these specific sections of story files - Tasks / Subtasks Checkboxes, Dev Agent Record section and all its subsections, Agent Model Used, Debug Log References, Completion Notes List, File List, Change Log, Status
          - CRITICAL: DO NOT modify Status, Story, Acceptance Criteria, Dev Notes, Testing sections, or any other sections not listed above
-      - blocking: 'HALT for: Unapproved deps needed, confirm with user | Ambiguous after story check | 3 failures attempting to implement or fix something repeatedly | Missing config | Failing regression'
+      - blocking: 'HALT for: Unapproved deps needed, confirm with user | 3 failures attempting to implement or fix something repeatedly | Missing config | Failing regression'
      - ready-for-review: Code matches requirements + All validations pass + Follows standards + File List complete
      - completion: 'All Tasks and Subtasks marked [x] and have tests→Validations and full regression passes (DON''T BE LAZY, EXECUTE ALL TESTS and CONFIRM)→Ensure File List is Complete→run the task execute-checklist for the checklist story-dod-checklist→set story status: ''Ready for Review''→HALT'
+  - tdd-implement {story}: |
+      Execute tdd-implement task for TDD Green phase.
+      Implement minimal code to make failing tests pass. No feature creep.
+      Prerequisites: Story has failing tests (tdd.status='red'), test runner configured.
+      Outcome: All tests pass, story tdd.status='green', ready for refactor assessment.
+  - make-tests-pass {story}: |
+      Iterative command to run tests and implement fixes until all tests pass.
+      Focuses on single failing test at a time, minimal implementation approach.
+      Auto-runs tests after each change, provides fast feedback loop.
+  - tdd-refactor {story}: |
+      Collaborate with QA agent on TDD Refactor phase.
+      Improve code quality while keeping all tests green.
+      Prerequisites: All tests passing (tdd.status='green').
+      Outcome: Improved code quality, tests remain green, tdd.status='refactor' or 'done'.
  - explain: teach me what and why you did whatever you just did in detail so I can learn. Explain to me as if you were training a junior engineer.
  - review-qa: run task `apply-qa-fixes.md'
  - run-tests: Execute linting and tests
@ -85,15 +103,24 @@ commands:
 dependencies:
  checklists:
    - story-dod-checklist.md
+    - tdd-dod-checklist.md
  tasks:
    - apply-qa-fixes.md
    - execute-checklist.md
    - validate-next-story.md
+    - tdd-implement.md
+    - tdd-refactor.md
+  prompts:
+    - tdd-green.md
+    - tdd-refactor.md
+  config:
+    - test-runners.yaml
 ```
 ==================== END: .bmad-core/agents/dev.md ====================

 ==================== START: .bmad-core/tasks/apply-qa-fixes.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # apply-qa-fixes

 Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.
@ -246,6 +273,7 @@ Fix plan:

 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -336,6 +364,7 @@ The LLM will:

 ==================== START: .bmad-core/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Validate Next Story Task

 ## Purpose
@ -472,8 +501,709 @@ Provide a structured validation report including:
 - **Confidence Level**: High/Medium/Low for successful implementation
 ==================== END: .bmad-core/tasks/validate-next-story.md ====================

+==================== START: .bmad-core/tasks/tdd-implement.md ====================
+<!-- Powered by BMAD™ Core -->
+
+# tdd-implement
+
+Implement minimal code to make failing tests pass - the "Green" phase of TDD.
+
+## Purpose
+
+Write the simplest possible implementation that makes all failing tests pass. This is the "Green" phase of TDD where we focus on making tests pass with minimal, clean code.
+
+## Prerequisites
+
+- Story has failing tests (tdd.status: red)
+- All tests fail for correct reasons (missing implementation, not bugs)
+- Test runner is configured and working
+- Dev agent has reviewed failing tests and acceptance criteria
+
+## Inputs
+
+```yaml
+required:
+  - story_id: '{epic}.{story}' # e.g., "1.3"
+  - story_path: '{devStoryLocation}/{epic}.{story}.*.md' # Path from core-config.yaml
+  - failing_tests: # List from story TDD metadata
+      - id: test identifier
+      - file_path: path to test file
+      - status: failing
+```
+
+## Process
+
+### 1. Review Failing Tests
+
+Before writing any code:
+
+- Read each failing test to understand expected behavior
+- Identify the interfaces/classes/functions that need to be created
+- Note expected inputs, outputs, and error conditions
+- Understand the test's mocking strategy
+
+### 2. Design Minimal Implementation
+
+**TDD Green Phase Principles:**
+
+- **Make it work first, then make it right**
+- **Simplest thing that could possibly work**
+- **No feature without a failing test**
+- **Avoid premature abstraction**
+- **Prefer duplication over wrong abstraction**
+
+### 3. Implement Code
+
+**Implementation Strategy:**
+
+```yaml
+approach: 1. Start with simplest happy path test
+  2. Write minimal code to pass that test
+  3. Run tests frequently (after each small change)
+  4. Move to next failing test
+  5. Repeat until all tests pass
+
+avoid:
+  - Adding features not covered by tests
+  - Complex algorithms when simple ones suffice
+  - Premature optimization
+  - Over-engineering the solution
+```
+
+**Example Implementation Progression:**
+
+```javascript
+// First test: should return user with id
+// Minimal implementation:
+function createUser(userData) {
+  return { id: 1, ...userData };
+}
+
+// Second test: should validate email format
+// Expand implementation:
+function createUser(userData) {
+  if (!userData.email.includes('@')) {
+    throw new Error('Invalid email format');
+  }
+  return { id: 1, ...userData };
+}
+```
+
+### 4. Run Tests Continuously
+
+**Test-Driven Workflow:**
+
+1. Run specific failing test
+2. Write minimal code to make it pass
+3. Run that test again to confirm green
+4. Run full test suite to ensure no regressions
+5. Move to next failing test
+
+**Test Execution Commands:**
+
+```bash
+# Run specific test file
+npm test -- user-service.test.js
+pytest tests/unit/test_user_service.py
+go test ./services/user_test.go
+
+# Run full test suite
+npm test
+pytest
+go test ./...
+```
+
+### 5. Handle Edge Cases
+
+Implement only edge cases that have corresponding tests:
+
+- Input validation as tested
+- Error conditions as specified in tests
+- Boundary conditions covered by tests
+- Nothing more, nothing less
+
+### 6. Maintain Test-Code Traceability
+
+**Commit Strategy:**
+
+```bash
+git add tests/ src/
+git commit -m "GREEN: Implement user creation [UC-001, UC-002]"
+```
+
+Link implementation to specific test IDs in commits for traceability.
+
+### 7. Update Story Metadata
+
+Update TDD status to green:
+
+```yaml
+tdd:
+  status: green
+  cycle: 1
+  tests:
+    - id: 'UC-001'
+      name: 'should create user with valid email'
+      type: unit
+      status: passing
+      file_path: 'tests/unit/user-service.test.js'
+    - id: 'UC-002'
+      name: 'should reject user with invalid email'
+      type: unit
+      status: passing
+      file_path: 'tests/unit/user-service.test.js'
+```
+
+## Output Requirements
+
+### 1. Working Implementation
+
+Create source files that:
+
+- Make all failing tests pass
+- Follow project coding standards
+- Are minimal and focused
+- Have clear, intention-revealing names
+
+### 2. Test Execution Report
+
+```bash
+Running tests...
+✅ UserService > should create user with valid email
+✅ UserService > should reject user with invalid email
+
+2 passing, 0 failing
+```
+
+### 3. Story File Updates
+
+Append to TDD section:
+
+```markdown
+## TDD Progress
+
+### Green Phase - Cycle 1
+
+**Date:** {current_date}
+**Agent:** James (Dev Agent)
+
+**Implementation Summary:**
+
+- Created UserService class with create() method
+- Added email validation for @ symbol
+- All tests now passing ✅
+
+**Files Modified:**
+
+- src/services/user-service.js (created)
+
+**Test Results:**
+
+- UC-001: should create user with valid email (PASSING ✅)
+- UC-002: should reject user with invalid email (PASSING ✅)
+
+**Next Step:** Review implementation for refactoring opportunities
+```
+
+## Implementation Guidelines
+
+### Code Quality Standards
+
+**During Green Phase:**
+
+- **Readable:** Clear variable and function names
+- **Simple:** Avoid complex logic when simple works
+- **Testable:** Code structure supports the tests
+- **Focused:** Each function has single responsibility
+
+**Acceptable Technical Debt (to be addressed in Refactor phase):**
+
+- Code duplication if it keeps tests green
+- Hardcoded values if they make tests pass
+- Simple algorithms even if inefficient
+- Minimal error handling beyond what tests require
+
+### Common Patterns
+
+**Factory Functions:**
+
+```javascript
+function createUser(data) {
+  // Minimal validation
+  return { id: generateId(), ...data };
+}
+```
+
+**Error Handling:**
+
+```javascript
+function validateEmail(email) {
+  if (!email.includes('@')) {
+    throw new Error('Invalid email');
+  }
+}
+```
+
+**State Management:**
+
+```javascript
+class UserService {
+  constructor(database) {
+    this.db = database; // Accept injected dependency
+  }
+}
+```
+
+## Error Handling
+
+**If tests still fail after implementation:**
+
+- Review test expectations vs actual implementation
+- Check for typos in function/method names
+- Verify correct imports/exports
+- Ensure proper handling of async operations
+
+**If tests pass unexpectedly without changes:**
+
+- Implementation might already exist
+- Test might be incorrect
+- Review git status for unexpected changes
+
+**If new tests start failing:**
+
+- Implementation may have broken existing functionality
+- Review change impact
+- Fix regressions before continuing
+
+## Anti-Patterns to Avoid
+
+**Feature Creep:**
+
+- Don't implement features without failing tests
+- Don't add "obviously needed" functionality
+
+**Premature Optimization:**
+
+- Don't optimize for performance in green phase
+- Focus on correctness first
+
+**Over-Engineering:**
+
+- Don't add abstraction layers without tests requiring them
+- Avoid complex design patterns in initial implementation
+
+## Completion Criteria
+
+- [ ] All previously failing tests now pass
+- [ ] No existing tests broken (regression check)
+- [ ] Implementation is minimal and focused
+- [ ] Code follows project standards
+- [ ] Story TDD status updated to 'green'
+- [ ] Files properly committed with test traceability
+- [ ] Ready for refactor phase assessment
+
+## Validation Commands
+
+```bash
+# Verify all tests pass
+npm test
+pytest
+go test ./...
+mvn test
+dotnet test
+
+# Check code quality (basic)
+npm run lint
+flake8 .
+golint ./...
+```
+
+## Key Principles
+
+- **Make it work:** Green tests are the only measure of success
+- **Keep it simple:** Resist urge to make it elegant yet
+- **One test at a time:** Focus on single failing test
+- **Fast feedback:** Run tests frequently during development
+- **No speculation:** Only implement what tests require
+==================== END: .bmad-core/tasks/tdd-implement.md ====================
+
+==================== START: .bmad-core/tasks/tdd-refactor.md ====================
+<!-- Powered by BMAD™ Core -->
+
+# tdd-refactor
+
+Safely refactor code while keeping all tests green - the "Refactor" phase of TDD.
+
+## Purpose
+
+Improve code quality, eliminate duplication, and enhance design while maintaining all existing functionality. This is the "Refactor" phase of TDD where we make the code clean and maintainable.
+
+## Prerequisites
+
+- All tests are passing (tdd.status: green)
+- Implementation is complete and functional
+- Test suite provides safety net for refactoring
+- Code follows basic project standards
+
+## Inputs
+
+```yaml
+required:
+  - story_id: '{epic}.{story}' # e.g., "1.3"
+  - story_path: '{devStoryLocation}/{epic}.{story}.*.md' # Path from core-config.yaml
+  - passing_tests: # All tests should be green
+      - id: test identifier
+      - status: passing
+  - implementation_files: # Source files to potentially refactor
+      - path: file path
+      - purpose: what it does
+```
+
+## Process
+
+### 1. Identify Refactoring Opportunities
+
+**Code Smells to Look For:**
+
+```yaml
+common_smells:
+  duplication:
+    - Repeated code blocks
+    - Similar logic in different places
+    - Copy-paste patterns
+
+  complexity:
+    - Long methods/functions (>10-15 lines)
+    - Too many parameters (>3-4)
+    - Nested conditions (>2-3 levels)
+    - Complex boolean expressions
+
+  naming:
+    - Unclear variable names
+    - Non-descriptive function names
+    - Inconsistent naming conventions
+
+  structure:
+    - God objects/classes doing too much
+    - Primitive obsession
+    - Feature envy (method using more from other class)
+    - Long parameter lists
+```
+
+### 2. Plan Refactoring Steps
+
+**Refactoring Strategy:**
+
+- **One change at a time:** Make small, atomic improvements
+- **Run tests after each change:** Ensure no functionality breaks
+- **Commit frequently:** Create checkpoints for easy rollback
+- **Improve design:** Move toward better architecture
+
+**Common Refactoring Techniques:**
+
+```yaml
+extract_methods:
+  when: 'Function is too long or doing multiple things'
+  technique: 'Extract complex logic into named methods'
+
+rename_variables:
+  when: "Names don't clearly express intent"
+  technique: 'Use intention-revealing names'
+
+eliminate_duplication:
+  when: 'Same code appears in multiple places'
+  technique: 'Extract to shared function/method'
+
+simplify_conditionals:
+  when: 'Complex boolean logic is hard to understand'
+  technique: 'Extract to well-named boolean methods'
+
+introduce_constants:
+  when: 'Magic numbers or strings appear repeatedly'
+  technique: 'Create named constants'
+```
+
+### 3. Execute Refactoring
+
+**Step-by-Step Process:**
+
+1. **Choose smallest improvement**
+2. **Make the change**
+3. **Run all tests**
+4. **Commit if green**
+5. **Repeat**
+
+**Example Refactoring Sequence:**
+
+```javascript
+// Before refactoring
+function createUser(data) {
+  if (!data.email.includes('@') || data.email.length < 5) {
+    throw new Error('Invalid email format');
+  }
+  if (!data.name || data.name.trim().length === 0) {
+    throw new Error('Name is required');
+  }
+  return {
+    id: Math.floor(Math.random() * 1000000),
+    ...data,
+    createdAt: new Date().toISOString(),
+  };
+}
+
+// After refactoring - Step 1: Extract validation
+function validateEmail(email) {
+  return email.includes('@') && email.length >= 5;
+}
+
+function validateName(name) {
+  return name && name.trim().length > 0;
+}
+
+function createUser(data) {
+  if (!validateEmail(data.email)) {
+    throw new Error('Invalid email format');
+  }
+  if (!validateName(data.name)) {
+    throw new Error('Name is required');
+  }
+  return {
+    id: Math.floor(Math.random() * 1000000),
+    ...data,
+    createdAt: new Date().toISOString(),
+  };
+}
+
+// After refactoring - Step 2: Extract ID generation
+function generateUserId() {
+  return Math.floor(Math.random() * 1000000);
+}
+
+function createUser(data) {
+  if (!validateEmail(data.email)) {
+    throw new Error('Invalid email format');
+  }
+  if (!validateName(data.name)) {
+    throw new Error('Name is required');
+  }
+  return {
+    id: generateUserId(),
+    ...data,
+    createdAt: new Date().toISOString(),
+  };
+}
+```
+
+### 4. Test After Each Change
+
+**Critical Rule:** Never proceed without green tests
+
+```bash
+# Run tests after each refactoring step
+npm test
+pytest
+go test ./...
+
+# If tests fail:
+# 1. Undo the change
+# 2. Understand what broke
+# 3. Try smaller refactoring
+# 4. Fix tests if they need updating (rare)
+```
+
+### 5. Collaborate with QA Agent
+
+**When to involve QA:**
+
+- Tests need updating due to interface changes
+- New test cases identified during refactoring
+- Questions about test coverage adequacy
+- Validation of refactoring safety
+
+### 6. Update Story Documentation
+
+Track refactoring progress:
+
+```yaml
+tdd:
+  status: refactor # or done if complete
+  cycle: 1
+  refactoring_notes:
+    - extracted_methods: ['validateEmail', 'validateName', 'generateUserId']
+    - eliminated_duplication: 'Email validation logic'
+    - improved_readability: 'Function names now express intent'
+```
+
+## Output Requirements
+
+### 1. Improved Code Quality
+
+**Measurable Improvements:**
+
+- Reduced code duplication
+- Clearer naming and structure
+- Smaller, focused functions
+- Better separation of concerns
+
+### 2. Maintained Test Coverage
+
+```bash
+# All tests still passing
+✅ UserService > should create user with valid email
+✅ UserService > should reject user with invalid email
+✅ UserService > should require valid name
+
+3 passing, 0 failing
+```
+
+### 3. Story File Updates
+
+Append to TDD section:
+
+```markdown
+## TDD Progress
+
+### Refactor Phase - Cycle 1
+
+**Date:** {current_date}
+**Agents:** James (Dev) & Quinn (QA)
+
+**Refactoring Completed:**
+
+- ✅ Extracted validation functions for better readability
+- ✅ Eliminated duplicate email validation logic
+- ✅ Introduced generateUserId() for testability
+- ✅ Simplified createUser() main logic
+
+**Code Quality Improvements:**
+
+- Function length reduced from 12 to 6 lines
+- Three reusable validation functions created
+- Magic numbers eliminated
+- Test coverage maintained at 100%
+
+**Files Modified:**
+
+- src/services/user-service.js (refactored)
+
+**All Tests Passing:** ✅
+
+**Next Step:** Story ready for review or next TDD cycle
+```
+
+## Refactoring Guidelines
+
+### Safe Refactoring Practices
+
+**Always Safe:**
+
+- Rename variables/functions
+- Extract methods
+- Inline temporary variables
+- Replace magic numbers with constants
+
+**Potentially Risky:**
+
+- Changing method signatures
+- Modifying class hierarchies
+- Altering error handling
+- Changing async/sync behavior
+
+**Never Do During Refactor:**
+
+- Add new features
+- Change external behavior
+- Remove existing functionality
+- Skip running tests
+
+### Code Quality Metrics
+
+**Before/After Comparison:**
+
+```yaml
+metrics_to_track:
+  cyclomatic_complexity: 'Lower is better'
+  function_length: 'Shorter is generally better'
+  duplication_percentage: 'Should decrease'
+  test_coverage: 'Should maintain 100%'
+
+acceptable_ranges:
+  function_length: '5-15 lines for most functions'
+  parameters: '0-4 parameters per function'
+  nesting_depth: 'Maximum 3 levels'
+```
+
+## Advanced Refactoring Techniques
+
+### Design Pattern Introduction
+
+**When appropriate:**
+
+- Template Method for algorithmic variations
+- Strategy Pattern for behavior selection
+- Factory Pattern for object creation
+- Observer Pattern for event handling
+
+**Caution:** Only introduce patterns if they simplify the code
+
+### Architecture Improvements
+
+```yaml
+layering:
+  - Separate business logic from presentation
+  - Extract data access concerns
+  - Isolate external dependencies
+
+dependency_injection:
+  - Make dependencies explicit
+  - Enable easier testing
+  - Improve modularity
+
+error_handling:
+  - Consistent error types
+  - Meaningful error messages
+  - Proper error propagation
+```
+
+## Error Handling
+
+**If tests fail during refactoring:**
+
+1. **Undo immediately** - Use git to revert
+2. **Analyze the failure** - What assumption was wrong?
+3. **Try smaller steps** - More atomic refactoring
+4. **Consider test updates** - Only if interface must change
+
+**If code becomes more complex:**
+
+- Refactoring went wrong direction
+- Revert and try different approach
+- Consider if change is actually needed
+
+## Completion Criteria
+
+- [ ] All identified code smells addressed or documented
+- [ ] All tests remain green throughout process
+- [ ] Code is more readable and maintainable
+- [ ] No new functionality added during refactoring
+- [ ] Story TDD status updated appropriately
+- [ ] Refactoring changes committed with clear messages
+- [ ] Code quality metrics improved or maintained
+- [ ] Ready for story completion or next TDD cycle
+
+## Key Principles
+
+- **Green Bar:** Never proceed with failing tests
+- **Small Steps:** Make incremental improvements
+- **Behavior Preservation:** External behavior must remain identical
+- **Frequent Commits:** Create rollback points
+- **Test First:** Let tests guide refactoring safety
+- **Collaborative:** Work with QA when test updates needed
+==================== END: .bmad-core/tasks/tdd-refactor.md ====================
+
 ==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Definition of Done (DoD) Checklist

 ## Instructions for Developer Agent
@ -569,3 +1299,194 @@ Be honest - it's better to flag issues now than have them discovered later.]]

 - [ ] I, the Developer Agent, confirm that all applicable items above have been addressed.
 ==================== END: .bmad-core/checklists/story-dod-checklist.md ====================
+
+==================== START: .bmad-core/checklists/tdd-dod-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
+
+# TDD Story Definition of Done Checklist
+
+## Instructions for Agents
+
+This checklist ensures TDD stories meet quality standards across all Red-Green-Refactor cycles. Both QA and Dev agents should validate completion before marking a story as Done.
+
+[[LLM: TDD DOD VALIDATION INSTRUCTIONS
+
+This is a specialized DoD checklist for Test-Driven Development stories. It extends the standard DoD with TDD-specific quality gates.
+
+EXECUTION APPROACH:
+
+1. Verify TDD cycle progression (Red → Green → Refactor → Done)
+2. Validate test-first approach was followed
+3. Ensure proper test isolation and determinism
+4. Check code quality improvements from refactoring
+5. Confirm coverage targets are met
+
+CRITICAL: Never mark a TDD story as Done without completing all TDD phases.]]
+
+## TDD Cycle Validation
+
+### Red Phase Completion
+
+[[LLM: Verify tests were written BEFORE implementation]]
+
+- [ ] **Tests written first:** All tests were created before any implementation code
+- [ ] **Failing correctly:** Tests fail for the right reasons (missing functionality, not bugs)
+- [ ] **Proper test structure:** Tests follow Given-When-Then or Arrange-Act-Assert patterns
+- [ ] **Deterministic tests:** No random values, network calls, or time dependencies
+- [ ] **External dependencies mocked:** All external services, databases, APIs properly mocked
+- [ ] **Test naming:** Clear, descriptive test names that express intent
+- [ ] **Story metadata updated:** TDD status set to 'red' and test list populated
+
+### Green Phase Completion
+
+[[LLM: Ensure minimal implementation that makes tests pass]]
+
+- [ ] **All tests passing:** 100% of tests pass consistently
+- [ ] **Minimal implementation:** Only code necessary to make tests pass was written
+- [ ] **No feature creep:** No functionality added without corresponding failing tests
+- [ ] **Test-code traceability:** Implementation clearly addresses specific test requirements
+- [ ] **Regression protection:** All previously passing tests remain green
+- [ ] **Story metadata updated:** TDD status set to 'green' and test results documented
+
+### Refactor Phase Completion
+
+[[LLM: Verify code quality improvements while maintaining green tests]]
+
+- [ ] **Tests remain green:** All tests continue to pass after refactoring
+- [ ] **Code quality improved:** Duplication eliminated, naming improved, structure clarified
+- [ ] **Design enhanced:** Better separation of concerns, cleaner interfaces
+- [ ] **Technical debt addressed:** Known code smells identified and resolved
+- [ ] **Commit discipline:** Small, incremental commits with green tests after each
+- [ ] **Story metadata updated:** Refactoring notes and improvements documented
+
+## Test Quality Standards
+
+### Test Implementation Quality
+
+[[LLM: Ensure tests are maintainable and reliable]]
+
+- [ ] **Fast execution:** Unit tests complete in <100ms each
+- [ ] **Isolated tests:** Each test can run independently in any order
+- [ ] **Single responsibility:** Each test validates one specific behavior
+- [ ] **Clear assertions:** Test failures provide meaningful error messages
+- [ ] **Appropriate test types:** Right mix of unit/integration/e2e tests
+- [ ] **Mock strategy:** Appropriate use of mocks vs fakes vs stubs
+
+### Coverage and Completeness
+
+[[LLM: Validate comprehensive test coverage]]
+
+- [ ] **Coverage target met:** Code coverage meets story's target percentage
+- [ ] **Acceptance criteria covered:** All ACs have corresponding tests
+- [ ] **Edge cases tested:** Boundary conditions and error scenarios included
+- [ ] **Happy path validated:** Primary success scenarios thoroughly tested
+- [ ] **Error handling tested:** Exception paths and error recovery validated
+
+## Implementation Quality
+
+### Code Standards Compliance
+
+[[LLM: Ensure production-ready code quality]]
+
+- [ ] **Coding standards followed:** Code adheres to project style guidelines
+- [ ] **Architecture alignment:** Implementation follows established patterns
+- [ ] **Security practices:** Input validation, error handling, no hardcoded secrets
+- [ ] **Performance considerations:** No obvious performance bottlenecks introduced
+- [ ] **Documentation updated:** Code comments and documentation reflect changes
+
+### File Organization and Management
+
+[[LLM: Verify proper project structure]]
+
+- [ ] **Test file organization:** Tests follow project's testing folder structure
+- [ ] **Naming conventions:** Files and functions follow established patterns
+- [ ] **Dependencies managed:** New dependencies properly declared and justified
+- [ ] **Import/export clarity:** Clear module interfaces and dependencies
+- [ ] **File list accuracy:** All created/modified files documented in story
+
+## TDD Process Adherence
+
+### Methodology Compliance
+
+[[LLM: Confirm true TDD practice was followed]]
+
+- [ ] **Test-first discipline:** No implementation code written before tests
+- [ ] **Minimal cycles:** Small Red-Green-Refactor iterations maintained
+- [ ] **Refactoring safety:** Only refactored with green test coverage
+- [ ] **Requirements traceability:** Clear mapping from tests to acceptance criteria
+- [ ] **Collaboration evidence:** QA and Dev agent coordination documented
+
+### Documentation and Traceability
+
+[[LLM: Ensure proper tracking and communication]]
+
+- [ ] **TDD progress tracked:** Story shows progression through all TDD phases
+- [ ] **Test execution logged:** Evidence of test runs and results captured
+- [ ] **Refactoring documented:** Changes made during refactor phase explained
+- [ ] **Agent collaboration:** Clear handoffs between QA (Red) and Dev (Green/Refactor)
+- [ ] **Story metadata complete:** All TDD fields properly populated
+
+## Integration and Deployment Readiness
+
+### Build and Deployment
+
+[[LLM: Ensure story integrates properly with project]]
+
+- [ ] **Project builds successfully:** Code compiles without errors or warnings
+- [ ] **All tests pass in CI:** Automated test suite runs successfully
+- [ ] **No breaking changes:** Existing functionality remains intact
+- [ ] **Environment compatibility:** Code works across development environments
+- [ ] **Configuration managed:** Any new config values properly documented
+
+### Review Readiness
+
+[[LLM: Story is ready for peer review]]
+
+- [ ] **Complete implementation:** All acceptance criteria fully implemented
+- [ ] **Clean commit history:** Clear, logical progression of changes
+- [ ] **Review artifacts:** All necessary files and documentation available
+- [ ] **No temporary code:** Debug code, TODOs, and temporary hacks removed
+- [ ] **Quality gates passed:** All automated quality checks successful
+
+## Final TDD Validation
+
+### Holistic Assessment
+
+[[LLM: Overall TDD process and outcome validation]]
+
+- [ ] **TDD value delivered:** Process improved code design and quality
+- [ ] **Test suite value:** Tests provide reliable safety net for changes
+- [ ] **Knowledge captured:** Future developers can understand and maintain code
+- [ ] **Standards elevated:** Code quality meets or exceeds project standards
+- [ ] **Learning documented:** Any insights or patterns discovered are captured
+
+### Story Completion Criteria
+
+[[LLM: Final checklist before marking Done]]
+
+- [ ] **Business value delivered:** Story provides promised user value
+- [ ] **Technical debt managed:** Any remaining debt is documented and acceptable
+- [ ] **Future maintainability:** Code can be easily modified and extended
+- [ ] **Production readiness:** Code is ready for production deployment
+- [ ] **TDD story complete:** All TDD-specific requirements fulfilled
+
+## Completion Declaration
+
+**Agent Validation:**
+
+- [ ] **QA Agent confirms:** Test strategy executed successfully, coverage adequate
+- [ ] **Dev Agent confirms:** Implementation complete, code quality satisfactory
+
+**Final Status:**
+
+- [ ] **Story marked Done:** All DoD criteria met and verified
+- [ ] **TDD status complete:** Story TDD metadata shows 'done' status
+- [ ] **Ready for review:** Story package complete for stakeholder review
+
+---
+
+**Validation Date:** {date}  
+**Validating Agents:** {qa_agent} & {dev_agent}  
+**TDD Cycles Completed:** {cycle_count}  
+**Final Test Status:** {passing_count} passing, {failing_count} failing
+==================== END: .bmad-core/checklists/tdd-dod-checklist.md ====================
--- a/dist/agents/pm.txt
+++ b/dist/agents/pm.txt
@ -105,6 +105,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Brownfield Epic Task

 ## Purpose
@ -269,6 +270,7 @@ The epic creation is successful when:

 ==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Brownfield Story Task

 ## Purpose
@ -420,6 +422,7 @@ The story creation is successful when:

 ==================== START: .bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Correct Course Task

 ## Purpose
@ -494,6 +497,7 @@ The story creation is successful when:

 ==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task

 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@ -776,6 +780,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que

 ==================== START: .bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -881,6 +886,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -971,6 +977,7 @@ The LLM will:

 ==================== START: .bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document Sharding Task

 ## Purpose
@ -1650,6 +1657,7 @@ sections:

 ==================== START: .bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Change Navigation Checklist

 **Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
@ -1836,6 +1844,7 @@ Keep it action-oriented and forward-looking.]]

 ==================== START: .bmad-core/checklists/pm-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Product Manager (PM) Requirements Checklist

 This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
@ -2210,6 +2219,7 @@ After presenting the report, ask if the user wants:

 ==================== START: .bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # User-Defined Preferred Patterns and Preferences

 None Listed
--- a/dist/agents/po.txt
+++ b/dist/agents/po.txt
@ -100,6 +100,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Correct Course Task

 ## Purpose
@ -174,6 +175,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -264,6 +266,7 @@ The LLM will:

 ==================== START: .bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document Sharding Task

 ## Purpose
@ -453,6 +456,7 @@ Document sharded successfully:

 ==================== START: .bmad-core/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Validate Next Story Task

 ## Purpose
@ -732,6 +736,7 @@ sections:

 ==================== START: .bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Change Navigation Checklist

 **Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
@ -918,6 +923,7 @@ Keep it action-oriented and forward-looking.]]

 ==================== START: .bmad-core/checklists/po-master-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Product Owner (PO) Master Validation Checklist

 This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
--- a/dist/agents/qa.txt
+++ b/dist/agents/qa.txt
--- a/dist/agents/sm.txt
+++ b/dist/agents/sm.txt
@ -86,6 +86,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Correct Course Task

 ## Purpose
@ -160,6 +161,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/create-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Next Story Task

 ## Purpose
@ -276,6 +278,7 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`

 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -507,6 +510,7 @@ sections:

 ==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Draft Checklist

 The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
--- a/dist/agents/ux-expert.txt
+++ b/dist/agents/ux-expert.txt
@ -90,6 +90,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -195,6 +196,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -285,6 +287,7 @@ The LLM will:

 ==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create AI Frontend Prompt Task

 ## Purpose
@ -693,6 +696,7 @@ sections:

 ==================== START: .bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # User-Defined Preferred Patterns and Preferences

 None Listed
--- a/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt
+++ b/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt
@ -96,6 +96,7 @@ dependencies:

 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -201,6 +202,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -291,6 +293,7 @@ The LLM will:

 ==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Brainstorming Techniques Task

 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@ -585,6 +588,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques

 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task

 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@ -867,6 +871,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que

 ==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Game Design Elicitation Task

 ## Purpose
@ -2176,6 +2181,7 @@ sections:

 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Document Quality Checklist

 ## Document Completeness
--- a/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt
+++ b/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt
@ -103,6 +103,7 @@ dependencies:

 ==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -810,6 +811,7 @@ sections:

 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Story Definition of Done Checklist

 ## Story Completeness
@ -974,6 +976,7 @@ _Any specific concerns, recommendations, or clarifications needed before develop

 ==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Guidelines

 ## Overview
--- a/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt
+++ b/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt
@ -89,6 +89,7 @@ dependencies:

 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Game Development Story Task

 ## Purpose
@ -309,6 +310,7 @@ This task ensures game development stories are immediately actionable and enable

 ==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -656,6 +658,7 @@ sections:

 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Story Definition of Done Checklist

 ## Story Completeness
--- a/dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt
+++ b/dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt
@ -414,6 +414,7 @@ dependencies:

 ==================== START: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development BMad Knowledge Base

 ## Overview
@ -668,6 +669,7 @@ This knowledge base provides the foundation for effective game development using

 ==================== START: .bmad-2d-phaser-game-dev/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Brainstorming Techniques Data

 ## Creative Expansion
@ -708,6 +710,7 @@ This knowledge base provides the foundation for effective game development using

 ==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Game Design Elicitation Task

 ## Purpose
@ -822,6 +825,7 @@ The questions and perspectives offered should always consider:

 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task

 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@ -1104,6 +1108,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que

 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -1209,6 +1214,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-2d-phaser-game-dev/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document an Existing Project

 ## Purpose
@ -1555,10 +1561,11 @@ Apply the advanced elicitation task after major sections to refine based on user
 ==================== END: .bmad-2d-phaser-game-dev/tasks/document-project.md ====================

 ==================== START: .bmad-2d-phaser-game-dev/tasks/facilitate-brainstorming-session.md ====================
-<!-- Powered by BMAD™ Core -->
---
+## <!-- Powered by BMAD™ Core -->
+
 docOutputLocation: docs/brainstorming-session-results.md
 template: '.bmad-2d-phaser-game-dev/templates/brainstorming-output-tmpl.yaml'
+
 ---

 # Facilitate Brainstorming Session Task
@ -2646,6 +2653,7 @@ sections:

 ==================== START: .bmad-2d-phaser-game-dev/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Elicitation Methods Data

 ## Core Reflective Methods
@ -2804,6 +2812,7 @@ sections:

 ==================== START: .bmad-2d-phaser-game-dev/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # KB Mode Interaction Task

 ## Purpose
@ -2883,6 +2892,7 @@ Or ask me about anything else related to BMad-Method!

 ==================== START: .bmad-2d-phaser-game-dev/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Workflow Management

 Enables BMad orchestrator to manage and execute team workflows.
@ -2956,6 +2966,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa

 ==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -3046,6 +3057,7 @@ The LLM will:

 ==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Brainstorming Techniques Task

 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@ -4535,6 +4547,7 @@ sections:

 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Document Quality Checklist

 ## Document Completeness
@ -5357,6 +5370,7 @@ sections:

 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Story Definition of Done Checklist

 ## Story Completeness
@ -5521,6 +5535,7 @@ _Any specific concerns, recommendations, or clarifications needed before develop

 ==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Guidelines

 ## Overview
@ -6172,6 +6187,7 @@ These guidelines ensure consistent, high-quality game development that meets per

 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Game Development Story Task

 ## Purpose
@ -8718,6 +8734,7 @@ sections:

 ==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Game Design Elicitation Task

 ## Purpose
@ -8832,6 +8849,7 @@ The questions and perspectives offered should always consider:

 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Game Development Story Task

 ## Purpose
@ -9052,6 +9070,7 @@ This task ensures game development stories are immediately actionable and enable

 ==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Brainstorming Techniques Task

 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@ -9346,6 +9365,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques

 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Document Quality Checklist

 ## Document Completeness
@ -9551,6 +9571,7 @@ _Outline immediate next actions for the team based on this assessment._

 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Story Definition of Done Checklist

 ## Story Completeness
@ -10081,6 +10102,7 @@ workflow:

 ==================== START: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development BMad Knowledge Base

 ## Overview
@ -10335,6 +10357,7 @@ This knowledge base provides the foundation for effective game development using

 ==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Guidelines

 ## Overview
--- a/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-architect.txt
+++ b/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-architect.txt
@ -104,6 +104,7 @@ dependencies:

 ==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -209,6 +210,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task

 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@ -491,6 +493,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que

 ==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document Sharding Task

 ## Purpose
@ -680,6 +683,7 @@ Document sharded successfully:

 ==================== START: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document an Existing Project

 ## Purpose
@ -1027,6 +1031,7 @@ Apply the advanced elicitation task after major sections to refine based on user

 ==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -1117,6 +1122,7 @@ The LLM will:

 ==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Game Design Elicitation Task

 ## Purpose
@ -2265,6 +2271,7 @@ sections:

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Architect Solution Validation Checklist

 This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
@ -2660,6 +2667,7 @@ After presenting the report, ask the user if they would like detailed analysis o

 ==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Guidelines (Unity & C#)

 ## Overview
@ -3250,6 +3258,7 @@ These guidelines ensure consistent, high-quality game development that meets per

 ==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Knowledge Base - 2D Unity Game Development

 ## Overview
--- a/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-designer.txt
+++ b/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-designer.txt
@ -101,6 +101,7 @@ dependencies:

 ==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -206,6 +207,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -296,6 +298,7 @@ The LLM will:

 ==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document Sharding Task

 ## Purpose
@ -485,6 +488,7 @@ Document sharded successfully:

 ==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Brainstorming Techniques Task

 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@ -779,6 +783,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques

 ==================== START: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task

 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@ -1061,6 +1066,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que

 ==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Game Design Elicitation Task

 ## Purpose
@ -2732,6 +2738,7 @@ sections:

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Document Quality Checklist

 ## Document Completeness
@ -2937,6 +2944,7 @@ _Outline immediate next actions for the team based on this assessment._

 ==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Knowledge Base - 2D Unity Game Development

 ## Overview
--- a/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-developer.txt
+++ b/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-developer.txt
@ -98,6 +98,7 @@ dependencies:

 ==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -188,6 +189,7 @@ The LLM will:

 ==================== START: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Validate Next Story Task

 ## Purpose
@ -326,6 +328,7 @@ Provide a structured validation report including:

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Story Definition of Done (DoD) Checklist

 ## Instructions for Developer Agent
--- a/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-sm.txt
+++ b/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-sm.txt
@ -89,6 +89,7 @@ dependencies:

 ==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Game Story Task

 ## Purpose
@ -277,6 +278,7 @@ This task ensures game development stories are immediately actionable and enable

 ==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -367,6 +369,7 @@ The LLM will:

 ==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Correct Course Task - Game Development

 ## Purpose
@ -772,6 +775,7 @@ sections:

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Change Navigation Checklist

 **Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.
--- a/dist/expansion-packs/bmad-2d-unity-game-dev/teams/unity-2d-game-team.txt
+++ b/dist/expansion-packs/bmad-2d-unity-game-dev/teams/unity-2d-game-team.txt
@ -478,6 +478,7 @@ dependencies:

 ==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Knowledge Base - 2D Unity Game Development

 ## Overview
@ -1251,6 +1252,7 @@ This knowledge base provides the foundation for effective game development using

 ==================== START: .bmad-2d-unity-game-dev/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Brainstorming Techniques Data

 ## Creative Expansion
@ -1291,6 +1293,7 @@ This knowledge base provides the foundation for effective game development using

 ==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Game Design Elicitation Task

 ## Purpose
@ -1405,6 +1408,7 @@ The questions and perspectives offered should always consider:

 ==================== START: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task

 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@ -1687,6 +1691,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que

 ==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -1792,6 +1797,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document an Existing Project

 ## Purpose
@ -2138,10 +2144,11 @@ Apply the advanced elicitation task after major sections to refine based on user
 ==================== END: .bmad-2d-unity-game-dev/tasks/document-project.md ====================

 ==================== START: .bmad-2d-unity-game-dev/tasks/facilitate-brainstorming-session.md ====================
-<!-- Powered by BMAD™ Core -->
---
+## <!-- Powered by BMAD™ Core -->
+
 docOutputLocation: docs/brainstorming-session-results.md
 template: '.bmad-2d-unity-game-dev/templates/brainstorming-output-tmpl.yaml'
+
 ---

 # Facilitate Brainstorming Session Task
@ -3229,6 +3236,7 @@ sections:

 ==================== START: .bmad-2d-unity-game-dev/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Elicitation Methods Data

 ## Core Reflective Methods
@ -3387,6 +3395,7 @@ sections:

 ==================== START: .bmad-2d-unity-game-dev/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # KB Mode Interaction Task

 ## Purpose
@ -3466,6 +3475,7 @@ Or ask me about anything else related to BMad-Method!

 ==================== START: .bmad-2d-unity-game-dev/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Workflow Management

 Enables BMad orchestrator to manage and execute team workflows.
@ -3539,6 +3549,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa

 ==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -3629,6 +3640,7 @@ The LLM will:

 ==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document Sharding Task

 ## Purpose
@ -3818,6 +3830,7 @@ Document sharded successfully:

 ==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Brainstorming Techniques Task

 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@ -5669,6 +5682,7 @@ sections:

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Document Quality Checklist

 ## Document Completeness
@ -6908,6 +6922,7 @@ sections:

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Architect Solution Validation Checklist

 This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
@ -7303,6 +7318,7 @@ After presenting the report, ask the user if they would like detailed analysis o

 ==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Guidelines (Unity & C#)

 ## Overview
@ -7893,6 +7909,7 @@ These guidelines ensure consistent, high-quality game development that meets per

 ==================== START: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Validate Next Story Task

 ## Purpose
@ -8031,6 +8048,7 @@ Provide a structured validation report including:

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Story Definition of Done (DoD) Checklist

 ## Instructions for Developer Agent
@ -8159,6 +8177,7 @@ Be honest - it's better to flag issues now than have them discovered during play

 ==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Game Story Task

 ## Purpose
@ -8347,6 +8366,7 @@ This task ensures game development stories are immediately actionable and enable

 ==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Correct Course Task - Game Development

 ## Purpose
@ -8752,6 +8772,7 @@ sections:

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Change Navigation Checklist

 **Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.
@ -11810,6 +11831,7 @@ sections:

 ==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Game Design Elicitation Task

 ## Purpose
@ -11924,6 +11946,7 @@ The questions and perspectives offered should always consider:

 ==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Correct Course Task - Game Development

 ## Purpose
@ -12069,6 +12092,7 @@ Based on the analysis and agreed path forward:

 ==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Game Story Task

 ## Purpose
@ -12257,6 +12281,7 @@ This task ensures game development stories are immediately actionable and enable

 ==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Brainstorming Techniques Task

 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@ -12551,6 +12576,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques

 ==================== START: .bmad-2d-unity-game-dev/tasks/validate-game-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Validate Game Story Task

 ## Purpose
@ -12755,6 +12781,7 @@ Based on validation results, provide specific recommendations for:

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Architect Solution Validation Checklist

 This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
@ -13150,6 +13177,7 @@ After presenting the report, ask the user if they would like detailed analysis o

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Change Navigation Checklist

 **Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.
@ -13357,6 +13385,7 @@ Keep it technically precise and actionable.]]

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Design Document Quality Checklist

 ## Document Completeness
@ -13562,6 +13591,7 @@ _Outline immediate next actions for the team based on this assessment._

 ==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Story Definition of Done (DoD) Checklist

 ## Instructions for Developer Agent
@ -14056,6 +14086,7 @@ workflow:

 ==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Knowledge Base - 2D Unity Game Development

 ## Overview
@ -14829,6 +14860,7 @@ This knowledge base provides the foundation for effective game development using

 ==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Game Development Guidelines (Unity & C#)

 ## Overview
--- a/dist/expansion-packs/bmad-creative-writing/agents/beta-reader.txt
+++ b/dist/expansion-packs/bmad-creative-writing/agents/beta-reader.txt
@ -117,6 +117,7 @@ Remember to present all options as numbered lists for easy selection.

 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -222,6 +223,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 5. Provide Feedback (Beta)
@ -248,6 +250,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 13. Quick Feedback (Serial)
@ -272,6 +275,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 16. Analyze Reader Feedback
@ -297,6 +301,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -387,6 +392,7 @@ The LLM will:

 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -608,6 +614,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 6. Beta‑Feedback Closure Checklist
@ -633,6 +640,7 @@ items:

 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Creative Writing Knowledge Base

 ## Overview
@ -844,6 +852,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c

 ==================== START: .bmad-creative-writing/data/story-structures.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Structure Patterns

 ## Three-Act Structure
--- a/dist/expansion-packs/bmad-creative-writing/agents/character-psychologist.txt
+++ b/dist/expansion-packs/bmad-creative-writing/agents/character-psychologist.txt
@ -116,6 +116,7 @@ Remember to present all options as numbered lists for easy selection.

 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -221,6 +222,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-creative-writing/tasks/develop-character.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 3. Develop Character
@ -247,6 +249,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Workshop Dialog

 ## Purpose
@ -313,6 +316,7 @@ Refined dialog with stronger voices and dramatic impact

 ==================== START: .bmad-creative-writing/tasks/character-depth-pass.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 9. Character Depth Pass
@ -337,6 +341,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -427,6 +432,7 @@ The LLM will:

 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -643,6 +649,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 1. Character Consistency Checklist
@ -668,6 +675,7 @@ items:

 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Creative Writing Knowledge Base

 ## Overview
--- a/dist/expansion-packs/bmad-creative-writing/agents/dialog-specialist.txt
+++ b/dist/expansion-packs/bmad-creative-writing/agents/dialog-specialist.txt
@ -115,6 +115,7 @@ Remember to present all options as numbered lists for easy selection.

 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -220,6 +221,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Workshop Dialog

 ## Purpose
@ -286,6 +288,7 @@ Refined dialog with stronger voices and dramatic impact

 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -376,6 +379,7 @@ The LLM will:

 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -592,6 +596,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 23. Comedic Timing & Humor Checklist
@ -617,6 +622,7 @@ items:

 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Creative Writing Knowledge Base

 ## Overview
@ -828,6 +834,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c

 ==================== START: .bmad-creative-writing/data/story-structures.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Structure Patterns

 ## Three-Act Structure
--- a/dist/expansion-packs/bmad-creative-writing/agents/editor.txt
+++ b/dist/expansion-packs/bmad-creative-writing/agents/editor.txt
@ -116,6 +116,7 @@ Remember to present all options as numbered lists for easy selection.

 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -221,6 +222,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-creative-writing/tasks/final-polish.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 14. Final Polish
@ -246,6 +248,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 6. Incorporate Feedback
@ -273,6 +276,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -363,6 +367,7 @@ The LLM will:

 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -569,6 +574,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 4. Line‑Edit Quality Checklist
@ -594,6 +600,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 5. Publication Readiness Checklist
@ -619,6 +626,7 @@ items:

 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Creative Writing Knowledge Base

 ## Overview
--- a/dist/expansion-packs/bmad-creative-writing/agents/genre-specialist.txt
+++ b/dist/expansion-packs/bmad-creative-writing/agents/genre-specialist.txt
@ -118,6 +118,7 @@ Remember to present all options as numbered lists for easy selection.

 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -223,6 +224,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Analyze Story Structure

 ## Purpose
@ -292,6 +294,7 @@ Comprehensive structural analysis with actionable recommendations

 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -382,6 +385,7 @@ The LLM will:

 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -602,6 +606,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/genre-tropes-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 10. Genre Tropes Checklist (General)
@ -626,6 +631,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 17. Fantasy Magic System Consistency Checklist
@ -651,6 +657,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 15. Sci‑Fi Technology Plausibility Checklist
@ -675,6 +682,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 12. Romance Emotional Beats Checklist
@ -700,6 +708,7 @@ items:

 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Creative Writing Knowledge Base

 ## Overview
@ -911,6 +920,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c

 ==================== START: .bmad-creative-writing/data/story-structures.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Structure Patterns

 ## Three-Act Structure
--- a/dist/expansion-packs/bmad-creative-writing/agents/narrative-designer.txt
+++ b/dist/expansion-packs/bmad-creative-writing/agents/narrative-designer.txt
@ -116,6 +116,7 @@ Remember to present all options as numbered lists for easy selection.

 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -221,6 +222,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-creative-writing/tasks/outline-scenes.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 11. Outline Scenes
@ -246,6 +248,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/generate-scene-list.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 10. Generate Scene List
@ -271,6 +274,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -361,6 +365,7 @@ The LLM will:

 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -540,6 +545,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Plot Structure Checklist

 ## Opening
@ -601,6 +607,7 @@ sections:

 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Creative Writing Knowledge Base

 ## Overview
@ -812,6 +819,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c

 ==================== START: .bmad-creative-writing/data/story-structures.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Structure Patterns

 ## Three-Act Structure
--- a/dist/expansion-packs/bmad-creative-writing/agents/plot-architect.txt
+++ b/dist/expansion-packs/bmad-creative-writing/agents/plot-architect.txt
@ -118,6 +118,7 @@ Remember to present all options as numbered lists for easy selection.

 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -223,6 +224,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Analyze Story Structure

 ## Purpose
@ -292,6 +294,7 @@ Comprehensive structural analysis with actionable recommendations

 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -382,6 +385,7 @@ The LLM will:

 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -826,6 +830,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Plot Structure Checklist

 ## Opening
@ -887,6 +892,7 @@ sections:

 ==================== START: .bmad-creative-writing/data/story-structures.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Structure Patterns

 ## Three-Act Structure
@ -956,6 +962,7 @@ sections:

 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Creative Writing Knowledge Base

 ## Overview
--- a/dist/expansion-packs/bmad-creative-writing/agents/world-builder.txt
+++ b/dist/expansion-packs/bmad-creative-writing/agents/world-builder.txt
@ -117,6 +117,7 @@ Remember to present all options as numbered lists for easy selection.

 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -222,6 +223,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-creative-writing/tasks/build-world.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 2. Build World
@ -248,6 +250,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -338,6 +341,7 @@ The LLM will:

 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -551,6 +555,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/world-building-continuity-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 2. World‑Building Continuity Checklist
@ -576,6 +581,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 17. Fantasy Magic System Consistency Checklist
@ -601,6 +607,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/steampunk-gadget-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 25. Steampunk Gadget Plausibility Checklist
@ -626,6 +633,7 @@ items:

 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Creative Writing Knowledge Base

 ## Overview
@ -837,6 +845,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c

 ==================== START: .bmad-creative-writing/data/story-structures.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Structure Patterns

 ## Three-Act Structure
--- a/dist/expansion-packs/bmad-creative-writing/teams/agent-team.txt
+++ b/dist/expansion-packs/bmad-creative-writing/teams/agent-team.txt
@ -837,6 +837,7 @@ dependencies:

 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Creative Writing Knowledge Base

 ## Overview
@ -1048,6 +1049,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c

 ==================== START: .bmad-creative-writing/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Elicitation Methods Data

 ## Core Reflective Methods
@ -1206,6 +1208,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c

 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -1327,6 +1330,7 @@ Choose a number (0-8) or 9 to proceed:

 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -1432,6 +1436,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-creative-writing/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # KB Mode Interaction Task

 ## Purpose
@ -1511,6 +1516,7 @@ Or ask me about anything else related to BMad-Method!

 ==================== START: .bmad-creative-writing/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Workflow Management

 Enables BMad orchestrator to manage and execute team workflows.
@ -1584,6 +1590,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa

 ==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Analyze Story Structure

 ## Purpose
@ -1653,6 +1660,7 @@ Comprehensive structural analysis with actionable recommendations

 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -2066,6 +2074,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Plot Structure Checklist

 ## Opening
@ -2127,6 +2136,7 @@ sections:

 ==================== START: .bmad-creative-writing/data/story-structures.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Structure Patterns

 ## Three-Act Structure
@ -2196,6 +2206,7 @@ sections:

 ==================== START: .bmad-creative-writing/tasks/develop-character.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 3. Develop Character
@ -2222,6 +2233,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Workshop Dialog

 ## Purpose
@ -2288,6 +2300,7 @@ Refined dialog with stronger voices and dramatic impact

 ==================== START: .bmad-creative-writing/tasks/character-depth-pass.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 9. Character Depth Pass
@ -2407,6 +2420,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 1. Character Consistency Checklist
@ -2432,6 +2446,7 @@ items:

 ==================== START: .bmad-creative-writing/tasks/build-world.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 2. Build World
@ -2550,6 +2565,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/world-building-continuity-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 2. World‑Building Continuity Checklist
@ -2575,6 +2591,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 17. Fantasy Magic System Consistency Checklist
@ -2600,6 +2617,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/steampunk-gadget-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 25. Steampunk Gadget Plausibility Checklist
@ -2625,6 +2643,7 @@ items:

 ==================== START: .bmad-creative-writing/tasks/final-polish.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 14. Final Polish
@ -2650,6 +2669,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 6. Incorporate Feedback
@ -2677,6 +2697,7 @@ inputs:

 ==================== START: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 4. Line‑Edit Quality Checklist
@ -2702,6 +2723,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 5. Publication Readiness Checklist
@ -2727,6 +2749,7 @@ items:

 ==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 5. Provide Feedback (Beta)
@ -2753,6 +2776,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 13. Quick Feedback (Serial)
@ -2777,6 +2801,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 16. Analyze Reader Feedback
@ -2902,6 +2927,7 @@ sections:

 ==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 6. Beta‑Feedback Closure Checklist
@ -2927,6 +2953,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 23. Comedic Timing & Humor Checklist
@ -2952,6 +2979,7 @@ items:

 ==================== START: .bmad-creative-writing/tasks/outline-scenes.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 11. Outline Scenes
@ -2977,6 +3005,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/generate-scene-list.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 10. Generate Scene List
@ -3002,6 +3031,7 @@ inputs:

 ==================== START: .bmad-creative-writing/checklists/genre-tropes-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 10. Genre Tropes Checklist (General)
@ -3026,6 +3056,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 15. Sci‑Fi Technology Plausibility Checklist
@ -3050,6 +3081,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 12. Romance Emotional Beats Checklist
@ -3786,6 +3818,7 @@ sections:

 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -3907,6 +3940,7 @@ Choose a number (0-8) or 9 to proceed:

 ==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 16. Analyze Reader Feedback
@ -3932,6 +3966,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Analyze Story Structure

 ## Purpose
@ -4001,6 +4036,7 @@ Comprehensive structural analysis with actionable recommendations

 ==================== START: .bmad-creative-writing/tasks/assemble-kdp-package.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # tasks/assemble-kdp-package.md
@ -4032,6 +4068,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/brainstorm-premise.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 1. Brainstorm Premise
@ -4057,6 +4094,7 @@ steps:

 ==================== START: .bmad-creative-writing/tasks/build-world.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 2. Build World
@ -4083,6 +4121,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/character-depth-pass.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 9. Character Depth Pass
@ -4107,6 +4146,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -4212,6 +4252,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-creative-writing/tasks/create-draft-section.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 4. Create Draft Section (Chapter)
@ -4240,6 +4281,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/develop-character.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 3. Develop Character
@ -4266,6 +4308,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -4356,6 +4399,7 @@ The LLM will:

 ==================== START: .bmad-creative-writing/tasks/expand-premise.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 7. Expand Premise (Snowflake Step 2)
@ -4381,6 +4425,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/expand-synopsis.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 8. Expand Synopsis (Snowflake Step 4)
@ -4406,6 +4451,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/final-polish.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 14. Final Polish
@ -4431,6 +4477,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/generate-cover-brief.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # tasks/generate-cover-brief.md
@ -4458,6 +4505,7 @@ steps:

 ==================== START: .bmad-creative-writing/tasks/generate-cover-prompts.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # tasks/generate-cover-prompts.md
@ -4486,6 +4534,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/generate-scene-list.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 10. Generate Scene List
@ -4511,6 +4560,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 6. Incorporate Feedback
@ -4538,6 +4588,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/outline-scenes.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 11. Outline Scenes
@ -4563,6 +4614,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 5. Provide Feedback (Beta)
@ -4589,6 +4641,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/publish-chapter.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 15. Publish Chapter
@ -4614,6 +4667,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 13. Quick Feedback (Serial)
@ -4638,6 +4692,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/select-next-arc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 12. Select Next Arc (Serial)
@ -4663,6 +4718,7 @@ inputs:

 ==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Workshop Dialog

 ## Purpose
@ -4729,6 +4785,7 @@ Refined dialog with stronger voices and dramatic impact

 ==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 6. Beta‑Feedback Closure Checklist
@ -4754,6 +4811,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 1. Character Consistency Checklist
@ -4779,6 +4837,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 23. Comedic Timing & Humor Checklist
@ -4804,6 +4863,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/cyberpunk-aesthetic-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 24. Cyberpunk Aesthetic Consistency Checklist
@ -4829,6 +4889,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/ebook-formatting-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 14. eBook Formatting Checklist
@ -4852,6 +4913,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/epic-poetry-meter-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 22. Epic Poetry Meter & Form Checklist
@ -4877,6 +4939,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 17. Fantasy Magic System Consistency Checklist
@ -4902,6 +4965,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/foreshadowing-payoff-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 9. Foreshadowing & Payoff Checklist
@ -4926,6 +4990,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/historical-accuracy-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 18. Historical Accuracy Checklist
@ -4951,6 +5016,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/horror-suspense-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 16. Horror Suspense & Scare Checklist
@ -4976,6 +5042,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/kdp-cover-ready-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # checklists/kdp-cover-ready-checklist.md
@ -5003,6 +5070,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 4. Line‑Edit Quality Checklist
@ -5028,6 +5096,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/marketing-copy-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 13. Marketing Copy Checklist
@ -5053,6 +5122,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/mystery-clue-trail-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 11. Mystery Clue Trail Checklist
@ -5078,6 +5148,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/orbital-mechanics-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 21. Hard‑Science Orbital Mechanics Checklist
@ -5103,6 +5174,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Plot Structure Checklist

 ## Opening
@ -5164,6 +5236,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 5. Publication Readiness Checklist
@ -5189,6 +5262,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 12. Romance Emotional Beats Checklist
@ -5214,6 +5288,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/scene-quality-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 3. Scene Quality Checklist
@ -5239,6 +5314,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 15. Sci‑Fi Technology Plausibility Checklist
@ -5263,6 +5339,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/sensitivity-representation-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 7. Sensitivity & Representation Checklist
@ -5288,6 +5365,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/steampunk-gadget-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 25. Steampunk Gadget Plausibility Checklist
@ -5313,6 +5391,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/thriller-pacing-stakes-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 19. Thriller Pacing & Stakes Checklist
@ -5338,6 +5417,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/timeline-continuity-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 8. Timeline & Continuity Checklist
@ -5363,6 +5443,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/world-building-continuity-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 2. World‑Building Continuity Checklist
@ -5388,6 +5469,7 @@ items:

 ==================== START: .bmad-creative-writing/checklists/ya-appropriateness-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # ------------------------------------------------------------

 # 20. YA Appropriateness Checklist
@ -5413,6 +5495,7 @@ items:

 ==================== START: .bmad-creative-writing/workflows/book-cover-design-workflow.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Book Cover Design Assets

 # ============================================================
@ -6147,6 +6230,7 @@ outputs:

 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMad Creative Writing Knowledge Base

 ## Overview
@ -6358,6 +6442,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c

 ==================== START: .bmad-creative-writing/data/story-structures.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Story Structure Patterns

 ## Three-Act Structure
--- a/dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt
+++ b/dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt
@ -102,6 +102,7 @@ dependencies:

 ==================== START: .bmad-infrastructure-devops/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -207,6 +208,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-infrastructure-devops/tasks/review-infrastructure.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Infrastructure Review Task

 ## Purpose
@ -370,6 +372,7 @@ REPEAT by Asking the user if they would like to perform another Reflective, Elic

 ==================== START: .bmad-infrastructure-devops/tasks/validate-infrastructure.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Infrastructure Validation Task

 ## Purpose
@ -1588,6 +1591,7 @@ sections:

 ==================== START: .bmad-infrastructure-devops/checklists/infrastructure-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Infrastructure Change Validation Checklist

 This checklist serves as a comprehensive framework for validating infrastructure changes before deployment to production. The DevOps/Platform Engineer should systematically work through each item, ensuring the infrastructure is secure, compliant, resilient, and properly implemented according to organizational standards.
@ -2076,6 +2080,7 @@ This checklist serves as a comprehensive framework for validating infrastructure

 ==================== START: .bmad-infrastructure-devops/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # User-Defined Preferred Patterns and Preferences

 None Listed
--- a/dist/expansion-packs/bmad-tdd-methodology/agents/dev.txt
+++ b/dist/expansion-packs/bmad-tdd-methodology/agents/dev.txt
--- a/dist/expansion-packs/bmad-tdd-methodology/agents/qa.txt
+++ b/dist/expansion-packs/bmad-tdd-methodology/agents/qa.txt
--- a/dist/expansion-packs/tdd-methodology/agents/dev.txt
+++ b/dist/expansion-packs/tdd-methodology/agents/dev.txt
--- a/dist/expansion-packs/tdd-methodology/agents/qa.txt
+++ b/dist/expansion-packs/tdd-methodology/agents/qa.txt
--- a/dist/teams/team-all.txt
+++ b/dist/teams/team-all.txt
--- a/dist/teams/team-fullstack.txt
+++ b/dist/teams/team-fullstack.txt
@ -491,6 +491,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -612,6 +613,7 @@ Choose a number (0-8) or 9 to proceed:

 ==================== START: .bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -717,6 +719,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # KB Mode Interaction Task

 ## Purpose
@ -796,6 +799,7 @@ Or ask me about anything else related to BMad-Method!

 ==================== START: .bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMAD™ Knowledge Base

 ## Overview
@ -1606,6 +1610,7 @@ Use the **expansion-creator** pack to build your own:

 ==================== START: .bmad-core/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Elicitation Methods Data

 ## Core Reflective Methods
@ -1764,6 +1769,7 @@ Use the **expansion-creator** pack to build your own:

 ==================== START: .bmad-core/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Workflow Management

 Enables BMad orchestrator to manage and execute team workflows.
@ -1837,6 +1843,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa

 ==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task

 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@ -2119,6 +2126,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que

 ==================== START: .bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document an Existing Project

 ## Purpose
@ -2465,10 +2473,11 @@ Apply the advanced elicitation task after major sections to refine based on user
 ==================== END: .bmad-core/tasks/document-project.md ====================

 ==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
-<!-- Powered by BMAD™ Core -->
---
+## <!-- Powered by BMAD™ Core -->
+
 docOutputLocation: docs/brainstorming-session-results.md
 template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
+
 ---

 # Facilitate Brainstorming Session Task
@ -3556,6 +3565,7 @@ sections:

 ==================== START: .bmad-core/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Brainstorming Techniques Data

 ## Creative Expansion
@ -3596,6 +3606,7 @@ sections:

 ==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Brownfield Epic Task

 ## Purpose
@ -3760,6 +3771,7 @@ The epic creation is successful when:

 ==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Brownfield Story Task

 ## Purpose
@ -3911,6 +3923,7 @@ The story creation is successful when:

 ==================== START: .bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Correct Course Task

 ## Purpose
@ -3985,6 +3998,7 @@ The story creation is successful when:

 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -4075,6 +4089,7 @@ The LLM will:

 ==================== START: .bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document Sharding Task

 ## Purpose
@ -4754,6 +4769,7 @@ sections:

 ==================== START: .bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Change Navigation Checklist

 **Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
@ -4940,6 +4956,7 @@ Keep it action-oriented and forward-looking.]]

 ==================== START: .bmad-core/checklists/pm-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Product Manager (PM) Requirements Checklist

 This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
@ -5314,6 +5331,7 @@ After presenting the report, ask if the user wants:

 ==================== START: .bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # User-Defined Preferred Patterns and Preferences

 None Listed
@ -5321,6 +5339,7 @@ None Listed

 ==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create AI Frontend Prompt Task

 ## Purpose
@ -7912,6 +7931,7 @@ sections:

 ==================== START: .bmad-core/checklists/architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Architect Solution Validation Checklist

 This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
@ -8354,6 +8374,7 @@ After presenting the report, ask the user if they would like detailed analysis o

 ==================== START: .bmad-core/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Validate Next Story Task

 ## Purpose
@ -8633,6 +8654,7 @@ sections:

 ==================== START: .bmad-core/checklists/po-master-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Product Owner (PO) Master Validation Checklist

 This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
@ -9230,7 +9252,7 @@ workflow:
        - Dev Agent (New Chat): Address remaining items
        - Return to QA for final approval

-    - repeat_development_cycle:
+    - step: repeat_development_cycle
      action: continue_for_all_stories
      notes: |
        Repeat story cycle (SM → Dev → QA) for all epic stories
@ -9247,7 +9269,7 @@ workflow:
        - Validate epic was completed correctly
        - Document learnings and improvements

-    - workflow_end:
+    - step: workflow_end
      action: project_complete
      notes: |
        All stories implemented and reviewed!
@ -9477,7 +9499,7 @@ workflow:
        - Dev Agent (New Chat): Address remaining items
        - Return to QA for final approval

-    - repeat_development_cycle:
+    - step: repeat_development_cycle
      action: continue_for_all_stories
      notes: |
        Repeat story cycle (SM → Dev → QA) for all epic stories
@ -9494,7 +9516,7 @@ workflow:
        - Validate epic was completed correctly
        - Document learnings and improvements

-    - workflow_end:
+    - step: workflow_end
      action: project_complete
      notes: |
        All stories implemented and reviewed!
@ -9675,7 +9697,7 @@ workflow:
        - Dev Agent (New Chat): Address remaining items
        - Return to QA for final approval

-    - repeat_development_cycle:
+    - step: repeat_development_cycle
      action: continue_for_all_stories
      notes: |
        Repeat story cycle (SM → Dev → QA) for all epic stories
@ -9692,7 +9714,7 @@ workflow:
        - Validate epic was completed correctly
        - Document learnings and improvements

-    - workflow_end:
+    - step: workflow_end
      action: project_complete
      notes: |
        All stories implemented and reviewed!
@ -9828,12 +9850,12 @@ workflow:
      condition: po_checklist_issues
      notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."

-    - project_setup_guidance:
+    - step: project_setup_guidance
      action: guide_project_structure
      condition: user_has_generated_ui
      notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo alongside backend repo. For monorepo, place in apps/web or packages/frontend directory. Review architecture document for specific guidance."

-    - development_order_guidance:
+    - step: development_order_guidance
      action: guide_development_sequence
      notes: "Based on PRD stories: If stories are frontend-heavy, start with frontend project/directory first. If backend-heavy or API-first, start with backend. For tightly coupled features, follow story sequence in monorepo setup. Reference sharded PRD epics for development order."

@ -9901,7 +9923,7 @@ workflow:
        - Dev Agent (New Chat): Address remaining items
        - Return to QA for final approval

-    - repeat_development_cycle:
+    - step: repeat_development_cycle
      action: continue_for_all_stories
      notes: |
        Repeat story cycle (SM → Dev → QA) for all epic stories
@ -9918,7 +9940,7 @@ workflow:
        - Validate epic was completed correctly
        - Document learnings and improvements

-    - workflow_end:
+    - step: workflow_end
      action: project_complete
      notes: |
        All stories implemented and reviewed!
@ -10121,7 +10143,7 @@ workflow:
        - Dev Agent (New Chat): Address remaining items
        - Return to QA for final approval

-    - repeat_development_cycle:
+    - step: repeat_development_cycle
      action: continue_for_all_stories
      notes: |
        Repeat story cycle (SM → Dev → QA) for all epic stories
@ -10138,7 +10160,7 @@ workflow:
        - Validate epic was completed correctly
        - Document learnings and improvements

-    - workflow_end:
+    - step: workflow_end
      action: project_complete
      notes: |
        All stories implemented and reviewed!
@ -10281,7 +10303,7 @@ workflow:
      condition: po_checklist_issues
      notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."

-    - project_setup_guidance:
+    - step: project_setup_guidance
      action: guide_project_structure
      condition: user_has_generated_ui
      notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance."
@ -10350,7 +10372,7 @@ workflow:
        - Dev Agent (New Chat): Address remaining items
        - Return to QA for final approval

-    - repeat_development_cycle:
+    - step: repeat_development_cycle
      action: continue_for_all_stories
      notes: |
        Repeat story cycle (SM → Dev → QA) for all epic stories
@ -10367,7 +10389,7 @@ workflow:
        - Validate epic was completed correctly
        - Document learnings and improvements

-    - workflow_end:
+    - step: workflow_end
      action: project_complete
      notes: |
        All stories implemented and reviewed!
--- a/dist/teams/team-ide-minimal.txt
+++ b/dist/teams/team-ide-minimal.txt
--- a/dist/teams/team-no-ui.txt
+++ b/dist/teams/team-no-ui.txt
@ -437,6 +437,7 @@ dependencies:

 ==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task

 ## Purpose
@ -558,6 +559,7 @@ Choose a number (0-8) or 9 to proceed:

 ==================== START: .bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)

 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@ -663,6 +665,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).

 ==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # KB Mode Interaction Task

 ## Purpose
@ -742,6 +745,7 @@ Or ask me about anything else related to BMad-Method!

 ==================== START: .bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # BMAD™ Knowledge Base

 ## Overview
@ -1552,6 +1556,7 @@ Use the **expansion-creator** pack to build your own:

 ==================== START: .bmad-core/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Elicitation Methods Data

 ## Core Reflective Methods
@ -1710,6 +1715,7 @@ Use the **expansion-creator** pack to build your own:

 ==================== START: .bmad-core/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Workflow Management

 Enables BMad orchestrator to manage and execute team workflows.
@ -1783,6 +1789,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa

 ==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task

 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@ -2065,6 +2072,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que

 ==================== START: .bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document an Existing Project

 ## Purpose
@ -2411,10 +2419,11 @@ Apply the advanced elicitation task after major sections to refine based on user
 ==================== END: .bmad-core/tasks/document-project.md ====================

 ==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
-<!-- Powered by BMAD™ Core -->
---
+## <!-- Powered by BMAD™ Core -->
+
 docOutputLocation: docs/brainstorming-session-results.md
 template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
+
 ---

 # Facilitate Brainstorming Session Task
@ -3502,6 +3511,7 @@ sections:

 ==================== START: .bmad-core/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Brainstorming Techniques Data

 ## Creative Expansion
@ -3542,6 +3552,7 @@ sections:

 ==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Brownfield Epic Task

 ## Purpose
@ -3706,6 +3717,7 @@ The epic creation is successful when:

 ==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Create Brownfield Story Task

 ## Purpose
@ -3857,6 +3869,7 @@ The story creation is successful when:

 ==================== START: .bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Correct Course Task

 ## Purpose
@ -3931,6 +3944,7 @@ The story creation is successful when:

 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task

 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@ -4021,6 +4035,7 @@ The LLM will:

 ==================== START: .bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Document Sharding Task

 ## Purpose
@ -4700,6 +4715,7 @@ sections:

 ==================== START: .bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Change Navigation Checklist

 **Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
@ -4886,6 +4902,7 @@ Keep it action-oriented and forward-looking.]]

 ==================== START: .bmad-core/checklists/pm-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Product Manager (PM) Requirements Checklist

 This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
@ -5260,6 +5277,7 @@ After presenting the report, ask if the user wants:

 ==================== START: .bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # User-Defined Preferred Patterns and Preferences

 None Listed
@ -7450,6 +7468,7 @@ sections:

 ==================== START: .bmad-core/checklists/architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Architect Solution Validation Checklist

 This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
@ -7892,6 +7911,7 @@ After presenting the report, ask the user if they would like detailed analysis o

 ==================== START: .bmad-core/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Validate Next Story Task

 ## Purpose
@ -8171,6 +8191,7 @@ sections:

 ==================== START: .bmad-core/checklists/po-master-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
+
 # Product Owner (PO) Master Validation Checklist

 This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
@ -8722,7 +8743,7 @@ workflow:
        - Dev Agent (New Chat): Address remaining items
        - Return to QA for final approval

-    - repeat_development_cycle:
+    - step: repeat_development_cycle
      action: continue_for_all_stories
      notes: |
        Repeat story cycle (SM → Dev → QA) for all epic stories
@ -8739,7 +8760,7 @@ workflow:
        - Validate epic was completed correctly
        - Document learnings and improvements

-    - workflow_end:
+    - step: workflow_end
      action: project_complete
      notes: |
        All stories implemented and reviewed!
@ -8924,7 +8945,7 @@ workflow:
        - Dev Agent (New Chat): Address remaining items
        - Return to QA for final approval

-    - repeat_development_cycle:
+    - step: repeat_development_cycle
      action: continue_for_all_stories
      notes: |
        Repeat story cycle (SM → Dev → QA) for all epic stories
@ -8941,7 +8962,7 @@ workflow:
        - Validate epic was completed correctly
        - Document learnings and improvements

-    - workflow_end:
+    - step: workflow_end
      action: project_complete
      notes: |
        All stories implemented and reviewed!