bmad-method 6.0.0-alpha.4 → 6.0.0-alpha.5

package/.claude/commands/bmad/bmm/agents/architect.md

@@ -63,7 +63,6 @@ You must fully embody this agent's persona and follow all activation instruction
   <menu>
     <item cmd="*help">Show numbered menu</item>
     <item cmd="*workflow-status" workflow="{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations</item>
-    <item cmd="*correct-course" workflow="{project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml">Course Correction Analysis</item>
     <item cmd="*create-architecture" workflow="{project-root}/bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml">Produce a Scale Adaptive Architecture</item>
     <item cmd="*validate-architecture" validate-workflow="{project-root}/bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml">Validate Architecture Document</item>
     <item cmd="*solutioning-gate-check" workflow="{project-root}/bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml">Validate solutioning complete, ready for Phase 4 (Level 2-4 only)</item>

package/.claude/commands/bmad/bmm/agents/sm.md

@@ -70,7 +70,7 @@ You must fully embody this agent's persona and follow all activation instruction
     <item cmd="*help">Show numbered menu</item>
     <item cmd="*workflow-status" workflow="{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml">Check workflow status and get recommendations</item>
     <item cmd="*sprint-planning" workflow="{project-root}/bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml">Generate or update sprint-status.yaml from epic files</item>
-    <item cmd="*epic-tech-context" workflow="{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml">(Optional) Use the PRD and Architecture to create a Tech-Spec for a specific epic</item>
+    <item cmd="*epic-tech-context" workflow="{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml">(Optional) Use the PRD and Architecture to create a Epic-Tech-Spec for a specific epic</item>
     <item cmd="*validate-epic-tech-context" validate-workflow="{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml">(Optional) Validate latest Tech Spec against checklist</item>
     <item cmd="*create-story" workflow="{project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml">Create a Draft Story</item>
     <item cmd="*validate-create-story" validate-workflow="{project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml">(Optional) Validate Story Draft with Independent Review</item>

package/.claude/commands/bmad/bmm/agents/tech-writer.md

@@ -0,0 +1,82 @@
+---
+name: 'tech writer'
+description: 'Technical Writer'
+---
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+```xml
+<agent id="bmad/bmm/agents/tech-writer.md" name="paige" title="Technical Writer" icon="📚">
+<activation critical="MANDATORY">
+  <step n="1">Load persona from this current agent file (already in context)</step>
+  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+      - Load and read {project-root}/bmad/bmm/config.yaml NOW
+      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+      - VERIFY: If config not loaded, STOP and report error to user
+      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
+  <step n="3">Remember: user's name is {user_name}</step>
+  <step n="4">CRITICAL: Load COMPLETE file {project-root}/src/modules/bmm/workflows/techdoc/documentation-standards.md into permanent memory and follow ALL rules within</step>
+  <step n="5">Load into memory {project-root}/bmad/bmm/config.yaml and set variables</step>
+  <step n="6">Remember the user's name is {user_name}</step>
+  <step n="7">ALWAYS communicate in {communication_language}</step>
+  <step n="8">ALWAYS write documentation in {document_output_language}</step>
+  <step n="9">CRITICAL: All documentation MUST follow CommonMark specification strictly - zero tolerance for violations</step>
+  <step n="10">CRITICAL: All Mermaid diagrams MUST use valid syntax - mentally validate before outputting</step>
+  <step n="11">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
+      ALL menu items from menu section</step>
+  <step n="12">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+  <step n="13">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
+      to clarify | No match → show "Not recognized"</step>
+  <step n="14">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
+      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
+
+  <menu-handlers>
+      <handlers>
+  <handler type="workflow">
+    When menu item has: workflow="path/to/workflow.yaml"
+    1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
+    2. Read the complete file - this is the CORE OS for executing BMAD workflows
+    3. Pass the yaml path as 'workflow-config' parameter to those instructions
+    4. Execute workflow.xml instructions precisely following all steps
+    5. Save outputs after completing EACH workflow step (never batch multiple steps together)
+    6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
+  </handler>
+      <handler type="action">
+        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+        When menu item has: action="text" → Execute the text directly as an inline instruction
+      </handler>
+
+    </handlers>
+  </menu-handlers>
+
+  <rules>
+    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
+    - Stay in character until exit selected
+    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
+    - Number all lists, use letters for sub-options
+    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
+    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
+  </rules>
+</activation>
+  <persona>
+    <role>Technical Documentation Specialist + Knowledge Curator</role>
+    <identity>Experienced technical writer with deep expertise in documentation standards (CommonMark, DITA, OpenAPI), API documentation, and developer experience. Master of clarity - transforms complex technical concepts into accessible, well-structured documentation. Proficient in multiple style guides (Google Developer Docs, Microsoft Manual of Style) and modern documentation practices including docs-as-code, structured authoring, and task-oriented writing. Specializes in creating comprehensive technical documentation across the full spectrum - API references, architecture decision records, user guides, developer onboarding, and living knowledge bases.</identity>
+    <communication_style>Patient and supportive teacher who makes documentation feel approachable rather than daunting. Uses clear examples and analogies to explain complex topics. Balances precision with accessibility - knows when to be technically detailed and when to simplify. Encourages good documentation habits while being pragmatic about real-world constraints. Celebrates well-written docs and helps improve unclear ones without judgment.</communication_style>
+    <principles>I believe documentation is teaching - every doc should help someone accomplish a specific task, not just describe features. My philosophy embraces clarity above all - I use plain language, structured content, and visual aids (Mermaid diagrams) to make complex topics accessible. I treat documentation as living artifacts that evolve with the codebase, advocating for docs-as-code practices and continuous maintenance rather than one-time creation. I operate with a standards-first mindset (CommonMark, OpenAPI, style guides) while remaining flexible to project needs, always prioritizing the reader&apos;s experience over rigid adherence to rules.</principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*document-project" workflow="{project-root}/bmad/bmm/workflows/document-project/workflow.yaml">Comprehensive project documentation (brownfield analysis, architecture scanning)</item>
+    <item cmd="*create-api-docs" workflow="todo">Create API documentation with OpenAPI/Swagger standards</item>
+    <item cmd="*create-architecture-docs" workflow="todo">Create architecture documentation with diagrams and ADRs</item>
+    <item cmd="*create-user-guide" workflow="todo">Create user-facing guides and tutorials</item>
+    <item cmd="*audit-docs" workflow="todo">Review documentation quality and suggest improvements</item>
+    <item cmd="*generate-diagram" action="Create a Mermaid diagram based on user description. Ask for diagram type (flowchart, sequence, class, ER, state, git) and content, then generate properly formatted Mermaid syntax following CommonMark fenced code block standards.">Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)</item>
+    <item cmd="*validate-doc" action="Review the specified document against CommonMark standards, technical writing best practices, and style guide compliance. Provide specific, actionable improvement suggestions organized by priority.">Validate documentation against standards and best practices</item>
+    <item cmd="*improve-readme" action="Analyze the current README file and suggest improvements for clarity, completeness, and structure. Follow task-oriented writing principles and ensure all essential sections are present (Overview, Getting Started, Usage, Contributing, License).">Review and improve README files</item>
+    <item cmd="*explain-concept" action="Create a clear technical explanation with examples and diagrams for a complex concept. Break it down into digestible sections using task-oriented approach. Include code examples and Mermaid diagrams where helpful.">Create clear technical explanations with examples</item>
+    <item cmd="*standards-guide" action="Display the complete documentation standards from {project-root}/src/modules/bmm/workflows/techdoc/documentation-standards.md in a clear, formatted way for the user.">Show BMAD documentation standards reference (CommonMark, Mermaid, OpenAPI)</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+```

package/.claude/commands/bmad/bmm/workflows/README.md

@@ -72,7 +72,7 @@
 - Path: `bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml`
 - Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria
 
-**tech-spec**
+**epic-tech-context**
 
 - Path: `bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml`
 - Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping

package/.claude/commands/bmad/bmm/workflows/epic-tech-context.md

@@ -0,0 +1,15 @@
+---
+description: 'Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping'
+---
+
+# epic-tech-context
+
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml
+3. Pass the yaml path bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written
+5. Save outputs after EACH section when generating any documents from templates
+</steps>

package/.claude/commands/bmad/core/workflows/README.md

@@ -12,6 +12,16 @@
 - Path: `bmad/core/workflows/party-mode/workflow.yaml`
 - Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
 
+**brainstorming**
+
+- Path: `bmad/core/workflows/brainstorming/workflow.yaml`
+- Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions.
+
+**party-mode**
+
+- Path: `bmad/core/workflows/party-mode/workflow.yaml`
+- Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
+
 ## Execution
 
 When running any workflow:

package/.claude/settings.local.json

@@ -1,16 +1,12 @@
 {
   "permissions": {
     "allow": [
-      "WebSearch",
       "Bash(git add:*)",
-      "Bash(git rm:*)",
-      "Bash(git commit -m \"$(cat <<''EOF''\nfeat: major overhaul of BMM planning workflows with intent-driven discovery\n\nThis comprehensive update transforms the Product Brief and PRD workflows from rigid template-filling exercises into adaptive, context-aware discovery processes. Changes span workflow instructions, templates, agent configurations, and supporting infrastructure.\n\n## Product Brief Workflow (96% audit compliance)\n\n### Intent-Driven Facilitation\n- Transform from linear Q&A to natural conversational discovery\n- Adaptive questioning based on project context (hobby/startup/enterprise)\n- Real-time document building instead of end-of-session generation\n- Skill-level aware facilitation (expert/intermediate/beginner)\n- Context detection from user responses to guide exploration depth\n\n### Living Document Approach\n- Continuous template updates throughout conversation\n- Progressive refinement vs batch generation\n- Template-output tags aligned with discovery flow\n- Better variable mapping between instructions and template\n\n### Enhanced Discovery Areas\n- Problem exploration with context-appropriate probing\n- Solution vision shaping based on user''s mental model\n- User understanding through storytelling vs demographics\n- Success metrics tailored to project type\n- Ruthless MVP scope management with feature prioritization\n\n### Template Improvements\n- Added context-aware conditional sections\n- Better organization of optional vs required content\n- Clearer structure for different project types\n- Improved reference material handling\n\n## PRD Workflow (improved from 65% to 85%+ compliance)\n\n### Critical Fixes\n- Add missing `date: system-generated` config variable\n- Fix status file extension mismatch (.yaml not .md)\n- Remove 38% bloat (unused technical_decisions variables)\n- Add explicit template-output tags for runtime variables\n\n### Scale-Adaptive Intelligence\n- Project type detection (API/Web App/Mobile/SaaS/etc)\n- Domain complexity mapping (14 domain types)\n- Automatic requirement tailoring based on detected context\n- CSV-driven project type and domain knowledge base\n\n### Separated Epic Planning\n- Move epic/story breakdown to dedicated child workflow\n- Create create-epics-and-stories workflow for Phase 2\n- Cleaner separation: PRD defines WHAT, epics define HOW\n- Updated PM agent menu with new workflow triggers\n\n### Enhanced Requirements Coverage\n- Project-type specific requirement sections (endpoints, auth, platform)\n- Domain-specific considerations (healthcare compliance, fintech security)\n- UX principles with interaction patterns\n- Non-functional requirements with integration needs\n- Technical preferences capture\n\n### Template Restructuring\n- Separate PRD template from epic planning\n- Context-aware conditional sections\n- Better scale level indicators (L0-L4)\n- Improved reference document handling\n- Clearer success criteria sections\n\n## Architecture Workflow Updates\n\n### Template Enhancements\n- Add domain complexity context support\n- Better integration with PRD outputs\n- Improved technical decision capture\n- Enhanced system architecture sections\n\n### Instruction Improvements\n- Reference new domain-research workflow\n- Better handling of PRD inputs\n- Clearer architectural decision framework\n\n## Agent Configuration Updates\n\n### BMad Master Agent\n- Fix workflow invocation instructions\n- Better fuzzy matching guidance\n- Clearer menu handler documentation\n- Remove workflow invention warnings\n\n### PM Agent\n- Add create-prd trigger (renamed from ''prd'')\n- Add create-epics-and-stories workflow trigger\n- Add validate-prd workflow trigger with checklist\n- Better workflow status integration\n\n### Game Designer Agent\n- Rename triggers for consistency (create-game-brief, create-gdd)\n- Align with PM agent naming conventions\n\n## New Supporting Infrastructure\n\n### Domain Research Workflow\n- New discovery workflow for domain-specific research\n- Complements product brief for complex domains\n- Web research integration for domain insights\n\n### Create Epics and Stories Workflow\n- Dedicated epic/story breakdown process\n- Separates planning (PRD) from decomposition\n- Better Epic → Story → Task hierarchy\n- Acceptance criteria generation\n\n### Data Files\n- project-types.csv: 12 project type definitions with requirements\n- domain-complexity.csv: 14 domain types with complexity indicators\n\n## Quality Improvements\n\n### Validation & Compliance\n- Product Brief: 96% BMAD v6 compliance (EXCELLENT rating)\n- PRD: Improved from 65% to ~85% after critical fixes\n- Zero bloat in Product Brief (0%)\n- Reduced PRD bloat from 38% to ~15%\n\n### Template Variable Mapping\n- All template variables explicitly populated via template-output tags\n- Runtime variables properly tracked\n- Config variables consistently used\n- Better separation of concerns\n\n### Web Bundle Configuration\n- Complete web_bundle sections for all workflows\n- Proper child workflow references\n- Data file inclusions (CSV files)\n- Correct bmad/-relative paths\n\n## Breaking Changes\n\n### File Removals\n- Delete src/modules/bmm/workflows/2-plan-workflows/prd/epics-template.md\n  (replaced by create-epics-and-stories child workflow)\n\n### Workflow Trigger Changes\n- PM agent: ''prd'' → ''create-prd''\n- PM agent: ''gdd'' → ''create-gdd'' \n- New: ''create-epics-and-stories''\n- New: ''validate-prd''\n\n## Impact\n\nThis update significantly improves the BMM module''s ability to:\n- Adapt to different project types and scales\n- Guide users through discovery naturally vs mechanically\n- Generate higher quality planning documents\n- Support complex domains with specialized knowledge\n- Scale from Level 0 quick changes to Level 4 enterprise projects\n\nThe workflows now feel like collaborative discovery sessions with an expert consultant rather than form-filling exercises.\nEOF\n)\")",
-      "Bash(git commit:*)",
-      "Bash(git log:*)",
-      "Bash(git mv:*)",
-      "Bash(test:*)",
-      "Bash(find:*)",
+      "Bash(git commit -m \"$(cat <<''EOF''\nrefactor: comprehensive workflow modernization and standardization\n\n## Major Improvements\n\n### 1. Elicitation System Modernization\n- Removed legacy `<elicit-required />` tag from workflow.xml\n- Replaced with direct `<invoke-task halt=\"true\">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>` pattern\n- More explicit, self-documenting, and eliminates indirection layer\n- Added strategic elicitation points across all planning workflows:\n  - PRD: After success criteria, scope, functional requirements, and final review\n  - Create-Epics-And-Stories: After epic proposals and each epic''s stories\n  - Architecture: After decisions, structure, patterns, implementation patterns, and final doc\n  - Updated audit-workflow tag scanner to remove obsolete elicit-required reference\n\n### 2. Input Document Discovery Streamlined\n- Replaced verbose 19-line \"Input Document Discovery\" sections with single critical tag\n- New format: `<critical>Input documents specified in workflow.yaml input_file_patterns...</critical>`\n- Eliminates duplication - workflow.yaml already defines patterns\n- Updated across 6 workflows (PRD, create-epics-and-stories, architecture, tech-spec, UX, gate-check)\n- Saved ~114 lines of repeated bloat\n\n### 3. Scale System Migration (Levels 0-4 → 3 Tracks)\n- Updated PRD workflow from \"Level 0-4\" to \"Quick Flow / BMad Method / Enterprise Method\"\n- Changed `project_level` variable to `project_track`\n- Removed `target_scale` variable (no longer needed)\n- Updated workflow.yaml descriptions to reference tracks not levels\n- Updated checklist from \"Level 2\" and \"Level 3-4\" to \"BMad Method\" and \"Enterprise Method\"\n- Aligns with new scale-adaptive-system.md (3-track methodology)\n\n### 4. Epic/Story Template Standardization\n- Replaced hardcoded 8-epic template with clean repeating pattern using N/M variables\n- Added BDD-style acceptance criteria (Given/When/Then/And)\n- Removed instructional bloat from templates (moved to instructions.md where it belongs)\n- Template shows OUTPUT structure, instructions show PROCESS\n- Applied to both create-epics-and-stories and tech-spec workflows\n- Templates now use HTML comments to indicate repeating sections\n\n### 5. Workflow.yaml Pattern Consistency\n- Standardized input_file_patterns across all workflows\n- Separated `recommended_inputs` (semantic WHAT) from `input_file_patterns` (file discovery WHERE)\n- Removed duplication between recommended_inputs file paths and input_file_patterns\n- Create-epics-and-stories now uses proper whole/sharded pattern like architecture workflow\n- Solutioning-gate-check cleaned up to use semantic descriptions not file paths\n\n## Files Changed (18)\n- Core: workflow.xml (removed elicit-required tag and references)\n- Audit workflow: Updated tag pattern scanner\n- PRD workflow: Elicitation points, track migration, input discovery\n- Create-epics-and-stories: Template rebuild, BDD format, elicitation, input patterns\n- Tech-spec: Template rebuild, BDD format, input discovery\n- UX Design: Input discovery streamlined\n- Architecture: Elicitation at 5 key decision points, input discovery\n- Gate-check: Input pattern cleanup, input discovery\n\n## Impact\n- More consistent elicitation across workflows\n- Cleaner, more maintainable templates\n- Better separation of concerns (templates vs instructions)\n- Aligned with v6 3-track scale system\n- Reduced bloat and duplication significantly\nEOF\n)\")",
+      "Bash(git push)",
       "Bash(git tag:*)",
+      "Bash(git log:*)",
+      "Bash(git commit:*)",
       "Bash(git push:*)",
       "Bash(npm publish:*)"
     ],

package/CHANGELOG.md

@@ -2,6 +2,311 @@
 
 ## [Unreleased]
 
+## [6.0.0-alpha.5]
+
+**Release: November 4, 2025**
+
+This alpha release represents a major refinement of BMM workflows, documentation accuracy, and the introduction of the revolutionary 3-track scale system. The focus is on workflow consistency, eliminating bloat, and providing accurate, reality-based guidance for modern AI-driven development.
+
+### 🎯 3-Track Scale System - Revolutionary Simplification
+
+**From 5 Levels to 3 Clear Tracks:**
+
+The BMM scale system has been dramatically simplified from a confusing 5-level hierarchy (Levels 0-4) to 3 intuitive, preference-driven tracks:
+
+- **Quick Flow** - Fast, lightweight development for small changes and quick iterations
+- **BMad Method** - Balanced approach for most development projects
+- **Enterprise Method** - Comprehensive methodology for large-scale, mission-critical systems
+
+**Key Changes:**
+
+- Replaced `project_level` variable with `project_track` throughout all workflows
+- Updated 8 workflow path YAML files to reflect new track naming (removed level-based paths)
+- Simplified workflow-init to guide users based on preference, not artificial "levels"
+- Updated all documentation to reference tracks instead of levels
+- Eliminated confusing "target_scale" variable (no longer needed)
+
+**Impact:**
+
+Users now choose development approach based on **project needs and team preference**, not arbitrary complexity levels. This aligns with how real teams actually work and removes decision paralysis.
+
+**Documentation Updated:**
+
+- `scale-adaptive-system.md` - Complete rewrite around 3-track methodology (756 line overhaul)
+- `quick-start.md` - Updated to reference tracks
+- `brownfield-guide.md` - Track-based guidance instead of level-based
+- `glossary.md` - New track definitions, removed level references
+- `workflow-status/init/instructions.md` - Major rewrite for track-based initialization (865 lines)
+
+### ✨ Workflow Modernization & Standardization
+
+**1. Elicitation System Modernization:**
+
+- Removed legacy `<elicit-required />` XML tag from core workflow.xml
+- Replaced with explicit `<invoke-task halt="true">adv-elicit.xml</invoke-task>` pattern
+- More self-documenting and eliminates confusing indirection layer
+- Added strategic elicitation points across all planning workflows:
+  - **PRD:** After success criteria, scope, functional requirements, and final review
+  - **Create-Epics-And-Stories:** After epic proposals and each epic's stories
+  - **Architecture:** After decisions, structure, patterns, implementation patterns, and final doc
+- Updated audit-workflow to remove obsolete elicit-required tag scanning
+
+**2. Input Document Discovery Streamlined:**
+
+- Replaced verbose 19-line "Input Document Discovery" sections with single critical tag
+- New concise format: `<critical>Input documents specified in workflow.yaml input_file_patterns...</critical>`
+- Eliminates duplication (workflow.yaml already defines patterns - why repeat them?)
+- Updated across 6 workflows: PRD, create-epics-and-stories, architecture, tech-spec, UX, gate-check
+- **Saved ~114 lines of repeated bloat**
+
+**3. Epic/Story Template Standardization:**
+
+- Replaced hardcoded 8-epic templates with clean repeating patterns using N/M variables
+- Added BDD-style acceptance criteria (Given/When/Then/And) for better clarity
+- Removed instructional bloat from templates (moved to instructions.md where it belongs)
+- **Principle:** Templates show OUTPUT structure, instructions show PROCESS
+- Applied to both create-epics-and-stories and tech-spec workflows
+- Templates now use HTML comments to clearly indicate repeating sections
+
+**4. Workflow.yaml Pattern Consistency:**
+
+- Standardized `input_file_patterns` across all workflows
+- Separated `recommended_inputs` (semantic WHAT) from `input_file_patterns` (file discovery WHERE)
+- Removed duplication between recommended_inputs file paths and input_file_patterns
+- Create-epics-and-stories now uses proper whole/sharded pattern like architecture workflow
+- Solutioning-gate-check cleaned up to use semantic descriptions not file paths
+
+**Files Changed:** 18 files across core, planning, and solutioning workflows
+
+### 📚 Documentation Accuracy Overhaul
+
+**Agent YAML as Source of Truth:**
+
+Fixed critical documentation inaccuracies by treating agent YAML files as the authoritative source:
+
+**agents-guide.md Corrections:**
+
+- Fixed Game Developer workflow names (dev-story → develop-story, added story-done)
+- Added agent name "Paige" to Technical Writer (matches naming pattern)
+- Corrected epic-tech-context ownership (Architect → SM agent across all docs)
+- Updated agent reference tables to reflect actual capabilities from YAML configs
+
+**workflows-implementation.md Corrections:**
+
+- Fixed epic-tech-context agent attribution in 3 locations (Architect → SM)
+- Updated multi-agent workflow ownership table
+- Aligned all workflow descriptions with actual agent YAML definitions
+
+**Impact:** Zero hallucination risk - documentation now accurately reflects what agents can actually do.
+
+### 🏗️ Brownfield Development Reality Check
+
+**Rewrote brownfield-guide.md Phase 0 Section:**
+
+Replaced oversimplified 3-scenario model with **real-world guidance** for messy brownfield projects:
+
+**New Scenarios (4 instead of 3):**
+
+- **Scenario A:** No documentation → `document-project` workflow (existing)
+- **Scenario B:** Docs exist but massive/outdated/incomplete → **document-project** (NEW - very common case)
+- **Scenario C:** Good docs but massive files → **shard-doc → index-docs** (NEW - handles >500 line files)
+- **Scenario D:** Confirmed AI-optimized docs → Skip Phase 0 (correctly marked as RARE)
+
+**Key Additions:**
+
+- Default recommendation: "Run document-project unless you have confirmed, trusted, AI-optimized docs"
+- Quality assessment checklist (current, AI-optimized, comprehensive, trusted)
+- Massive document handling guidance (>500 lines, 10+ sections triggers shard-doc)
+- Explicit explanation of why regenerating is better than indexing bad docs
+- Impact explanation: how outdated docs break AI workflows (token limits, wrong assumptions, broken integrations)
+
+**Principle:** "When in doubt, run document-project" - Better to spend 10-30 minutes generating fresh docs than waste hours debugging AI agents with bad documentation.
+
+### 🚀 PM/UX Evolution for Enterprise Agentic Development
+
+**New Section: The Evolving Role of Product Managers & UX Designers**
+
+Added comprehensive forward-looking guidance based on **November 2025 industry research**:
+
+**Industry Trends:**
+
+- 56% of product professionals cite AI/ML as top strategic focus
+- PRD-to-Code automation: build and deploy apps in 10-15 minutes (current state)
+- By 2026: Roles converging into "Full-Stack Product Lead" (PM + Design + Engineering)
+- Very high salaries for AI Agent PMs who orchestrate autonomous development systems
+
+**Role Transformation:**
+
+- PMs evolving from spec writers → code orchestrators
+- Writing AI-optimized PRDs that **feed agentic pipelines directly**
+- UX designers generating production code with Figma-to-code tools
+- Technical fluency becoming **table stakes**, not optional
+- Reviewing PRs from AI agents alongside human developers
+
+**How BMad Method Enables This Future (10 Ways):**
+
+1. AI-Executable PRD Generation - PRDs become work packages for cloud agents
+2. Automated Epic/Story Breakdown - No more manual story refinement sessions
+3. Human-in-the-Loop Architecture - PMs learn while validating technical decisions
+4. Cloud Agentic Pipeline Vision - Current (2025) + Future (2026) roadmap with diagrams
+5. UX Design Integration - Designs validated through working prototypes
+6. PM Technical Skills Development - Learn by doing through conversational workflows
+7. Organizational Leverage - 1 PM → 20-50 AI agents (5-10× productivity multiplier)
+8. Quality Consistency - What gets built matches what was specified
+9. Rapid Prototyping - Hours to validate ideas vs months
+10. Career Path Evolution - Positions PMs for emerging AI Agent PM, Full-Stack Product Lead roles
+
+**Cloud Agentic Pipeline Vision:**
+
+```
+Current (2025): PM PRD → Stories → Human devs + BMad agents → PRs → Review → Deploy
+Future (2026): PM PRD → Stories → Cloud AI agents → Auto PRs → Review → Auto-merge → Deploy
+Time savings: 6-8 weeks → 2-5 days
+```
+
+**What Remains Human:**
+
+- Product vision, empathy, creativity, judgment, ethics
+- PMs spend MORE time on human elements (AI handles execution)
+- Product leaders become "builder-thinkers" not just spec writers
+
+### 📖 Document Tightening
+
+**enterprise-agentic-development.md Overhaul:**
+
+- Reduced from 1207 → 640 lines (47% reduction)
+- 10× more BMad-centric - every section ties back to how BMad enables the future
+- Removed redundant examples, consolidated sections, kept actionable insights
+- Stronger value propositions for PMs, UX, enterprise teams throughout
+
+**Key Message:** "The future isn't AI replacing PMs—it's AI-augmented PMs becoming 10× more powerful through BMad Method."
+
+### 🛠️ Infrastructure & Quality
+
+**Agent Naming Consistency:**
+
+- Renamed `paige.agent.yaml` → `tech-writer.agent.yaml` (matches agent naming pattern)
+- Updated all references across documentation and workflow files
+
+**README Updates:**
+
+- Updated local installation instructions
+- Better hierarchy and clearer CTAs in root README
+
+### 🔄 Breaking Changes
+
+**Variable Renames:**
+
+- `project_level` → `project_track` in PRD and all planning workflows
+- Removed `target_scale` variable (no longer needed with 3-track system)
+
+**Workflow Path Files:**
+
+- Removed 9 level-based workflow paths (brownfield-level-0, greenfield-level-3, etc.)
+- Added 6 new track-based workflow paths (quick-flow-greenfield, method-brownfield, enterprise-greenfield, etc.)
+
+**Workflow Triggers:**
+
+- Tech-spec workflow descriptions updated to reference tracks not levels
+
+### 📊 Impact Summary
+
+These changes bring BMM from alpha.4's solid foundation to alpha.5's **production-ready professionalism**:
+
+- **Accuracy:** Documentation matches YAML source of truth (zero hallucination risk)
+- **Simplicity:** 3-track system eliminates decision paralysis and artificial complexity
+- **Reality:** Brownfield guidance handles messy real-world scenarios, not idealized ones
+- **Forward-looking:** PM/UX evolution section positions BMad as essential framework for emerging roles
+- **Consistency:** Standardized elicitation, input discovery, and template patterns across all workflows
+- **Maintainability:** 47% documentation reduction + ~114 lines of bloat removed from workflows
+- **Actionable:** Concrete workflows, commands, examples throughout all guidance
+
+Users now have **trustworthy, reality-based, future-oriented guidance** for using BMad Method in both current workflows and emerging agentic development patterns.
+
+### 📦 Files Changed
+
+**Core & Infrastructure (3 files):**
+
+- `bmad/core/tasks/workflow.xml` - Removed elicit-required tag
+- `src/core/tasks/workflow.xml` - Removed elicit-required tag
+- `package.json` - Version bump
+
+**Documentation (8 files):**
+
+- `src/modules/bmm/docs/README.md` - Track references
+- `src/modules/bmm/docs/agents-guide.md` - Accuracy fixes, agent ownership corrections
+- `src/modules/bmm/docs/brownfield-guide.md` - Phase 0 reality check, track migration
+- `src/modules/bmm/docs/enterprise-agentic-development.md` - PM/UX evolution, 47% reduction
+- `src/modules/bmm/docs/faq.md` - Track references
+- `src/modules/bmm/docs/glossary.md` - Track definitions, removed levels
+- `src/modules/bmm/docs/quick-spec-flow.md` - Track references
+- `src/modules/bmm/docs/scale-adaptive-system.md` - Complete 3-track rewrite
+
+**Workflow Paths (14 files):**
+
+- Removed: 9 level-based paths (brownfield-level-0 through greenfield-level-4)
+- Added: 6 track-based paths (quick-flow/method/enterprise × greenfield/brownfield)
+
+**Planning Workflows (11 files):**
+
+- PRD workflow: Elicitation, track migration, input discovery, checklist updates
+- Create-epics-and-stories: Template rebuild, BDD format, elicitation, input patterns
+- Tech-spec: Template rebuild, BDD format, input discovery
+- Architecture: Elicitation points, input discovery
+
+**Solutioning Workflows (2 files):**
+
+- UX Design: Input discovery streamlined
+- Gate-check: Input pattern cleanup, semantic descriptions
+
+**Build & Utilities (2 files):**
+
+- Audit workflow: Updated tag scanner (removed elicit-required)
+- Workflow status init: Track-based initialization logic
+
+**Total: 40+ files changed**
+
+---
+
+### Installation
+
+```bash
+npx bmad-method@6.0.0-alpha.5 install
+```
+
+For upgrading from alpha.4:
+
+```bash
+# Backup your customizations first
+npx bmad-method@6.0.0-alpha.5 install
+```
+
+### Migration Notes
+
+If upgrading from v6.0.0-alpha.4:
+
+1. **Scale System Change:** The 5-level system (Levels 0-4) is now 3 tracks (Quick Flow, BMad Method, Enterprise Method)
+   - Existing projects continue to work - workflows auto-detect track from context
+   - New projects will use track-based initialization
+   - Review `docs/scale-adaptive-system.md` for the new mental model
+
+2. **Workflow Improvements:**
+   - Better elicitation at strategic decision points (you'll be asked for input more frequently)
+   - Cleaner templates with BDD acceptance criteria
+   - More consistent input document discovery
+
+3. **Documentation Accuracy:**
+   - Agent capabilities now match YAML definitions exactly
+   - Brownfield guidance handles real-world messy scenarios
+   - PM/UX evolution section shows future of AI-driven development
+
+4. **Agent Naming:** Technical Writer agent file renamed (paige.agent.yaml → tech-writer.agent.yaml)
+   - No functional impact - just internal naming consistency
+
+5. **No Breaking Changes:** Existing project structures, workflow outputs, and customizations remain compatible
+
+---
+
 ## [6.0.0-alpha.4]
 
 **Release: November 2, 2025**