chore(release): 4.24.0 [skip ci]

# [4.24.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.23.0...v4.24.0) (2025-07-02)

### Bug Fixes

* corrected cursor agent update instructions ([84e394a](84e394ac11))

### Features

* workflow plans introduced, preliminary feature under review ([731589a](731589aa28))

.github/FUNDING.yml

@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: bmad
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ""
+labels: ""
+assignees: ""
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Steps to Reproduce**
+What lead to the bug and can it be reliable recreated - if so with what steps.
+
+**PR**
+If you have an idea to fix and would like to contribute, please indicate here you are working on a fix, or link to a proposed PR to fix the issue. Please review the contribution.md - contributions are always welcome!
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Please be Specific if relevant**
+Model(s) Used:
+Agentic IDE Used:
+WebSite Used:
+Project Language:
+BMad Method version:
+
+**Screenshots or Links**
+If applicable, add screenshots or links (if web sharable record) to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here. The more information you can provide, the easier it will be to suggest a fix or resolve

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ""
+labels: ""
+assignees: ""
+---
+
+**Did you discuss the idea first in Discord Server (#general-dev)**
+Yes/No - Link to thread. If no, please after posting request also share the link in the channel so it can be easily discussed.
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.gitignore

@@ -19,4 +19,9 @@ Thumbs.db
 CLAUDE.md
 .ai/*
 test-project-install/*
-sample-project/*
+sample-project/*
+.claude
+.bmad-core
+.bmad-creator-tools
+.gemini
+.bmad*/

.vscode/extensions.json

@@ -1,6 +0,0 @@
-{
-	"recommendations": [
-		"davidanson.vscode-markdownlint",
-		"streetsidesoftware.code-spell-checker"
-	]
-}

.vscode/settings.json

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

CHANGELOG.md

@@ -1,3 +1,131 @@
+# [4.24.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.23.0...v4.24.0) (2025-07-02)
+
+
+### Bug Fixes
+
+* corrected cursor agent update instructions ([84e394a](https://github.com/bmadcode/BMAD-METHOD/commit/84e394ac11136d9cf8164cefc9ca8e298e8ef0ec))
+
+
+### Features
+
+* workflow plans introduced, preliminary feature under review ([731589a](https://github.com/bmadcode/BMAD-METHOD/commit/731589aa287c31ea120e232b4dcc07e9790500ff))
+
+# [4.23.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.22.1...v4.23.0) (2025-07-01)
+
+
+### Features
+
+* VS Code Copilot integration ([#284](https://github.com/bmadcode/BMAD-METHOD/issues/284)) ([1a4ca4f](https://github.com/bmadcode/BMAD-METHOD/commit/1a4ca4ffa630c2d4156bdd7a040d4c2274801757))
+
+## [4.22.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.22.0...v4.22.1) (2025-06-30)
+
+
+### Bug Fixes
+
+* update expansion versions ([6905fe7](https://github.com/bmadcode/BMAD-METHOD/commit/6905fe72f6c2abefbfd65729d1be85752130a1d2))
+
+# [4.22.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.21.2...v4.22.0) (2025-06-30)
+
+
+### Features
+
+* create doc more explicit and readme improvement ([a1b30d9](https://github.com/bmadcode/BMAD-METHOD/commit/a1b30d9341d2ceff79db2c7e178860c5ef0d99e5))
+
+## [4.21.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.21.1...v4.21.2) (2025-06-30)
+
+
+### Bug Fixes
+
+* improve create-doc task clarity for template execution ([86d5139](https://github.com/bmadcode/BMAD-METHOD/commit/86d5139aea7097cc5d4ee9da0f7d3e395ce0835e))
+
+## [4.21.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.21.0...v4.21.1) (2025-06-30)
+
+
+### Bug Fixes
+
+* readme clarifies that the installer handles installs upgrades and expansion installation ([9371a57](https://github.com/bmadcode/BMAD-METHOD/commit/9371a5784f6a6f2ad358a72ea0cde9c980357167))
+
+# [4.21.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.20.0...v4.21.0) (2025-06-30)
+
+
+### Bug Fixes
+
+* remove unneeded files ([c48f200](https://github.com/bmadcode/BMAD-METHOD/commit/c48f200727384f37a42f4c6b1a946cb90f2445fe))
+
+
+### Features
+
+* massive installer improvement update ([c151bda](https://github.com/bmadcode/BMAD-METHOD/commit/c151bda93833aa310ccc7c0eabcf483376f9e82a))
+
+# [4.20.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.19.2...v4.20.0) (2025-06-29)
+
+
+### Features
+
+* Massive documentation refactor, added explanation of the new expanded role of the QA agent that will make your code quality MUCH better. 2 new diagram clearly explain the role of the pre dev ideation cycle (prd and architecture) and the details of how the dev cycle works. ([c881dcc](https://github.com/bmadcode/BMAD-METHOD/commit/c881dcc48ff827ddfe8653aa364a021a66ce66eb))
+
+## [4.19.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.19.1...v4.19.2) (2025-06-28)
+
+
+### Bug Fixes
+
+* docs update and correction ([2408068](https://github.com/bmadcode/BMAD-METHOD/commit/240806888448bb3a42acfd2f209976d489157e21))
+
+## [4.19.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.19.0...v4.19.1) (2025-06-28)
+
+
+### Bug Fixes
+
+* discord link ([2ea806b](https://github.com/bmadcode/BMAD-METHOD/commit/2ea806b3af58ad37fcb695146883a9cd3003363d))
+
+# [4.19.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.18.0...v4.19.0) (2025-06-28)
+
+
+### Bug Fixes
+
+* expansion install config ([50d17ed](https://github.com/bmadcode/BMAD-METHOD/commit/50d17ed65d40f6688f3b6e62732fb2280b6b116e))
+
+
+### Features
+
+* install for ide now sets up rules also for expansion agents! ([b82978f](https://github.com/bmadcode/BMAD-METHOD/commit/b82978fd38ea789a799ccc1373cfb61a2001c1e0))
+
+# [4.18.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.17.0...v4.18.0) (2025-06-28)
+
+
+### Features
+
+* expansion teams can now include core agents and include their assets automatically ([c70f1a0](https://github.com/bmadcode/BMAD-METHOD/commit/c70f1a056b0f6e3c805096ee5d27f0a3640fb00c))
+* remove hardcoding from installer for agents, improve expansion pack installation to its own locations, common files moved to common folder ([95e833b](https://github.com/bmadcode/BMAD-METHOD/commit/95e833beebc3a60f73a7a1c67d534c8eb6bf48fd))
+
+# [4.17.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.16.1...v4.17.0) (2025-06-27)
+
+
+### Features
+
+* add GEMINI.md to agent context files ([#272](https://github.com/bmadcode/BMAD-METHOD/issues/272)) ([b557570](https://github.com/bmadcode/BMAD-METHOD/commit/b557570081149352e4efbef8046935650f6ecea1))
+
+## [4.16.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.16.0...v4.16.1) (2025-06-26)
+
+
+### Bug Fixes
+
+* remove accidental folder add ([b1c2de1](https://github.com/bmadcode/BMAD-METHOD/commit/b1c2de1fb58029f68e021faa90cd5d5faf345198))
+
+# [4.16.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.15.0...v4.16.0) (2025-06-26)
+
+
+### Features
+
+* repo builds all rules sets for supported ides for easy copy if desired ([ea945bb](https://github.com/bmadcode/BMAD-METHOD/commit/ea945bb43f6ea50594910b954c72e79f96a8504c))
+
+# [4.15.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.14.1...v4.15.0) (2025-06-26)
+
+
+### Features
+
+* Add Gemini CLI Integration ([#271](https://github.com/bmadcode/BMAD-METHOD/issues/271)) ([44b9d7b](https://github.com/bmadcode/BMAD-METHOD/commit/44b9d7bcb5cbb6de5a15d8f2ec7918d186ac9576))
+
 ## [4.14.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.14.0...v4.14.1) (2025-06-26)
 
 

CONTRIBUTING.md

@@ -4,10 +4,15 @@ Thank you for considering contributing to this project! This document outlines t
 
 🆕 **New to GitHub or pull requests?** Check out our [beginner-friendly Pull Request Guide](docs/how-to-contribute-with-pull-requests.md) first!
 
-📋 **Before contributing**, please read our [Guiding Principles](GUIDING-PRINCIPLES.md) to understand the BMAD Method's core philosophy and architectural decisions.
+📋 **Before contributing**, please read our [Guiding Principles](GUIDING-PRINCIPLES.md) to understand the BMad Method's core philosophy and architectural decisions.
 
 Also note, we use the discussions feature in GitHub to have a community to discuss potential ideas, uses, additions and enhancements.
 
+💬 **Discord Community**: Join our [Discord server](https://discord.gg/g6ypHytrCB) for real-time discussions:
+
+- **#general-dev** - Technical discussions, feature ideas, and development questions
+- **#bugs-issues** - Bug reports and issue discussions
+
 ## Code of Conduct
 
 By participating in this project, you agree to abide by our Code of Conduct. Please read it before participating.
@@ -16,16 +21,35 @@ By participating in this project, you agree to abide by our Code of Conduct. Ple
 
 ### Reporting Bugs
 
-- Check if the bug has already been reported in the Issues section
-- Include detailed steps to reproduce the bug
-- Include any relevant logs or screenshots
+1. **Check existing issues** first to avoid duplicates
+2. **Use the bug report template** when creating a new issue - it will guide you through providing:
+   - Clear bug description
+   - Steps to reproduce
+   - Expected vs actual behavior
+   - Model/IDE/BMad version details
+   - Screenshots or links if applicable
+3. **Consider discussing in Discord** (#bugs-issues channel) for quick help
+4. **Indicate if you're working on a fix** to avoid duplicate efforts
 
 ### Suggesting Features
 
-- Check if the feature has already been suggested in the Issues section, and consider using the discussions tab in GitHub also. Explain the feature in detail and why it would be valuable.
+1. **Discuss first in Discord** (#general-dev channel) - the feature request template asks if you've done this
+2. **Check existing issues and discussions** to avoid duplicates
+3. **Use the feature request template** when creating an issue - it will guide you through:
+   - Confirming Discord discussion
+   - Describing the problem it solves
+   - Explaining your solution
+   - Listing alternatives considered
+4. **Be specific** about why this feature would benefit the BMad community
 
 ### Pull Request Process
 
+⚠️ **Before starting work:**
+
+1. **For bugs**: Check if an issue exists (create one using the bug template if not)
+2. **For features**: Ensure you've discussed in Discord (#general-dev) AND created a feature request issue
+3. **For large changes**: Always open an issue first to discuss alignment
+
 Please only propose small granular commits! If its large or significant, please discuss in the discussions tab and open up an issue first. I do not want you to waste your time on a potentially very large PR to have it rejected because it is not aligned or deviates from other planned changes. Communicate and lets work together to build and improve this great community project!
 
 **Important**: All contributions must align with our [Guiding Principles](GUIDING-PRINCIPLES.md). Key points:
@@ -95,6 +119,15 @@ Example breakdown:
 6. Push to your branch (`git push origin feature/your-feature-name`)
 7. Open a Pull Request against the main branch
 
+## Issue Templates
+
+We use GitHub issue templates to ensure all necessary information is provided:
+
+- **Bug Reports**: Automatically guides you through providing reproduction steps, environment details, and expected behavior
+- **Feature Requests**: Requires Discord discussion confirmation and asks for problem/solution descriptions
+
+Using these templates helps maintainers understand and address your contribution faster.
+
 ## Pull Request Description Guidelines
 
 Keep PR descriptions short and to the point following this template:
@@ -111,6 +144,7 @@ Keep your PR description concise and focused. Use this template:
 ## Why
 
 [1-2 sentences explaining WHY this change is needed]
+Fixes #[issue number] (if applicable)
 
 ## How
 

GUIDING-PRINCIPLES.md

@@ -1,6 +1,6 @@
-# BMAD Method Guiding Principles
+# BMad Method Guiding Principles
 
-The BMAD Method is a natural language framework for AI-assisted software development. These principles ensure contributions maintain the method's effectiveness.
+The BMad Method is a natural language framework for AI-assisted software development. These principles ensure contributions maintain the method's effectiveness.
 
 ## Core Principles
 

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 Brian AKA BMad AKA Bmad Code
+Copyright (c) 2025 Brian AKA BMad AKA BMad Code
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -1,76 +1,141 @@
-# BMAD-METHOD
+# BMad-METHOD: Universal AI Agent Framework
 
 [![Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=version)](https://www.npmjs.com/package/bmad-method)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 [![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org)
-[![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/g6ypHytrCB)
+[![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj)
 
-**AI-Powered Agile Development Framework** - Transform your software development with specialized AI agents that work as your complete Agile team.
+Foundations in Agentic Agile Driven Development, known as the Breakthrough Method of Agile AI-Driven Development, but it is so much more. Transform any domain with specialized AI expertise: software development, entertainment, creative writing, business strategy to personal wellness just to name a few.
 
-📺 **[Subscribe to BMadCode on YouTube](https://www.youtube.com/@BMadCode?sub_confirmation=1)** - V4 walkthrough and comprehensive guide coming soon!
+**[Subscribe to BMadCode on YouTube](https://www.youtube.com/@BMadCode?sub_confirmation=1)**
 
-⭐ **If you find this project helpful or useful, please give it a star!** It helps others discover BMAD-METHOD and you will be notified of updates!
+**[Join our Discord Community](https://discord.gg/gk8jAdXWmj)** - A growing community for AI enthusiasts! Get help, share ideas, explore AI agents & frameworks, collaborate on tech projects, enjoy hobbies, and help each other succeed. Whether you're stuck on BMad, building your own agents, or just want to chat about the latest in AI - we're here for you!
 
-## 🔄 Important: Keeping Your BMAD Installation Updated
+⭐ **If you find this project helpful or useful, please give it a star in the upper right hand corner!** It helps others discover BMad-METHOD and you will be notified of updates!
 
-**Stay up-to-date effortlessly!** If you already have BMAD-METHOD installed in your project, simply run:
+## Quick Navigation
+
+### 🚨 MUST READ: Understanding the BMAD Workflow
+
+**Before diving in, review these critical workflow diagrams that explain how BMAD works:**
+
+1. **[Planning Workflow (Web UI)](docs/user-guide.md#the-planning-workflow-web-ui)** - How to create PRD and Architecture documents
+2. **[Core Development Cycle (IDE)](docs/user-guide.md#the-core-development-cycle-ide)** - How SM, Dev, and QA agents collaborate through story files
+
+> ⚠️ **These diagrams explain 90% of BMad Method Agentic Agile flow confusion** - Understanding the PRD+Architecture creation and the SM/Dev/QA workflow and how agents pass notes through story files is essential - and also explains why this is NOT taskmaster or just a simple task runner!
+
+### What would you like to do?
+
+- **[Build software with Full Stack Agile AI Team](#-quick-start)** → Quick Start Instruction
+- **[Learn how to use BMAD](docs/user-guide.md)** → Complete user guide and walkthrough
+- **[See available AI agents](#available-agents)** → Specialized roles for your team
+- **[Explore non-technical uses](#-beyond-software-development---expansion-packs)** → Creative writing, business, wellness, education
+- **[Create my own AI agents](#creating-your-own-expansion-pack)** → Build agents for your domain
+- **[Browse ready-made expansion packs](expansion-packs/)** → Game dev, DevOps, infrastructure and get inspired with ideas and examples
+- **[Understand the architecture](docs/core-architecture.md)** → Technical deep dive
+- **[Join the community](https://discord.gg/g6ypHytrCB)** → Get help and share ideas
+
+### Popular Use Cases
+
+- **Software Development** - [Quick Start](#-quick-start) | [User Guide](docs/user-guide.md) | [Workflow Guides](#documentation--guides)
+- **Game Development** - [2D Phaser Pack](expansion-packs/bmad-2d-phaser-game-dev/)
+- **Business Strategy** - [Full Guide](docs/expansion-packs.md#business-strategy-pack)
+- **Creative Writing** - [Full Guide](docs/expansion-packs.md#creative-writing-pack)
+- **DevOps/Infrastructure** - [Infrastructure Pack](expansion-packs/bmad-infrastructure-devops/)
+
+### Quick Links
+
+- **[Installation](#installation)** → Get started in minutes
+- **[Documentation](#documentation--guides)** → All guides and references
+- **[Contributing](#contributing)** → Help improve BMAD
+- **[Support](#support)** → Get help and connect
+
+## Important: Keep Your BMad Installation Updated
+
+**Stay up-to-date effortlessly!** If you already have BMad-METHOD installed in your project, simply run:
 
 ```bash
 npx bmad-method install
+# OR
+git pull
+npm run install:bmad
 ```
 
-The installer will:
+This will:
 
 - ✅ Automatically detect your existing v4 installation
-- ✅ Update only the files that have changed
+- ✅ Update only the files that have changed and add new files
 - ✅ Create `.bak` backup files for any custom modifications you've made
 - ✅ Preserve your project-specific configurations
 
-This makes it easy to benefit from the latest improvements, bug fixes, and new agents without losing your customizations!
+This makes it easy to benefit from the latest improvements, bug fixes, and new agents without losing your customizations! If for some reason this fails, you can rename or remove your .bmad-code folder and run the install again. The main thing to look out for is if you have set up custom modes that are not file driven (Cursor is the only one at this time that is not done through project files lagging behind) - you will want to ensure your sm and dev custom modes especially are kept up to date.
 
-## 🚀 Quick Start
+## Quick Start
 
-### Fastest Start: Web UI (2 minutes) 🏃‍♂️
+### One Command for Everything (IDE Installation)
+
+**Just run one of these commands:**
+
+```bash
+npx bmad-method install
+# OR if you already have BMad installed:
+git pull
+npm run install:bmad
+```
+
+This single command handles:
+
+- **New installations** - Sets up BMad in your project
+- **Upgrades** - Updates existing installations automatically
+- **Expansion packs** - Installs any expansion packs you've added to package.json
+
+> **That's it!** Whether you're installing for the first time, upgrading, or adding expansion packs - these commands do everything.
+
+**Prerequisites**: [Node.js](https://nodejs.org) v20+ required
+
+### Fastest Start: Web UI (2 minutes)
 
 1. **Get the bundle**: Copy `dist/teams/team-fullstack.txt` (from this repository)
 2. **Create AI agent**: Create a new Gemini Gem or CustomGPT
 3. **Upload & configure**: Upload the file and set instructions: "Your critical operating instructions are attached, do not break character as directed"
 4. **Start Ideating and Planning**: Start chatting! Type `*help` to see available commands or pick an agent like `*analyst` to start right in on creating a brief.
 
-> 💡 **All pre-built bundles are in the `dist/` folder** - ready to copy and use immediately!
+> **All pre-built bundles are in the `dist/` folder** - ready to copy and use immediately!
 
-### IDE Quick Start (5 minutes) 💻
+### Alternative: Clone and Build
 
-**Prerequisites**: Install [Node.js](https://nodejs.org) (v20 or higher)
-
-Run `npx bmad-method install`
-
-This installs all agents and configures them for your IDE. If you have an existing v3 installation, it will offer to upgrade it automatically.
-
-## 📋 Table of Contents
-
-- [Overview](#overview)
-- [Installation](#installation)
-- [Available Agents](#available-agents)
-- [Usage](#usage)
-- [Project Structure](#project-structure)
-- [Contributing](#contributing)
+```bash
+git clone https://github.com/bmadcode/bmad-method.git
+npm run install:bmad # build and install all to a destination folder
+```
 
 ## Overview
 
-BMAD-METHOD (Breakthrough Method of Agile AI-Driven Development) revolutionizes software development by providing specialized AI agents for every role in an Agile team. Each agent has deep expertise in their domain and can collaborate to deliver complete software projects.
+The BMad Method (Breakthrough Method of Agile Agentic-Driven Development) elevates 'Vibe Coding' by providing specialized AI agents for every role in an Agile team. Each agent has deep expertise in their domain helping you really plan and execute on your vision while keeping the agents on the rails even through complex application plans.
 
-### Why BMAD?
-
-- **🎯 Specialized Expertise**: Each agent is an expert in their specific role
-- **🔄 True Agile Workflow**: Follows real Agile methodologies and best practices
-- **📦 Modular Design**: Use one agent or an entire team
-- **🛠️ IDE Integration**: Works seamlessly with Cursor, Claude Code, and Windsurf
-- **🌐 Platform Agnostic**: Use with ChatGPT, Claude, Gemini, or any AI platform
+Unlike systems like Task Master, or inbuilt Task tool, the BMad Methods agile flow does so much more. With most systems, you give your idea in a few sentences at most, and the system churns out a plan, task list, lets you review it and then starts executing. Where the BMad agile flow is different is you can choose to have more upfront planning and architecture specification to ensure the system is built in a sustainable way, not a vibe coded spaghetti mess. When producing the PRD and Architectures (full stack, front end and or backend), the Agents work with you back and forth using advanced proven LLM techniques and techniques also based in psychology to produce beyond the average slop LLMs and Task generators will on their own. This truly is a system of Human in the Loop produces markedly better results.
 
 ## Installation
 
-### Method 1: Pre-Built Web Bundles (Fastest) 📦
+### Method 1: CLI Installer (For IDEs)
+
+**Just run one command:**
+
+```bash
+npx bmad-method install
+# OR if you already have BMad installed:
+npm run install:bmad
+```
+
+**This single command does everything:**
+
+- Installs BMad for the first time
+- Updates existing installations
+- Adds any expansion packs from your package.json
+
+**Prerequisites**: Install [Node.js](https://nodejs.org) v20+ first
+
+### Method 2: Pre-Built Web Bundles (For Web UI)
 
 For ChatGPT, Claude, or Gemini web interfaces:
 
@@ -81,49 +146,73 @@ For ChatGPT, Claude, or Gemini web interfaces:
 3. Set instructions: "Your critical operating instructions are attached, do not break character as directed"
 4. Type `/help` to see available commands
 
-### Method 2: CLI Installer (For IDEs) 🎯
-
-**Prerequisites**: Install [Node.js](https://nodejs.org) v20+ first
-
-Install directly into your project: `npx bmad-method install`
-
 **Supported IDEs:**
 
 The BMad Method works with any IDE, but has built-in integration for:
 
-- `cursor` - Cursor IDE with @agent commands
+- `cursor` - Cursor IDE with manual rule @agent commands
 - `claude-code` - Claude Code with /agent commands
-- `windsurf` - Windsurf with @agent commands
+- `cline` - Cline Rules integration
+- `gemini-cli` - Gemini with @agent commands
+- `windsurf` - Windsurf with manual rule @agent commands
 - `roo` - Roo Code with custom modes (see `.roomodes`)
-- More coming soon - BUT ITS easy to use with ANY IDE - just copy the bmad-code folder to your project, and rename it .bmad-code.
+- `vs-code-copilot` - VS Code with GitHub Copilot agent mode integration
 
 ## Available Agents
 
 ### Core Development Team
 
-| Agent       | Role               | Specialty                                     |
-| ----------- | ------------------ | --------------------------------------------- |
-| `analyst`   | Business Analyst   | market analysis, brainstorming, project brief |
-| `pm`        | Product Manager    | Product strategy, roadmaps, PRDs              |
-| `architect` | Solution Architect | System design, technical architecture         |
-| `dev`       | Developer          | Code implementation across all technologies   |
-| `qa`        | QA Specialist      | Testing strategies, quality assurance         |
-| `ux-expert` | UX Designer        | User experience, UI design, prototypes        |
-| `po`        | Product Owner      | Backlog management, story validation          |
-| `sm`        | Scrum Master       | Sprint planning, story creation               |
+| Agent       | Role               | Specialty                                                                                    |
+| ----------- | ------------------ | -------------------------------------------------------------------------------------------- |
+| `analyst`   | Business Analyst   | market analysis, brainstorming, project brief creation                                       |
+| `pm`        | Product Manager    | Product strategy, MVP Decisioning, PRD creation with Epics                                   |
+| `architect` | Solution Architect | System design, technical full stack, front end or backend architecture                       |
+| `ux-expert` | UX Designer        | User experience, UI design, prompts for V0, Lovable, and others                              |
+| `po`        | Product Owner      | Ensure PRD and Architecture are aligned, and changes from architecture end up in PRD stories |
+| `sm`        | Scrum Master       | High level epics and stories transformed into detailed dev stories with tasks and subtasks   |
+| `dev`       | Developer          | Code implementation across all technologies - follows the detailed SM created story          |
+| `qa`        | QA Specialist      | Detailed review of the devs ready for review story, refactor and propose issues and changes  |
 
-### Meta Agents
+### BMad Agents
 
-| Agent               | Role             | Specialty                                                           |
-| ------------------- | ---------------- | ------------------------------------------------------------------- |
-| `bmad-orchestrator` | Team Coordinator | Multi-agent workflows, role switching, is part of every team bundle |
-| `bmad-master`       | Universal Expert | All capabilities without switching                                  |
+| Agent               | Role             | Specialty                                                                                                                |
+| ------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| `bmad-orchestrator` | Team Coordinator | Helps guide you and answers your questions with its massive knowledge base, and guides you through Multi-agent workflows |
+| `bmad-master`       | Universal Expert | All capabilities without switching (Except Dev)                                                                          |
+
+## Advanced Features
+
+### Dynamic Dependencies
+
+Each agent only loads the resources it needs, keeping context windows lean.
+
+### Template System
+
+Rich templates for all document types:
+
+- Product Requirements (PRD)
+- Architecture Documents
+- User Stories
+- Test Plans
+- And more...
+
+Templates are unique in that they are embedded with the LLM instructions also for further working with you to prompt and elicit the best from you and your agile agent team member - allowing for unique coaching and customization options. While there is a single create-doc task, the possibilities are endless when you expand the templates into more doc types, or customize with your own docs embedded with the templating markup and LLM instruction framework that is core to the BMad Method.
+
+### Slash Star Commands
+
+Ask the agent you are using for help with /help (in the web) or \*help in the ide to see what commands are available!
+
+### Advanced Elicitation
+
+Many of the Agents and Templates for docs, and some tasks, include Advanced Elicitation directives based on the latest in LLM interactions and pro level prompt engineering guidance. With this, you can push the Agents further than ever before. If an agent proposes an idea, or an architecture - you can push it further with optional elicitations where it will have to really expand on, defend, or produce other options and prove its suggestion was better. This is a necessary step if you want the absolute best beyond accepting the generated average responses the LLMs think you want to hear for their first response. Some of this is interactive, and some of this is baked into the core prompting engine that powers the LLM progression through various tasks and template flows.
 
 ## Usage
 
-### With IDE Integration
+The BMAD Method follows a structured Agile workflow with specialized AI agents. For complete usage instructions and walkthroughs, see the **[User Guide](docs/user-guide.md)**.
 
-After installation with `--ide` flag:
+### Quick Start Examples
+
+#### With IDE Integration
 
 ```bash
 # In Cursor
@@ -136,118 +225,29 @@ After installation with `--ide` flag:
 @dev Implement story 1.3
 ```
 
-### With Web UI (ChatGPT/Claude/Gemini)
+#### With Web UI
 
-After uploading a bundle you can ask /help of the agent to learn what it can do
+After uploading a bundle, type `/help` to see available commands.
 
-### CLI Commands
+### Key Resources
 
-```bash
-# List all available agents
-npx bmad-method list
-
-# Install or update (automatically detects existing installations)
-npx bmad-method install
-
-# Check installation status
-npx bmad-method status
-```
-
-### Upgrading from V3 to V4
-
-If you have an existing BMAD-METHOD V3 project, simply run the installer in your project directory:
-
-```bash
-npx bmad-method install
-# The installer will automatically detect your V3 installation and offer to upgrade
-```
-
-The upgrade process will:
-
-1. Create a backup of your V3 files in `.bmad-v3-backup/`
-2. Install the new V4 `.bmad-core/` structure
-3. Migrate your documents (PRD, Architecture, Stories, Epics)
-4. Set up IDE integration for all V4 agents
-5. Create an install manifest for future updates
-
-After upgrading:
-
-1. Review your documents in the `docs/` folder - if you had a PRD or architecture in your old project, copy it from the backup to the docs folder if they are not there.
-2. Optionally run the `doc-migration-task` to align your documents with V4 templates - you can do this with your agent my saying something like: 'run {drag in task} against {drag prd or arch file from docs} to align with {drag the template from .bmad-core/templates/full-stack-architecture.md}
-3. If you have separate front-end and backend architecture docs you can modify step 2 to merge both into a single full stack architecture or separate Front and Back end.
-
-The reason #2 and 3 are optional is because now BMad V4 makes sharding optional for the SM. See [Core Configuration](#-core-configuration-new-in-v4)
-
-**Note**: The agents in `.bmad-core/` fully replace the items in `bmad-agent/` - you can remove the backup folder versions.
-
-### 🔧 Core Configuration (NEW in V4)
-
-**Critical**: V4 introduces `bmad-core/core-config.yml` - a powerful configuration file that enables BMAD to work seamlessly with any project structure, whether it's V4-optimized or legacy. You can even now use non-standard PRDs and architectures!
-
-#### What is core-config.yml?
-
-This configuration file tells BMAD agents exactly where to find your project documents and how they're structured. It's the key to V4's flexibility and backwards compatibility.
-
-#### Key Features
-
-- **Version Awareness**: Agents understand if your PRD/Architecture follows V4 conventions or earlier versions
-- **Flexible Document Locations**: Works whether your epics are embedded in PRD or properly sharded
-- **Developer Context**: Define which files the dev agent should always load
-- **Debug Support**: Built-in logging for troubleshooting story implementation
-
-#### Why It Matters
-
-- **Use BMAD with ANY project structure** - V3, V4, or custom layouts
-- **No forced migrations** - Keep your existing document organization
-- **Customize developer workflow** - Specify exactly which files provide context
-- **Seamless upgrades** - Start with V3 docs and gradually adopt V4 patterns
-
-See the [detailed core-config.yml guide](docs/user-guide.md#core-configuration-coreconfigyml) for configuration examples and best practices.
-
-## Teams & Workflows
-
-### Pre-Configured Teams
-
-Save context by using specialized teams:
-
-- **Team All**: Complete Agile team with all 10 agents
-- **Team Fullstack**: Frontend + Backend development focus
-- **Team No-UI**: Backend/API development without UX
-
-### Workflows
-
-Structured approaches for different scenarios:
-
-- **Greenfield**: Starting new projects (fullstack/service/UI)
-- **Brownfield**: Enhancing existing projects
-- **Simple**: Quick prototypes and MVPs
-- **Complex**: Enterprise and large-scale projects
+- **[Complete User Guide](docs/user-guide.md)** - Full walkthrough from project inception to completion
+- **[CLI Commands](docs/user-guide.md#cli-commands)** - Installation, updates, and management
+- **[Upgrading from V3](docs/user-guide.md#upgrading-from-v3-to-v4)** - Migration instructions
+- **[Core Configuration](docs/user-guide.md#core-configuration-coreconfigyml)** - V4's flexible project structure support
+- **[Teams & Workflows](docs/user-guide.md#team-configurations)** - Pre-configured agent teams
 
 ## Project Structure
 
-```plaintext
-.bmad-core/
-├── agents/          # Individual agent definitions
-├── agent-teams/     # Team configurations
-├── workflows/       # Development workflows
-├── templates/       # Document templates (PRD, Architecture, etc.)
-├── tasks/           # Reusable task definitions
-├── checklists/      # Quality checklists
-├── data/            # Knowledge base
-└── web-bundles/     # Optional can be added if you use the install command and select this folder as a destination for the build bundle files
+See the **[Core Architecture](docs/core-architecture.md)** for the complete source tree and detailed explanations of each component.
 
-tools/
-├── cli.js           # Build tool
-├── installer/       # NPX installer
-└── lib/             # Build utilities
+### Key Directories
 
-expansion-packs/     # Domain-specific add-ons (Technical & Non-Technical)
-
-dist/                # 📦 PRE-BUILT BUNDLES (Ready to use!)
-├── agents/          # Individual agent bundles (.txt files)
-├── teams/           # Team bundles (.txt files)
-└── expansion-packs/ # Expansion pack bundles
-```
+- **`.bmad-core/`** - Heart of the framework (agents, templates, workflows)
+- **`dist/`** - Pre-built bundles ready for web UI use
+- **`expansion-packs/`** - Domain-specific extensions
+- **`tools/`** - Build and installation utilities
+- **`docs/`** - Your project documentation (PRD, architecture, stories)
 
 ### 📦 Pre-Built Bundles (dist/ folder)
 
@@ -269,89 +269,6 @@ dist/                # 📦 PRE-BUILT BUNDLES (Ready to use!)
 
 **For Web UI usage**: Simply copy any `.txt` file from `dist/` and upload to your AI platform!`
 
-## Advanced Features
-
-### Dynamic Dependencies
-
-Each agent only loads the resources it needs, keeping context windows lean.
-
-### Template System
-
-Rich templates for all document types:
-
-- Product Requirements (PRD)
-- Architecture Documents
-- User Stories
-- Test Plans
-- And more...
-
-### Slash Star Commands
-
-Ask the agent you are using for help with /help (in the web) or \*help in the ide to see what commands are available!
-
-## Expansion Packs - Beyond Software Development
-
-BMAD Method's natural language framework isn't limited to software development. Create specialized agents for ANY domain:
-
-### Technical Expansion Packs
-
-- 🎮 **Game Development** - Game designers, level creators, narrative writers
-- 🏗️ **Infrastructure/DevOps** - Cloud architects, security specialists, SRE agents
-- 📱 **Mobile Development** - iOS/Android specialists, UX designers
-- 🔗 **Blockchain/Web3** - Smart contract developers, DeFi architects
-
-### Non-Technical Expansion Packs
-
-- 💼 **Business Strategy** - Strategic planners, market analysts, business coaches
-- 💪 **Health & Wellness** - Fitness coaches, nutrition advisors, meditation guides
-- 🎨 **Creative Arts** - Story writers, world builders, character developers
-- 📚 **Education** - Curriculum designers, tutors, learning coaches
-- 🧠 **Personal Development** - Life coaches, goal setters, habit builders
-- 🏢 **Professional Services** - Legal advisors, medical protocols, research assistants
-
-### Creating Your Own Expansion Pack
-
-The BMAD framework can support any domain where structured AI assistance is valuable:
-
-1. Define specialized agents with domain expertise
-2. Create task procedures for common workflows
-3. Build templates for domain-specific outputs
-4. Package as an expansion pack for others to use
-
-📖 **[Read the full Expansion Packs Guide](docs/expansion-packs.md)** for detailed examples and inspiration!
-
-🛠️ **[Use the Expansion Pack Creator](expansion-packs/expansion-creator/README.md)** to build your own!
-
-## Contributing
-
-**We're excited about contributions and welcome your ideas, improvements, and expansion packs!** 🎉
-
-### Before Contributing - MUST READ
-
-To ensure your contribution aligns with the BMAD Method and gets merged smoothly:
-
-1. 📋 **Read [CONTRIBUTING.md](CONTRIBUTING.md)** - Our contribution guidelines, PR requirements, and process
-2. 🎯 **Read [GUIDING-PRINCIPLES.md](GUIDING-PRINCIPLES.md)** - Core principles that keep BMAD powerful through simplicity
-3. 🆕 **New to GitHub?** Start with our [Pull Request Guide](docs/how-to-contribute-with-pull-requests.md)
-
-### Key Points to Remember
-
-- Keep dev agents lean (save context for coding!)
-- Use small, focused files over large branching ones
-- Reuse existing tasks (like `create-doc`) instead of creating duplicates
-- Consider expansion packs for domain-specific features
-- All contributions must follow our natural language, markdown-based approach
-
-We're building something amazing together - let's keep it simple, powerful, and focused! 💪
-
-### Development Setup
-
-```bash
-git clone https://github.com/bmadcode/bmad-method.git
-cd bmad-method
-npm install
-```
-
 ## Documentation & Guides
 
 ### Architecture & Technical
@@ -364,10 +281,50 @@ npm install
 
 - 📚 [Universal BMAD Workflow Guide](docs/bmad-workflow-guide.md) - Core workflow that applies to all IDEs
 - 🏗️ [Working in the Brownfield Guide](docs/working-in-the-brownfield.md) - Complete guide for enhancing existing projects
-- 🎯 [Cursor Guide](docs/cursor-guide.md) - Complete workflow for Cursor users
-- 🤖 [Claude Code Guide](docs/claude-code-guide.md) - Complete workflow for Claude Code users
-- 🌊 [Windsurf Guide](docs/windsurf-guide.md) - Complete workflow for Windsurf users
-- 🦘 [Roo Code Guide](docs/roo-code-guide.md) - Complete workflow for Roo Code users
+
+### IDE-Specific Guides
+
+- 🎯 [Cursor Guide](docs/agentic-tools/cursor-guide.md) - Setup and usage for Cursor
+- 🤖 [Claude Code Guide](docs/agentic-tools/claude-code-guide.md) - Setup and usage for Claude Code
+- 🌊 [Windsurf Guide](docs/agentic-tools/windsurf-guide.md) - Setup and usage for Windsurf
+- 🦘 [Roo Code Guide](docs/agentic-tools/roo-code-guide.md) - Setup and usage for Roo Code
+- 🔧 [Cline Guide](docs/agentic-tools/cline-guide.md) - Setup and usage for Cline (VS Code)
+- ✨ [Gemini CLI Guide](docs/agentic-tools/gemini-cli-guide.md) - Setup and usage for Gemini CLI
+- 💻 [VS Code Copilot Guide](docs/agentic-tools/vs-code-copilot-guide.md) - Setup and usage for VS Code with GitHub Copilot
+
+## 🌟 Beyond Software Development - Expansion Packs
+
+While BMad excels at software development, its natural language framework can structure expertise in ANY domain. Expansion packs transform BMAD into a universal AI agent system for creative writing, business strategy, health & wellness, education, and much more.
+
+### Available Expansion Packs
+
+#### Technical Domains
+
+- 🎮 **[Game Development](expansion-packs/bmad-2d-phaser-game-dev/)** - Complete game studio team with designers, developers, and narrative writers
+- 🏗️ **[Infrastructure/DevOps](expansion-packs/bmad-infrastructure-devops/)** - Cloud architects, security specialists, SRE experts
+- 📱 **Mobile Development** - iOS/Android specialists, mobile UX designers
+- 🔗 **Blockchain/Web3** - Smart contract developers, DeFi architects
+
+#### Non-Technical Domains
+
+- 💼 **Business Strategy** - Strategic planners, market analysts, business coaches
+- 💪 **Health & Wellness** - Fitness coaches, nutrition advisors, meditation guides
+- 🎨 **Creative Arts** - Story writers, world builders, character developers
+- 📚 **Education** - Curriculum designers, tutors, learning coaches
+- 🧠 **Personal Development** - Life coaches, goal setters, habit builders
+- 🏢 **Professional Services** - Legal advisors, content creators, research assistants
+
+### Creating Your Own Expansion Pack
+
+Transform your expertise into AI agents:
+
+1. **Identify your domain** - What knowledge do you want to share?
+2. **Design specialized agents** - Each with unique expertise and personality
+3. **Create reusable tasks** - Standard procedures in your field
+4. **Build professional templates** - Structured outputs for consistency
+5. **Share with the community** - Help others benefit from your expertise
+
+📖 **[Read the full Expansion Packs Guide](docs/expansion-packs.md)** - Detailed examples, inspiration, and technical details
 
 ## Support
 
@@ -394,7 +351,39 @@ See [versions.md](docs/versions.md) for detailed version history and migration g
 
 Created by Brian (BMad) Madison
 
----
+## Contributing
+
+**We're excited about contributions and welcome your ideas, improvements, and expansion packs!** 🎉
+
+### Before Contributing - MUST READ
+
+To ensure your contribution aligns with the BMad Method and gets merged smoothly:
+
+1. 📋 **Read [CONTRIBUTING.md](CONTRIBUTING.md)** - Our contribution guidelines, PR requirements, and process
+2. 🎯 **Read [GUIDING-PRINCIPLES.md](GUIDING-PRINCIPLES.md)** - Core principles that keep BMAD powerful through simplicity
+3. 🆕 **New to GitHub?** Start with our [Pull Request Guide](docs/how-to-contribute-with-pull-requests.md)
+
+### Key Points to Remember
+
+- Keep dev agents lean (save context for coding!)
+- Use small, focused files over large branching ones
+- Reuse existing tasks (like `create-doc`) instead of creating duplicates
+- Consider expansion packs for domain-specific features and not improvements to the core system (those belong in the core system)
+- All contributions must follow our natural language, markdown-based templating approach with template embedded LLM instructions and elicitations
+
+We're building something amazing together - let's keep it simple, powerful, and focused! 💪
+
+### Development Setup
+
+Want to help improve the BMad Method. Fork n' Clone the repo
+
+```bash
+git clone https://github.com/bmadcode/bmad-method.git
+cd bmad-method
+
+npm run build # rebuild the dist folder
+npm run install:bmad # build and install all to a destination folder
+```
 
 [![Contributors](https://contrib.rocks/image?repo=bmadcode/bmad-method)](https://github.com/bmadcode/bmad-method/graphs/contributors)
 

bmad-core/agents/bmad-master.md

@@ -26,6 +26,9 @@ persona:
     - Process (*) commands immediately
 startup:
   - Greet the user with your name and role, and inform of the *help command.
+  - Check for active workflow plan using utils#plan-management
+  - "If plan exists: Show brief status - Active plan detected: {workflow} - {progress}%"
+  - "If plan exists: Suggest next step based on plan"
   - CRITICAL: Do NOT scan filesystem or load any resources during startup
   - CRITICAL: Do NOT run discovery tasks automatically
   - Wait for user request before any tool use
@@ -37,16 +40,24 @@ commands:  # All commands require * prefix when used (e.g., *help)
   - status: Current context
   - task {template|util|checklist|workflow}: Execute
   - list {task|template|util|checklist|workflow}: List resources by type
+  - plan: Create workflow plan (for complex projects)
+  - plan-status: Show current workflow plan progress
+  - plan-update: Update workflow plan status
   - exit: Exit (confirm)
   - yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
   - doc-out: Output full document
 fuzzy-matching:
   - 85% confidence threshold
   - Show numbered list if unsure
+workflow-guidance:
+  - When user asks about workflows, offer: "Would you like me to create a workflow plan first? (*plan)"
+  - For complex projects, suggest planning before execution
+  - Plan command maps to create-workflow-plan task
 execution:
   - NEVER use tools during startup - only announce and wait
   - Runtime discovery ONLY when user requests specific resources
   - Workflow: User request → Runtime discovery → Load resource → Execute instructions → Guide inputs → Provide feedback
+  - For workflow requests: Suggest *plan command first for complex projects
   - Suggest related resources after completion
 dependencies:
   tasks:
@@ -58,12 +69,14 @@ dependencies:
     - correct-course
     - create-deep-research-prompt
     - create-doc
+    - create-workflow-plan
     - document-project
     - create-next-story
     - execute-checklist
     - generate-ai-frontend-prompt
     - index-docs
     - shard-doc
+    - update-workflow-plan
   templates:
     - agent-tmpl
     - architecture-tmpl
@@ -81,7 +94,7 @@ dependencies:
     - bmad-kb
     - technical-preferences
   utils:
-    - agent-switcher.ide
+    - plan-management
     - template-format
     - workflow-management
   workflows:

bmad-core/agents/bmad-orchestrator.md

@@ -31,6 +31,9 @@ startup:
   - Announce: Introduce yourself as the BMAD Orchestrator, explain you can coordinate agents and workflows
   - IMPORTANT: Tell users that all commands start with * (e.g., *help, *agent, *workflow)
   - Mention *help shows all available commands and options
+  - Check for active workflow plan using utils#plan-management
+  - "If plan exists: Show 📋 Active plan: {workflow} ({progress}% complete). Use *plan-status for details."
+  - "If plan exists: Suggest next action based on plan progress"
   - Assess user goal against available agents and workflows in this bundle
   - If clear match to an agent's expertise, suggest transformation with *agent command
   - If project-oriented, suggest *workflow-guidance to explore options
@@ -45,6 +48,9 @@ commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
   task: Run a specific task (list if name not specified)
   workflow: Start a specific workflow (list if name not specified)
   workflow-guidance: Get personalized help selecting the right workflow
+  plan: Create detailed workflow plan before starting
+  plan-status: Show current workflow plan progress
+  plan-update: Update workflow plan status
   checklist: Execute a checklist (list if name not specified)
   yolo: Toggle skip confirmations mode
   party-mode: Group chat with all agents
@@ -68,6 +74,9 @@ help-display-template: |
   Workflow Commands:
   *workflow [name] .... Start specific workflow (list if no name)
   *workflow-guidance .. Get personalized help selecting the right workflow
+  *plan ............... Create detailed workflow plan before starting
+  *plan-status ........ Show current workflow plan progress
+  *plan-update ........ Update workflow plan status
   
   Other Commands:
   *yolo ............... Toggle skip confirmations mode
@@ -109,6 +118,8 @@ workflow-guidance:
   - Understand each workflow's purpose, options, and decision points
   - Ask clarifying questions based on the workflow's structure
   - Guide users through workflow selection when multiple options exist
+  - For complex projects, offer to create a workflow plan using create-workflow-plan task
+  - When appropriate, suggest: "Would you like me to create a detailed workflow plan before starting?"
   - For workflows with divergent paths, help users choose the right path
   - Adapt questions to the specific domain (e.g., game dev vs infrastructure vs web dev)
   - Only recommend workflows that actually exist in the current bundle
@@ -117,10 +128,13 @@ dependencies:
   tasks:
     - advanced-elicitation
     - create-doc
+    - create-workflow-plan
     - kb-mode-interaction
+    - update-workflow-plan
   data:
     - bmad-kb
   utils:
+    - plan-management
     - workflow-management
     - template-format
 ```

bmad-core/agents/dev.md

@@ -50,7 +50,7 @@ task-execution:
   updates-ONLY:
     - "Checkboxes: [ ] not started | [-] in progress | [x] complete"
     - "Debug Log: | Task | File | Change | Reverted? |"
-    - "Completion Notes: Deviations only, <50 words"
+    - "Completion Notes: Deviations from AC or tasks during execution only, <50 words"
     - "Change Log: Requirement changes only"
     - "File List: CRITICAL - Maintain complete list of ALL files created/modified during implementation"
   blocking: "Unapproved deps | Ambiguous after story check | 3 failures | Missing config | Failing validations"

bmad-core/core-config.yml

@@ -1,3 +1,4 @@
+version: 4.21.1
 markdownExploder: true
 prd:
   prdFile: docs/prd.md
@@ -17,4 +18,8 @@ devLoadAlwaysFiles:
   - docs/architecture/source-tree.md
 devDebugLog: .ai/debug-log.md
 devStoryLocation: docs/stories
-agentCoreDump: .ai/core-dump{n}.md
+workflow:
+  planFile: docs/workflow-plan.md
+  trackProgress: true
+  enforceSequence: false
+  updateOnCompletion: true

bmad-core/data/bmad-kb.md

@@ -78,7 +78,7 @@ BMAD transforms you into a "Vibe CEO" - directing a team of specialized AI agent
 5. Type `/help` to see available commands
 
 #### Option 2: IDE Integration
-**Best for**: Cursor, Claude Code, Windsurf, Cline, Roo Code users
+**Best for**: Cursor, Claude Code, Windsurf, Cline, Roo Code, VS Code Copilot users
 
 ```bash
 # Interactive installation (recommended)
@@ -93,6 +93,7 @@ npx bmad-method install
   - **Windsurf**: Built-in AI capabilities
   - **Cline**: VS Code extension with AI features
   - **Roo Code**: Web-based IDE with agent support
+  - **VS Code Copilot**: AI-powered coding assistant
 
 **Note for VS Code Users**: BMAD-METHOD assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMAD agents. The installer includes built-in support for Cline and Roo.
 
@@ -278,6 +279,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 - **Cursor**: `@agent-name` (e.g., `@bmad-master`)
 - **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
 - **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
+- **VS Code Copilot**: Open the Chat view (`⌃⌘I` on Mac, `Ctrl+Alt+I` on Windows/Linux) and select **Agent** from the chat mode selector.
 
 **Chat Management Guidelines**:
 - **Claude Code, Cursor, Windsurf**: Start new chats when switching agents
@@ -719,7 +721,7 @@ Expansion packs extend BMAD-METHOD beyond traditional software development into
 ### Using Expansion Packs
 
 1. **Browse Available Packs**: Check `expansion-packs/` directory
-2. **Get Inspiration**: See `docs/expansion-pack-ideas.md` for detailed examples
+2. **Get Inspiration**: See `docs/expansion-packs.md` for detailed examples and ideas
 3. **Install via CLI**: 
    ```bash
    npx bmad-method install

bmad-core/tasks/core-dump.md

@@ -1,74 +0,0 @@
-# Core Dump Task
-
-## Purpose
-
-To create a concise memory recording file (`.ai/core-dump-n.md`) that captures the essential context of the current agent session, enabling seamless continuation of work in future agent sessions. This task ensures persistent context across agent conversations while maintaining minimal token usage for efficient context loading.
-
-## Inputs for this Task
-
-- Current session conversation history and accomplishments
-- Files created, modified, or deleted during the session
-- Key decisions made and procedures followed
-- Current project state and next logical steps
-- User requests and agent responses that shaped the session
-
-## Task Execution Instructions
-
-### 0. Check Existing Core Dump
-
-Before proceeding, check if `.ai/core-dump.md` already exists:
-
-- If file exists, ask user: "Core dump file exists. Should I: 1. Overwrite, 2. Update, 3. Append or 4. Create new?"
-- **Overwrite**: Replace entire file with new content
-- **Update**: Merge new session info with existing content, updating relevant sections
-- **Append**: Add new session as a separate entry while preserving existing content
-- **Create New**: Create a new file, appending the next possible -# to the file, such as core-dump-3.md if 1 and 2 already exist.
-- If file doesn't exist, proceed with creation of `core-dump-1.md`
-
-### 1. Analyze Session Context
-
-- Review the entire conversation to identify key accomplishments
-- Note any specific tasks, procedures, or workflows that were executed
-- Identify important decisions made or problems solved
-- Capture the user's working style and preferences observed during the session
-
-### 2. Document What Was Accomplished
-
-- **Primary Actions**: List the main tasks completed concisely
-- **Story Progress**: For story work, use format "Tasks Complete: 1-6, 8. Next Task Pending: 7, 9"
-- **Problem Solving**: Document any challenges encountered and how they were resolved
-- **User Communications**: Summarize key user requests, preferences, and discussion points
-
-### 3. Record File System Changes (Concise Format)
-
-- **Files Created**: `filename.ext` (brief purpose/size)
-- **Files Modified**: `filename.ext` (what changed)
-- **Files Deleted**: `filename.ext` (why removed)
-- Focus on essential details, avoid verbose descriptions
-
-### 4. Capture Current Project State
-
-- **Project Progress**: Where the project stands after this session
-- **Current Issues**: Any blockers or problems that need resolution
-- **Next Logical Steps**: What would be the natural next actions to take
-
-### 5. Create/Update Core Dump File
-
-Based on user's choice from step 0, handle the file accordingly:
-
-### 6. Optimize for Minimal Context
-
-- Keep descriptions concise but informative
-- Use abbreviated formats where possible (file sizes, task numbers)
-- Focus on actionable information rather than detailed explanations
-- Avoid redundant information that can be found in project documentation
-- Prioritize information that would be lost without this recording
-- Ensure the file can be quickly scanned and understood
-
-### 7. Validate Completeness
-
-- Verify all significant session activities are captured
-- Ensure a future agent could understand the current state
-- Check that file changes are accurately recorded
-- Confirm next steps are clear and actionable
-- Verify user communication style and preferences are noted

bmad-core/tasks/create-brownfield-story.md

@@ -0,0 +1,355 @@
+# Create Brownfield Story Task
+
+## Purpose
+
+Create detailed, implementation-ready stories for brownfield projects where traditional sharded PRD/architecture documents may not exist. This task bridges the gap between various documentation formats (document-project output, brownfield PRDs, epics, or user documentation) and executable stories for the Dev agent.
+
+## When to Use This Task
+
+**Use this task when:**
+
+- Working on brownfield projects with non-standard documentation
+- Stories need to be created from document-project output
+- Working from brownfield epics without full PRD/architecture
+- Existing project documentation doesn't follow BMAD v4+ structure
+- Need to gather additional context from user during story creation
+
+**Use create-next-story when:**
+
+- Working with properly sharded PRD and v4 architecture documents
+- Following standard greenfield or well-documented brownfield workflow
+- All technical context is available in structured format
+
+## Task Execution Instructions
+
+### 0. Check Workflow Plan and Documentation Context
+
+[[LLM: Check for workflow plan first, then available documentation]]
+
+#### 0.1 Check Workflow Plan
+
+- Load core-config.yml and check if `workflow.trackProgress: true`
+- If yes, check for active plan at `workflow.planFile`
+- If plan exists:
+  - Verify story creation aligns with current plan step
+  - If out of sequence, warn user (enforce based on config)
+  - Note which step this story creation corresponds to
+
+#### 0.2 Determine Documentation Context
+
+Check for available documentation in this order:
+
+1. **Sharded PRD/Architecture** (docs/prd/, docs/architecture/)
+   - If found, recommend using create-next-story task instead
+
+2. **Brownfield Architecture Document** (docs/brownfield-architecture.md or similar)
+   - Created by document-project task
+   - Contains actual system state, technical debt, workarounds
+
+3. **Brownfield PRD** (docs/prd.md)
+   - May contain embedded technical details
+
+4. **Epic Files** (docs/epics/ or similar)
+   - Created by brownfield-create-epic task
+
+5. **User-Provided Documentation**
+   - Ask user to specify location and format
+
+### 1. Story Identification and Context Gathering
+
+#### 1.1 Identify Story Source
+
+Based on available documentation:
+
+- **From Brownfield PRD**: Extract stories from epic sections
+- **From Epic Files**: Read epic definition and story list
+- **From User Direction**: Ask user which specific enhancement to implement
+- **No Clear Source**: Work with user to define the story scope
+
+#### 1.2 Gather Essential Context
+
+[[LLM: For brownfield stories, you MUST gather enough context for safe implementation. Be prepared to ask the user for missing information.]]
+
+**Required Information Checklist:**
+
+- [ ] What existing functionality might be affected?
+- [ ] What are the integration points with current code?
+- [ ] What patterns should be followed (with examples)?
+- [ ] What technical constraints exist?
+- [ ] Are there any "gotchas" or workarounds to know about?
+
+If any required information is missing, ask the user:
+
+```
+I need additional context for this brownfield story:
+
+Missing Information:
+- [List specific missing items]
+
+Please provide:
+1. [Specific question about integration]
+2. [Specific question about patterns]
+3. [Specific question about constraints]
+
+Or point me to documentation that contains this information.
+```
+
+### 2. Extract Technical Context from Available Sources
+
+#### 2.1 From Document-Project Output
+
+If using brownfield-architecture.md from document-project:
+
+- **Technical Debt Section**: Note any workarounds affecting this story
+- **Key Files Section**: Identify files that will need modification
+- **Integration Points**: Find existing integration patterns
+- **Known Issues**: Check if story touches problematic areas
+- **Actual Tech Stack**: Verify versions and constraints
+
+#### 2.2 From Brownfield PRD
+
+If using brownfield PRD:
+
+- **Technical Constraints Section**: Extract all relevant constraints
+- **Integration Requirements**: Note compatibility requirements
+- **Code Organization**: Follow specified patterns
+- **Risk Assessment**: Understand potential impacts
+
+#### 2.3 From User Documentation
+
+[[LLM: When working with non-BMAD documentation, actively extract and organize the information into categories the Dev agent will need]]
+
+Ask the user to help identify:
+
+- Relevant technical specifications
+- Existing code examples to follow
+- Integration requirements
+- Testing approaches used in the project
+
+### 3. Story Creation with Progressive Detail Gathering
+
+#### 3.1 Create Initial Story Structure
+
+Start with the story template, filling in what's known:
+
+```markdown
+# Story {{Enhancement Title}}
+
+## Status: Draft
+
+## Story
+As a {{user_type}},
+I want {{enhancement_capability}},
+so that {{value_delivered}}.
+
+## Context Source
+[[LLM: Document where story requirements came from]]
+- Source Document: {{document name/type}}
+- Enhancement Type: {{single feature/bug fix/integration/etc}}
+- Existing System Impact: {{brief assessment}}
+```
+
+#### 3.2 Develop Acceptance Criteria
+
+[[LLM: For brownfield, ALWAYS include criteria about maintaining existing functionality]]
+
+Standard structure:
+
+1. New functionality works as specified
+2. Existing {{affected feature}} continues to work unchanged  
+3. Integration with {{existing system}} maintains current behavior
+4. No regression in {{related area}}
+5. Performance remains within acceptable bounds
+
+#### 3.3 Gather Technical Guidance
+
+[[LLM: This is where you'll need to be interactive with the user if information is missing]]
+
+Create Dev Technical Guidance section with available information:
+
+```markdown
+## Dev Technical Guidance
+
+### Existing System Context
+[Extract from available documentation]
+
+### Integration Approach
+[Based on patterns found or ask user]
+
+### Technical Constraints
+[From documentation or user input]
+
+### Missing Information
+[[LLM: List anything you couldn't find that dev will need]]
+- [ ] {{missing item 1}}
+- [ ] {{missing item 2}}
+```
+
+If critical information is missing, pause and ask:
+
+```
+To complete the technical guidance for this story, I need:
+
+1. **{{Missing Category}}**: 
+   - Specifically: {{what you need to know}}
+   - Why needed: {{how it impacts implementation}}
+   
+Can you provide this information or point me to relevant code/docs?
+```
+
+### 4. Task Generation with Safety Checks
+
+#### 4.1 Generate Implementation Tasks
+
+Based on gathered context, create tasks that:
+
+- Include exploration tasks if system understanding is incomplete
+- Add verification tasks for existing functionality
+- Include rollback considerations
+- Reference specific files/patterns when known
+
+Example task structure for brownfield:
+
+```markdown
+## Tasks / Subtasks
+
+- [ ] Task 1: Analyze existing {{component/feature}} implementation
+  - [ ] Review {{specific files}} for current patterns
+  - [ ] Document integration points
+  - [ ] Identify potential impacts
+
+- [ ] Task 2: Implement {{new functionality}}
+  - [ ] Follow pattern from {{example file}}
+  - [ ] Integrate with {{existing component}}
+  - [ ] Maintain compatibility with {{constraint}}
+
+- [ ] Task 3: Verify existing functionality
+  - [ ] Test {{existing feature 1}} still works
+  - [ ] Verify {{integration point}} behavior unchanged
+  - [ ] Check performance impact
+
+- [ ] Task 4: Add tests
+  - [ ] Unit tests following {{project test pattern}}
+  - [ ] Integration test for {{integration point}}
+  - [ ] Update existing tests if needed
+```
+
+### 5. Risk Assessment and Mitigation
+
+[[LLM: CRITICAL for brownfield - always include risk assessment]]
+
+Add section for brownfield-specific risks:
+
+```markdown
+## Risk Assessment
+
+### Implementation Risks
+- **Primary Risk**: {{main risk to existing system}}
+- **Mitigation**: {{how to address}}
+- **Verification**: {{how to confirm safety}}
+
+### Rollback Plan
+- {{Simple steps to undo changes if needed}}
+
+### Safety Checks
+- [ ] Existing {{feature}} tested before changes
+- [ ] Changes can be feature-flagged or isolated
+- [ ] Rollback procedure documented
+```
+
+### 6. Final Story Validation
+
+Before finalizing:
+
+1. **Completeness Check**:
+   - [ ] Story has clear scope and acceptance criteria
+   - [ ] Technical context is sufficient for implementation
+   - [ ] Integration approach is defined
+   - [ ] Risks are identified with mitigation
+
+2. **Safety Check**:
+   - [ ] Existing functionality protection included
+   - [ ] Rollback plan is feasible
+   - [ ] Testing covers both new and existing features
+
+3. **Information Gaps**:
+   - [ ] All critical missing information gathered from user
+   - [ ] Remaining unknowns documented for dev agent
+   - [ ] Exploration tasks added where needed
+
+### 7. Story Output Format
+
+Save the story with appropriate naming:
+
+- If from epic: `docs/stories/epic-{n}-story-{m}.md`
+- If standalone: `docs/stories/brownfield-{feature-name}.md`
+- If sequential: Follow existing story numbering
+
+Include header noting documentation context:
+
+```markdown
+# Story: {{Title}}
+
+<!-- Source: {{documentation type used}} -->
+<!-- Context: Brownfield enhancement to {{existing system}} -->
+
+## Status: Draft
+[Rest of story content...]
+```
+
+### 8. Handoff Communication
+
+Provide clear handoff to the user:
+
+```text
+Brownfield story created: {{story title}}
+
+Source Documentation: {{what was used}}
+Story Location: {{file path}}
+
+Key Integration Points Identified:
+- {{integration point 1}}
+- {{integration point 2}}
+
+Risks Noted:
+- {{primary risk}}
+
+{{If missing info}}: 
+Note: Some technical details were unclear. The story includes exploration tasks to gather needed information during implementation.
+
+Next Steps:
+1. Review story for accuracy
+2. Verify integration approach aligns with your system
+3. Approve story or request adjustments
+4. Dev agent can then implement with safety checks
+```
+
+### 9. Update Workflow Plan (if applicable)
+
+[[LLM: After successful story creation]]
+
+- If workflow plan tracking is enabled and story was created successfully:
+  - Call update-workflow-plan task to mark step complete
+  - Parameters: task: create-brownfield-story, step_id: {from plan check}, status: complete
+  - If plan shows next recommended step, include it in handoff message
+
+## Success Criteria
+
+The brownfield story creation is successful when:
+
+1. Story can be implemented without requiring dev to search multiple documents
+2. Integration approach is clear and safe for existing system
+3. All available technical context has been extracted and organized
+4. Missing information has been identified and addressed
+5. Risks are documented with mitigation strategies
+6. Story includes verification of existing functionality
+7. Rollback approach is defined
+
+## Important Notes
+
+- This task is specifically for brownfield projects with non-standard documentation
+- Always prioritize existing system safety over new features
+- When in doubt, add exploration and verification tasks
+- It's better to ask the user for clarification than make assumptions
+- Each story should be self-contained for the dev agent
+- Include references to existing code patterns when available

bmad-core/tasks/create-doc.md

@@ -1,74 +0,0 @@
-# Create Document from Template Task
-
-## Purpose
-
-- Generate documents from any specified template following embedded instructions from the perspective of the selected agent persona
-
-## Instructions
-
-### 1. Identify Template and Context
-
-- Determine which template to use (user-provided or list available for selection to user)
-
-  - Agent-specific templates are listed in the agent's dependencies under `templates`. For each template listed, consider it a document the agent can create. So if an agent has:
-
-    @{example}
-    dependencies:
-    templates: - prd-tmpl - architecture-tmpl
-    @{/example}
-
-    You would offer to create "PRD" and "Architecture" documents when the user asks what you can help with.
-
-- Gather all relevant inputs, or ask for them, or else rely on user providing necessary details to complete the document
-- Understand the document purpose and target audience
-
-### 2. Determine Interaction Mode
-
-Confirm with the user their preferred interaction style:
-
-- **Incremental:** Work through chunks of the document.
-- **YOLO Mode:** Draft complete document making reasonable assumptions in one shot. (Can be entered also after starting incremental by just typing /yolo)
-
-### 3. Execute Template
-
-- Load specified template from `templates#*` or the /templates directory
-- Follow ALL embedded LLM instructions within the template
-- Process template markup according to `utils#template-format` conventions
-
-### 4. Template Processing Rules
-
-#### CRITICAL: Never display template markup, LLM instructions, or examples to users
-
-- Replace all {{placeholders}} with actual content
-- Execute all [[LLM: instructions]] internally
-- Process `<<REPEAT>>` sections as needed
-- Evaluate ^^CONDITION^^ blocks and include only if applicable
-- Use @{examples} for guidance but never output them
-
-### 5. Content Generation
-
-- **Incremental Mode**: Present each major section for review before proceeding
-- **YOLO Mode**: Generate all sections, then review complete document with user
-- Apply any elicitation protocols specified in template
-- Incorporate user feedback and iterate as needed
-
-### 6. Validation
-
-If template specifies a checklist:
-
-- Run the appropriate checklist against completed document
-- Document completion status for each item
-- Address any deficiencies found
-- Present validation summary to user
-
-### 7. Final Presentation
-
-- Present clean, formatted content only
-- Ensure all sections are complete
-- DO NOT truncate or summarize content
-- Begin directly with document content (no preamble)
-- Include any handoff prompts specified in template
-
-## Important Notes
-
-- Template markup is for AI processing only - never expose to users

bmad-core/tasks/create-next-story.md

@@ -26,6 +26,22 @@ To identify the next logical story based on project progress and epic definition
   - `architecture.architectureSharded`: Whether architecture is sharded
   - `architecture.architectureFile`: Location of monolithic architecture
   - `architecture.architectureShardedLocation`: Location of sharded architecture files
+  - `workflow.trackProgress`: Whether workflow plan tracking is enabled
+  - `workflow.planFile`: Location of workflow plan (if tracking enabled)
+
+### 0.5 Check Workflow Plan (if configured)
+
+[[LLM: Check if workflow plan tracking is enabled]]
+
+- If `workflow.trackProgress: true`, check for active plan at `workflow.planFile`
+- If plan exists:
+  - Parse plan to check if story creation is the expected next step
+  - If out of sequence and `workflow.enforceSequence: true`:
+    - Show warning: "The workflow plan indicates you should complete {expected_step} before creating stories."
+    - Block execution unless user explicitly overrides
+  - If out of sequence and `workflow.enforceSequence: false`:
+    - Show warning but allow continuation with confirmation
+- Continue with story identification after plan check
 
 ### 1. Identify Next Story for Preparation
 
@@ -249,4 +265,13 @@ Provide a summary to the user including:
 - Recommendations for story review before approval
 - Next steps: Story should be reviewed by PO for approval before dev work begins
 
+### 10. Update Workflow Plan (if applicable)
+
+[[LLM: After successful story creation]]
+
+- If `workflow.trackProgress: true` and `workflow.updateOnCompletion: true`:
+  - Call update-workflow-plan task to mark story creation step complete
+  - Parameters: task: create-next-story, step_id: {from plan}, status: complete
+  - If plan shows next step, mention it in completion message
+
 [[LLM: Remember - The success of this task depends on extracting real, specific technical details from the architecture shards. The dev agent should have everything they need in the story file without having to search through multiple documents.]]

bmad-core/tasks/create-workflow-plan.md

@@ -0,0 +1,289 @@
+# Create Workflow Plan Task
+
+## Purpose
+
+Guide users through workflow selection and create a detailed plan document that outlines the selected workflow steps, decision points, and expected outputs. This task helps users understand what will happen before starting a complex workflow and provides a checklist to track progress.
+
+## Task Instructions
+
+### 1. Understand User's Goal
+
+[[LLM: Start with discovery questions to understand what the user wants to accomplish]]
+
+Ask the user:
+
+1. **Project Type**:
+   - Are you starting a new project (greenfield) or enhancing an existing one (brownfield)?
+   - What type of application? (web app, service/API, UI only, full-stack)
+
+2. **For Greenfield**:
+   - Do you need a quick prototype or production-ready application?
+   - Will this have a UI component?
+   - Single service or multiple services?
+
+3. **For Brownfield**:
+   - What's the scope of the enhancement?
+     - Single bug fix or small feature (few hours)
+     - Small enhancement (1-3 stories)
+     - Major feature requiring coordination
+     - Architectural changes or modernization
+   - Do you have existing documentation?
+   - Are you following existing patterns or introducing new ones?
+
+### 2. Recommend Appropriate Workflow
+
+Based on the answers, recommend:
+
+**Greenfield Options:**
+
+- `greenfield-fullstack` - Complete web application
+- `greenfield-service` - Backend API/service only
+- `greenfield-ui` - Frontend only
+
+**Brownfield Options:**
+
+- `brownfield-create-story` - Single small change
+- `brownfield-create-epic` - Small feature (1-3 stories)
+- `brownfield-fullstack` - Major enhancement
+
+**Simplified Option:**
+
+- For users unsure or wanting flexibility, suggest starting with individual agent tasks
+
+### 3. Explain Selected Workflow
+
+[[LLM: Once workflow is selected, provide clear explanation]]
+
+For the selected workflow, explain:
+
+1. **Overview**: What this workflow accomplishes
+2. **Duration**: Estimated time for planning phase
+3. **Outputs**: What documents will be created
+4. **Decision Points**: Where user input will be needed
+5. **Requirements**: What information should be ready
+
+### 4. Create Workflow Plan Document
+
+[[LLM: Generate a comprehensive plan document with the following structure]]
+
+```markdown
+# Workflow Plan: {{Workflow Name}}
+
+<!-- WORKFLOW-PLAN-META
+workflow-id: {{workflow-id}}
+status: active
+created: {{ISO-8601 timestamp}}
+updated: {{ISO-8601 timestamp}}
+version: 1.0
+-->
+
+**Created Date**: {{current date}}
+**Project**: {{project name}}
+**Type**: {{greenfield/brownfield}}
+**Status**: Active
+**Estimated Planning Duration**: {{time estimate}}
+
+## Objective
+
+{{Clear description of what will be accomplished}}
+
+## Selected Workflow
+
+**Workflow**: `{{workflow-id}}`
+**Reason**: {{Why this workflow fits the user's needs}}
+
+## Workflow Steps
+
+### Planning Phase
+
+- [ ] Step 1: {{step name}} <!-- step-id: 1.1, agent: {{agent}}, task: {{task}} -->
+  - **Agent**: {{agent name}}
+  - **Action**: {{what happens}}
+  - **Output**: {{what's created}}
+  - **User Input**: {{if any}}
+
+- [ ] Step 2: {{step name}} <!-- step-id: 1.2, agent: {{agent}}, task: {{task}} -->
+  - **Agent**: {{agent name}}
+  - **Action**: {{what happens}}
+  - **Output**: {{what's created}}
+  - **Decision Point**: {{if any}} <!-- decision-id: D1 -->
+
+{{Continue for all planning steps}}
+
+### Development Phase (IDE)
+
+- [ ] Document Sharding <!-- step-id: 2.1, agent: po, task: shard-doc -->
+  - Prepare documents for story creation
+
+- [ ] Story Development Cycle <!-- step-id: 2.2, repeats: true -->
+  - [ ] Create story (SM agent) <!-- step-id: 2.2.1, agent: sm, task: create-next-story -->
+  - [ ] Review story (optional) <!-- step-id: 2.2.2, agent: analyst, optional: true -->
+  - [ ] Implement story (Dev agent) <!-- step-id: 2.2.3, agent: dev -->
+  - [ ] QA review (optional) <!-- step-id: 2.2.4, agent: qa, optional: true -->
+  - [ ] Repeat for all stories
+
+- [ ] Epic Retrospective (optional) <!-- step-id: 2.3, agent: po, optional: true -->
+
+## Key Decision Points
+
+1. **{{Decision Name}}** (Step {{n}}): <!-- decision-id: D1, status: pending -->
+   - Trigger: {{what causes this decision}}
+   - Options: {{available choices}}
+   - Impact: {{how it affects the workflow}}
+   - Decision Made: _Pending_
+
+{{List all decision points}}
+
+## Expected Outputs
+
+### Planning Documents
+- [ ] {{document 1}} - {{description}}
+- [ ] {{document 2}} - {{description}}
+{{etc...}}
+
+### Development Artifacts
+- [ ] Stories in `docs/stories/`
+- [ ] Implementation code
+- [ ] Tests
+- [ ] Updated documentation
+
+## Prerequisites Checklist
+
+Before starting this workflow, ensure you have:
+
+- [ ] {{prerequisite 1}}
+- [ ] {{prerequisite 2}}
+- [ ] {{prerequisite 3}}
+{{etc...}}
+
+## Customization Options
+
+Based on your project needs, you may:
+- Skip {{optional step}} if {{condition}}
+- Add {{additional step}} if {{condition}}
+- Choose {{alternative}} instead of {{default}}
+
+## Risk Considerations
+
+{{For brownfield only}}
+- Integration complexity: {{assessment}}
+- Rollback strategy: {{approach}}
+- Testing requirements: {{special needs}}
+
+## Next Steps
+
+1. Review this plan and confirm it matches your expectations
+2. Gather any missing prerequisites
+3. Start workflow with: `*task workflow {{workflow-id}}`
+4. Or begin with first agent: `@{{first-agent}}`
+
+## Notes
+
+{{Any additional context or warnings}}
+
+---
+*This plan can be updated as you progress through the workflow. Check off completed items to track progress.*
+```
+
+### 5. Save and Present Plan
+
+1. Save the plan as `docs/workflow-plan.md`
+2. Inform user: "Workflow plan created at docs/workflow-plan.md"
+3. Offer options:
+   - Review the plan together
+   - Start the workflow now
+   - Gather prerequisites first
+   - Modify the plan
+
+### 6. Plan Variations
+
+[[LLM: Adjust plan detail based on workflow complexity]]
+
+**For Simple Workflows** (create-story, create-epic):
+
+- Simpler checklist format
+- Focus on immediate next steps
+- Less detailed explanations
+
+**For Complex Workflows** (full greenfield/brownfield):
+
+- Detailed step breakdowns
+- All decision points documented
+- Comprehensive output descriptions
+- Risk mitigation sections
+
+**For Brownfield Workflows**:
+
+- Include existing system impact analysis
+- Document integration checkpoints
+- Add rollback considerations
+- Note documentation dependencies
+
+### 7. Interactive Planning Mode
+
+[[LLM: If user wants to customize the workflow]]
+
+If user wants to modify the standard workflow:
+
+1. Present workflow steps as options
+2. Allow skipping optional steps
+3. Let user reorder certain steps
+4. Document customizations in plan
+5. Warn about dependencies if steps are skipped
+
+### 8. Execution Guidance
+
+After plan is created, provide clear guidance:
+
+```text
+Your workflow plan is ready! Here's how to proceed:
+
+1. **Review the plan**: Check that all steps align with your goals
+2. **Gather prerequisites**: Use the checklist to ensure you're ready
+3. **Start execution**:
+   - Full workflow: `*task workflow {{workflow-id}}`
+   - Step by step: Start with `@{{first-agent}}`
+4. **Track progress**: Check off steps in the plan as completed
+
+Would you like to:
+a) Review the plan together
+b) Start the workflow now
+c) Gather prerequisites first
+d) Modify the plan
+```
+
+## Success Criteria
+
+The workflow plan is successful when:
+
+1. User clearly understands what will happen
+2. All decision points are documented
+3. Prerequisites are identified
+4. Expected outputs are clear
+5. User feels confident to proceed
+6. Plan serves as useful progress tracker
+
+## Integration with BMad Master and Orchestrator
+
+When used by BMad Master or BMad Orchestrator, this task should:
+
+1. Be offered when user asks about workflows
+2. Be suggested before starting complex workflows
+3. Create a plan that the agent can reference during execution
+4. Allow the agent to track progress against the plan
+
+## Example Usage
+
+```text
+User: "I need to add a payment system to my existing app"
+
+BMad Orchestrator: "Let me help you create a workflow plan for that enhancement. I'll ask a few questions to recommend the best approach..."
+
+[Runs through discovery questions]
+
+BMad Orchestrator: "Based on your answers, I recommend the brownfield-fullstack workflow. Let me create a detailed plan for you..."
+
+[Creates and saves plan]
+
+BMad Orchestrator: "I've created a workflow plan at docs/workflow-plan.md. This shows all the steps we'll go through, what documents will be created, and where you'll need to make decisions. Would you like to review it together?"
+```

bmad-core/tasks/execute-checklist.md

@@ -1,97 +0,0 @@
-# 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.
-
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
-## Available Checklists
-
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
-
-## Instructions
-
-1. **Initial Assessment**
-
-   - If user or the task being run provides a checklist name:
-     - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
-     - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
-   - If no checklist specified:
-     - Ask the user which checklist they want to use
-     - Present the available options from the files in the checklists folder
-   - Confirm if they want to work through the checklist:
-     - Section by section (interactive mode - very time consuming)
-     - All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
-
-2. **Document and Artifact Gathering**
-
-   - Each checklist will specify its required documents/artifacts at the beginning
-   - Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
-
-3. **Checklist Processing**
-
-   If in interactive mode:
-
-   - Work through each section of the checklist one at a time
-   - For each section:
-     - Review all items in the section following instructions for that section embedded in the checklist
-     - Check each item against the relevant documentation or artifacts as appropriate
-     - Present summary of findings for that section, highlighting warnings, errors and non applicable items (rationale for non-applicability).
-     - Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
-
-   If in YOLO mode:
-
-   - Process all sections at once
-   - Create a comprehensive report of all findings
-   - Present the complete analysis to the user
-
-4. **Validation Approach**
-
-   For each checklist item:
-
-   - Read and understand the requirement
-   - Look for evidence in the documentation that satisfies the requirement
-   - Consider both explicit mentions and implicit coverage
-   - Aside from this, follow all checklist llm instructions
-   - Mark items as:
-     - ✅ PASS: Requirement clearly met
-     - ❌ FAIL: Requirement not met or insufficient coverage
-     - ⚠️ PARTIAL: Some aspects covered but needs improvement
-     - N/A: Not applicable to this case
-
-5. **Section Analysis**
-
-   For each section:
-
-   - think step by step to calculate pass rate
-   - Identify common themes in failed items
-   - Provide specific recommendations for improvement
-   - In interactive mode, discuss findings with user
-   - Document any user decisions or explanations
-
-6. **Final Report**
-
-   Prepare a summary that includes:
-
-   - Overall checklist completion status
-   - Pass rates by section
-   - List of failed items with context
-   - Specific recommendations for improvement
-   - Any sections or items marked as N/A with justification
-
-## Checklist Execution Methodology
-
-Each checklist now contains embedded LLM prompts and instructions that will:
-
-1. **Guide thorough thinking** - Prompts ensure deep analysis of each section
-2. **Request specific artifacts** - Clear instructions on what documents/access is needed
-3. **Provide contextual guidance** - Section-specific prompts for better validation
-4. **Generate comprehensive reports** - Final summary with detailed findings
-
-The LLM will:
-
-- Execute the complete checklist validation
-- Present a final report with pass/fail rates and key findings
-- Offer to provide detailed analysis of any section, especially those with warnings or failures

bmad-core/tasks/update-workflow-plan.md

@@ -0,0 +1,248 @@
+# Update Workflow Plan Task
+
+## Purpose
+
+Update the status of steps in an active workflow plan, mark completions, add notes about deviations, and maintain an accurate record of workflow progress. This task can be called directly by users or automatically by other tasks upon completion.
+
+## Task Instructions
+
+### 0. Load Plan Configuration
+
+[[LLM: First load core-config.yml to get plan settings]]
+
+Check workflow configuration:
+
+- `workflow.planFile` - Location of the plan (default: docs/workflow-plan.md)
+- `workflow.trackProgress` - Whether tracking is enabled
+- `workflow.updateOnCompletion` - Whether to auto-update on task completion
+
+If tracking is disabled, inform user and exit.
+
+### 1. Verify Plan Exists
+
+[[LLM: Check if workflow plan exists at configured location]]
+
+If no plan exists:
+
+```
+No active workflow plan found at {location}.
+Would you like to create one? Use *plan command.
+```
+
+### 2. Determine Update Type
+
+[[LLM: Ask user what type of update they want to make]]
+
+Present options:
+
+```
+What would you like to update in the workflow plan?
+
+1. Mark step as complete
+2. Update current step
+3. Add deviation note
+4. Mark decision point resolution
+5. Update overall status
+6. View current plan status only
+
+Please select an option (1-6):
+```
+
+### 3. Parse Current Plan
+
+[[LLM: Read and parse the plan to understand current state]]
+
+Extract:
+
+- All steps with their checkbox status
+- Step IDs from comments (if present)
+- Current completion percentage
+- Any existing deviation notes
+- Decision points and their status
+
+### 4. Execute Updates
+
+#### 4.1 Mark Step Complete
+
+If user selected option 1:
+
+1. Show numbered list of incomplete steps
+2. Ask which step to mark complete
+3. Update the checkbox from `[ ]` to `[x]`
+4. Add completion timestamp: `<!-- completed: YYYY-MM-DD HH:MM -->`
+5. If this was the current step, identify next step
+
+#### 4.2 Update Current Step
+
+If user selected option 2:
+
+1. Show all steps with current status
+2. Ask which step is now current
+3. Add/move `<!-- current-step -->` marker
+4. Optionally add note about why sequence changed
+
+#### 4.3 Add Deviation Note
+
+If user selected option 3:
+
+1. Ask for deviation description
+2. Ask which step this relates to (or general)
+3. Insert note in appropriate location:
+
+```markdown
+> **Deviation Note** (YYYY-MM-DD): {user_note}
+> Related to: Step X.Y or General workflow
+```
+
+#### 4.4 Mark Decision Resolution
+
+If user selected option 4:
+
+1. Show pending decision points
+2. Ask which decision was made
+3. Record the decision and chosen path
+4. Update related steps based on decision
+
+#### 4.5 Update Overall Status
+
+If user selected option 5:
+
+1. Show current overall status
+2. Provide options:
+   - Active (continuing with plan)
+   - Paused (temporarily stopped)
+   - Abandoned (no longer following)
+   - Complete (all steps done)
+3. Update plan header with new status
+
+### 5. Automatic Updates (When Called by Tasks)
+
+[[LLM: When called automatically by another task]]
+
+If called with parameters:
+
+```
+task: {task_name}
+step_id: {step_identifier}
+status: complete|skipped|failed
+note: {optional_note}
+```
+
+Automatically:
+
+1. Find the corresponding step
+2. Update its status
+3. Add completion metadata
+4. Add note if provided
+5. Calculate new progress percentage
+
+### 6. Generate Update Summary
+
+After updates, show summary:
+
+```
+✅ Workflow Plan Updated
+
+Changes made:
+- {change_1}
+- {change_2}
+
+New Status:
+- Progress: {X}% complete ({completed}/{total} steps)
+- Current Step: {current_step}
+- Next Recommended: {next_step}
+
+Plan location: {file_path}
+```
+
+### 7. Integration with Other Tasks
+
+[[LLM: How other tasks should call this]]
+
+Other tasks can integrate by:
+
+1. **After Task Completion**:
+
+```
+At end of task execution:
+- Check if task corresponds to a plan step
+- If yes, call update-workflow-plan with:
+  - task: {current_task_name}
+  - step_id: {matching_step}
+  - status: complete
+```
+
+2. **On Task Failure**:
+
+```
+If task fails:
+- Call update-workflow-plan with:
+  - task: {current_task_name}
+  - status: failed
+  - note: {failure_reason}
+```
+
+### 8. Plan Status Display
+
+[[LLM: When user selects view status only]]
+
+Display comprehensive status:
+
+```markdown
+📋 Workflow Plan Status
+━━━━━━━━━━━━━━━━━━━━
+Workflow: {workflow_name}
+Status: {Active|Paused|Complete}
+Progress: {X}% complete ({completed}/{total} steps)
+Last Updated: {timestamp}
+
+✅ Completed Steps:
+- [x] Step 1.1: {description} (completed: {date})
+- [x] Step 1.2: {description} (completed: {date})
+
+🔄 Current Step:
+- [ ] Step 2.1: {description} <!-- current-step -->
+  Agent: {agent_name}
+  Task: {task_name}
+
+📌 Upcoming Steps:
+- [ ] Step 2.2: {description}
+- [ ] Step 3.1: {description}
+
+⚠️ Deviations/Notes:
+{any_deviation_notes}
+
+📊 Decision Points:
+- Decision 1: {status} - {choice_made}
+- Decision 2: Pending
+
+💡 Next Action:
+Based on the plan, you should {recommended_action}
+```
+
+## Success Criteria
+
+The update is successful when:
+
+1. Plan accurately reflects current workflow state
+2. All updates are clearly timestamped
+3. Deviations are documented with reasons
+4. Progress calculation is correct
+5. Next steps are clear to user
+6. Plan remains readable and well-formatted
+
+## Error Handling
+
+- **Plan file not found**: Offer to create new plan
+- **Malformed plan**: Attempt basic updates, warn user
+- **Write permission error**: Show changes that would be made
+- **Step not found**: Show available steps, ask for clarification
+- **Concurrent updates**: Implement simple locking or warn about conflicts
+
+## Notes
+
+- Always preserve plan history (don't delete old information)
+- Keep updates atomic to prevent corruption
+- Consider creating backup before major updates
+- Updates should enhance, not complicate, the workflow experience
+- If plan becomes too cluttered, suggest creating fresh plan for next phase

bmad-core/templates/brownfield-prd-tmpl.md

@@ -22,34 +22,45 @@ Do not proceed with any recommendations until the user has validated your unders
 
 ### Existing Project Overview
 
-[[LLM: If working in IDE with project loaded, analyze the project structure and existing documentation. If working in web interface, request project upload or detailed project information from user.]]
+[[LLM: Check if document-project analysis was already performed. If yes, reference that output instead of re-analyzing.]]
 
-**Project Location**: [[LLM: Note if this is IDE-based analysis or user-provided information]]
+**Analysis Source**: [[LLM: Indicate one of the following:
+- Document-project output available at: {{path}}
+- IDE-based fresh analysis
+- User-provided information
+]]
 
-**Current Project State**: [[LLM: Brief description of what the project currently does and its primary purpose]]
+**Current Project State**: [[LLM: 
+- If document-project output exists: Extract summary from "High Level Architecture" and "Technical Summary" sections
+- Otherwise: Brief description of what the project currently does and its primary purpose
+]]
 
 ### Available Documentation Analysis
 
-[[LLM: Check for existing documentation in docs folder or provided by user. List what documentation is available and assess its completeness. Required documents include:
+[[LLM: 
+If document-project was run:
+- Note: "Document-project analysis available - using existing technical documentation"
+- List key documents created by document-project
+- Skip the missing documentation check below
 
-- Tech stack documentation
-- Source tree/architecture overview
-- Coding standards
-- API documentation or OpenAPI specs
-- External API integrations
-- UX/UI guidelines or existing patterns]]
+Otherwise, check for existing documentation:
+]]
 
 **Available Documentation**:
 
-- [ ] Tech Stack Documentation
-- [ ] Source Tree/Architecture
-- [ ] Coding Standards
-- [ ] API Documentation
-- [ ] External API Documentation
-- [ ] UX/UI Guidelines
+- [ ] Tech Stack Documentation [[LLM: If from document-project, check ✓]]
+- [ ] Source Tree/Architecture [[LLM: If from document-project, check ✓]]
+- [ ] Coding Standards [[LLM: If from document-project, may be partial]]
+- [ ] API Documentation [[LLM: If from document-project, check ✓]]
+- [ ] External API Documentation [[LLM: If from document-project, check ✓]]
+- [ ] UX/UI Guidelines [[LLM: May not be in document-project]]
+- [ ] Technical Debt Documentation [[LLM: If from document-project, check ✓]]
 - [ ] Other: \***\*\_\_\_\*\***
 
-[[LLM: If critical documentation is missing, STOP and recommend: "I recommend running the document-project task first to generate baseline documentation including tech-stack, source-tree, coding-standards, APIs, external-APIs, and UX/UI information. This will provide the foundation needed for a comprehensive brownfield PRD."]]
+[[LLM: 
+- If document-project was already run: "Using existing project analysis from document-project output."
+- If critical documentation is missing and no document-project: "I recommend running the document-project task first..."
+]]
 
 ### Enhancement Scope Definition
 
@@ -139,13 +150,19 @@ Do not proceed with any recommendations until the user has validated your unders
 
 ### Existing Technology Stack
 
-[[LLM: Document the current technology stack that must be maintained or integrated with]]
+[[LLM: 
+If document-project output available:
+- Extract from "Actual Tech Stack" table in High Level Architecture section
+- Include version numbers and any noted constraints
 
-**Languages**: [[LLM: Current programming languages in use]]
-**Frameworks**: [[LLM: Current frameworks and their versions]]
-**Database**: [[LLM: Current database technology and schema considerations]]
-**Infrastructure**: [[LLM: Current deployment and hosting infrastructure]]
-**External Dependencies**: [[LLM: Current third-party services and APIs]]
+Otherwise, document the current technology stack:
+]]
+
+**Languages**: [[LLM: From document-project or fresh analysis]]
+**Frameworks**: [[LLM: From document-project or fresh analysis]]
+**Database**: [[LLM: From document-project or fresh analysis]]
+**Infrastructure**: [[LLM: From document-project or fresh analysis]]
+**External Dependencies**: [[LLM: From document-project "External Services" section or fresh analysis]]
 
 ### Integration Approach
 
@@ -176,12 +193,19 @@ Do not proceed with any recommendations until the user has validated your unders
 
 ### Risk Assessment and Mitigation
 
-[[LLM: Identify risks specific to working with existing codebase]]
+[[LLM: 
+If document-project output available:
+- Reference "Technical Debt and Known Issues" section
+- Include "Workarounds and Gotchas" that might impact enhancement
+- Note any identified constraints from "Critical Technical Debt"
 
-**Technical Risks**: [[LLM: Risks related to modifying existing code]]
-**Integration Risks**: [[LLM: Risks in integrating with existing systems]]
-**Deployment Risks**: [[LLM: Risks in deploying alongside existing features]]
-**Mitigation Strategies**: [[LLM: Specific strategies to address identified risks]]
+Build risk assessment incorporating existing known issues:
+]]
+
+**Technical Risks**: [[LLM: Include risks from document-project + new enhancement risks]]
+**Integration Risks**: [[LLM: Reference integration constraints from document-project]]
+**Deployment Risks**: [[LLM: Include deployment gotchas from document-project]]
+**Mitigation Strategies**: [[LLM: Address both existing and new risks]]
 
 ## Epic and Story Structure
 

bmad-core/utils/file-resolution-context.md

@@ -1,10 +0,0 @@
-# File Resolution Context
-
-Update the installer/upgrader so that when agents are added to a project (under Add these two lines to any agent's `activation-instructions` for ide installation:
-
-```yaml
-- IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
-- REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
-```
-
-and add `root: .bmad-core` as the first root yml property.

bmad-core/utils/plan-management.md

@@ -0,0 +1,223 @@
+# Plan Management Utility
+
+## Purpose
+
+Provides utilities for agents and tasks to interact with workflow plans, check progress, update status, and ensure workflow steps are executed in the appropriate sequence.
+
+## Core Functions
+
+### 1. Check Plan Existence
+
+[[LLM: When any agent starts or task begins, check if a workflow plan exists]]
+
+```
+Check for workflow plan:
+1. Look for docs/workflow-plan.md (default location)
+2. Check core-config.yml for custom plan location
+3. Return plan status (exists/not exists)
+```
+
+### 2. Parse Plan Status
+
+[[LLM: Extract current progress from the plan document]]
+
+**Plan Parsing Logic:**
+
+1. **Identify Step Structure**:
+   - Look for checkbox lines: `- [ ]` or `- [x]`
+   - Extract step IDs from comments: `<!-- step-id: X.Y -->`
+   - Identify agent assignments: `<!-- agent: pm -->`
+
+2. **Determine Current State**:
+   - Last completed step (highest numbered `[x]`)
+   - Next expected step (first `[ ]` after completed steps)
+   - Overall progress percentage
+
+3. **Extract Metadata**:
+   - Workflow type from plan header
+   - Decision points and their status
+   - Any deviation notes
+
+### 3. Sequence Validation
+
+[[LLM: Check if requested action aligns with plan sequence]]
+
+**Validation Rules:**
+
+1. **Strict Mode** (enforceSequence: true):
+   - Must complete steps in exact order
+   - Warn and block if out of sequence
+   - Require explicit override justification
+
+2. **Flexible Mode** (enforceSequence: false):
+   - Warn about sequence deviation
+   - Allow with confirmation
+   - Log deviation reason
+
+**Warning Templates:**
+
+```
+SEQUENCE WARNING: 
+The workflow plan shows you should complete "{expected_step}" next.
+You're attempting to: "{requested_action}"
+
+In strict mode: Block and require plan update
+In flexible mode: Allow with confirmation
+```
+
+### 4. Plan Update Operations
+
+[[LLM: Provide consistent way to update plan progress]]
+
+**Update Actions:**
+
+1. **Mark Step Complete**:
+   - Change `- [ ]` to `- [x]`
+   - Add completion timestamp comment
+   - Update any status metadata
+
+2. **Add Deviation Note**:
+   - Insert note explaining why sequence changed
+   - Reference the deviation in plan
+
+3. **Update Current Step Pointer**:
+   - Add/move `<!-- current-step -->` marker
+   - Update last-modified timestamp
+
+### 5. Integration Instructions
+
+[[LLM: How agents and tasks should use this utility]]
+
+**For Agents (startup sequence)**:
+
+```
+1. Check if plan exists using this utility
+2. If exists:
+   - Parse current status
+   - Show user: "Active workflow plan detected. Current step: {X}"
+   - Suggest: "Next recommended action: {next_step}"
+3. Continue with normal startup
+```
+
+**For Tasks (pre-execution)**:
+
+```
+1. Check if plan exists
+2. If exists:
+   - Verify this task aligns with plan
+   - If not aligned:
+     - In strict mode: Show warning and stop
+     - In flexible mode: Show warning and ask for confirmation
+3. After task completion:
+   - Update plan if task was a planned step
+   - Add note if task was unplanned
+```
+
+### 6. Plan Status Report Format
+
+[[LLM: Standard format for showing plan status]]
+
+```
+📋 Workflow Plan Status
+━━━━━━━━━━━━━━━━━━━━
+Workflow: {workflow_name}
+Progress: {X}% complete ({completed}/{total} steps)
+
+✅ Completed:
+- {completed_step_1}
+- {completed_step_2}
+
+🔄 Current Step:
+- {current_step_description}
+
+📌 Upcoming:
+- {next_step_1}
+- {next_step_2}
+
+⚠️ Notes:
+- {any_deviations_or_notes}
+```
+
+### 7. Decision Point Handling
+
+[[LLM: Special handling for workflow decision points]]
+
+When encountering a decision point in the plan:
+
+1. **Identify Decision Marker**: `<!-- decision: {decision_id} -->`
+2. **Check Decision Status**: Made/Pending
+3. **If Pending**: 
+   - Block progress until decision made
+   - Show options to user
+   - Record decision when made
+4. **If Made**: 
+   - Verify current path aligns with decision
+   - Warn if attempting alternate path
+
+### 8. Plan Abandonment
+
+[[LLM: Graceful handling when user wants to stop following plan]]
+
+If user wants to abandon plan:
+
+1. Confirm abandonment intent
+2. Add abandonment note to plan
+3. Mark plan as "Abandoned" in header
+4. Stop plan checking for remainder of session
+5. Suggest creating new plan if needed
+
+## Usage Examples
+
+### Example 1: Agent Startup Check
+
+```
+BMad Master starting...
+
+[Check for plan]
+Found active workflow plan: brownfield-fullstack
+Progress: 40% complete (4/10 steps)
+Current step: Create PRD (pm agent)
+
+Suggestion: Based on your plan, you should work with the PM agent next.
+Use *agent pm to switch, or *plan-status to see full progress.
+```
+
+### Example 2: Task Sequence Warning
+
+```
+User: *task create-next-story
+
+[Plan check triggered]
+⚠️ SEQUENCE WARNING: 
+Your workflow plan indicates the PRD hasn't been created yet.
+Creating stories before the PRD may lead to incomplete requirements.
+
+Would you like to:
+1. Continue anyway (will note deviation in plan)
+2. Switch to creating PRD first (*agent pm)
+3. View plan status (*plan-status)
+```
+
+### Example 3: Automatic Plan Update
+
+```
+[After completing create-doc task for PRD]
+
+✅ Plan Updated: Marked "Create PRD" as complete
+📍 Next step: Create Architecture Document (architect agent)
+```
+
+## Implementation Notes
+
+- This utility should be lightweight and fast
+- Plan parsing should be resilient to format variations
+- Always preserve user agency - warnings not blocks (unless strict mode)
+- Plan updates should be atomic to prevent corruption
+- Consider plan versioning for rollback capability
+
+## Error Handling
+
+- Missing plan: Return null, don't error
+- Malformed plan: Warn but continue, treat as no plan
+- Update failures: Log but don't block task completion
+- Parse errors: Fallback to basic text search

bmad-core/utils/workflow-management.md

@@ -1,223 +0,0 @@
-# Workflow Management
-
-This utility enables the BMAD orchestrator to manage and execute team workflows.
-
-## Important: Dynamic Workflow Loading
-
-The BMAD orchestrator MUST read the available workflows from the current team configuration's `workflows` field. Do not use hardcoded workflow lists. Each team bundle defines its own set of supported workflows based on the agents it includes.
-
-**Critical Distinction**:
-
-- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
-- Use `/agent-list` to show agents in the current bundle
-- Use `/workflows` to show workflows in the current bundle, NOT any creation tasks
-
-### Workflow Descriptions
-
-When displaying workflows, use these descriptions based on the workflow ID:
-
-- **greenfield-fullstack**: Build a new full-stack application from concept to development
-- **brownfield-fullstack**: Enhance an existing full-stack application with new features
-- **greenfield-service**: Build a new backend service or API from concept to development
-- **brownfield-service**: Enhance an existing backend service or API
-- **greenfield-ui**: Build a new frontend/UI application from concept to development
-- **brownfield-ui**: Enhance an existing frontend/UI application
-
-## Workflow Commands
-
-### /workflows
-
-Lists all available workflows for the current team. The available workflows are determined by the team configuration and may include workflows such as:
-
-- greenfield-fullstack
-- brownfield-fullstack
-- greenfield-service
-- brownfield-service
-- greenfield-ui
-- brownfield-ui
-
-The actual list depends on which team bundle is loaded. When responding to this command, display the workflows that are configured in the current team's `workflows` field.
-
-Example response format:
-
-```text
-Available workflows for [Team Name]:
-1. [workflow-id] - [Brief description based on workflow type]
-2. [workflow-id] - [Brief description based on workflow type]
-[... etc. ...]
-
-Use /workflow-start {number or id} to begin a workflow.
-```
-
-### /workflow-start {workflow-id}
-
-Starts a specific workflow and transitions to the first agent.
-
-Example: `/workflow-start greenfield-fullstack`
-
-### /workflow-status
-
-Shows current workflow progress, completed artifacts, and next steps.
-
-Example response:
-
-```text
-Current Workflow: Greenfield Full-Stack Development
-Stage: Product Planning (2 of 6)
-Completed:
-  ✓ Discovery & Requirements
-    - project-brief (completed by Mary)
-
-In Progress:
-  ⚡ Product Planning
-    - Create PRD (John) - awaiting input
-
-Next: Technical Architecture
-```
-
-### /workflow-resume
-
-Resumes a workflow from where it left off, useful when starting a new chat.
-
-User can provide completed artifacts:
-
-```text
-User: /workflow-resume greenfield-fullstack
-      I have completed: project-brief, PRD
-BMad: I see you've completed Discovery and part of Product Planning.
-      Based on the greenfield-fullstack workflow, the next step is:
-      - UX Strategy with Sally (ux-expert)
-
-      Would you like me to load Sally to continue?
-```
-
-### /workflow-next
-
-Shows the next recommended agent and action in the current workflow.
-
-## Workflow Execution Flow
-
-### 1. Starting a Workflow
-
-When a workflow is started:
-
-1. Load the workflow definition
-2. Identify the first stage and step
-3. Transition to the required agent
-4. Provide context about expected inputs/outputs
-5. Guide artifact creation
-
-### 2. Stage Transitions
-
-After each artifact is completed:
-
-1. Mark the step as complete
-2. Check transition conditions
-3. If stage is complete, move to next stage
-4. Load the appropriate agent
-5. Pass relevant artifacts as context
-
-### 3. Artifact Tracking
-
-Track all created artifacts:
-
-```yaml
-workflow_state:
-  current_workflow: greenfield-fullstack
-  current_stage: planning
-  current_step: 2
-  artifacts:
-    project-brief:
-      status: completed
-      created_by: analyst
-      timestamp: 2024-01-15T10:30:00.000Z
-    prd:
-      status: in-progress
-      created_by: pm
-      started: 2024-01-15T11:00:00.000Z
-```
-
-### 4. Workflow Interruption Handling
-
-When user returns after interruption:
-
-1. Ask if continuing previous workflow
-2. Request any completed artifacts
-3. Analyze provided artifacts
-4. Determine workflow position
-5. Suggest next appropriate step
-
-Example:
-
-```text
-User: I'm working on a new app. Here's my PRD and architecture doc.
-BMad: I see you have a PRD and architecture document. Based on these artifacts,
-      it looks like you're following the greenfield-fullstack workflow and have completed
-      stages 1-3. The next recommended step would be:
-
-      Stage 4: Validation & Refinement
-      - Load Sarah (Product Owner) to validate all artifacts
-
-      Would you like to continue with this workflow?
-```
-
-## Workflow Context Passing
-
-When transitioning between agents, pass:
-
-1. Previous artifacts created
-2. Current workflow stage
-3. Expected outputs
-4. Any decisions or constraints identified
-
-Example transition:
-
-```text
-BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
-      the next step is UX Strategy with Sally.
-
-      /ux-expert
-
-Sally: I see we're in the Product Planning stage of the greenfield-fullstack workflow.
-       I have access to:
-       - Project Brief from Mary
-       - PRD from John
-
-       Let's create the UX strategy and UI specifications. First, let me review
-       the PRD to understand the features we're designing for...
-```
-
-## Multi-Path Workflows
-
-Some workflows may have multiple paths:
-
-```yaml
-conditional_paths:
-  - condition: project_type == 'mobile'
-    next_stage: mobile-specific-design
-  - condition: project_type == 'web'
-    next_stage: web-architecture
-  - default: fullstack-architecture
-```
-
-Handle these by asking clarifying questions when needed.
-
-## Workflow Best Practices
-
-1. **Always show progress** - Users should know where they are
-2. **Explain transitions** - Why moving to next agent
-3. **Preserve context** - Pass relevant information forward
-4. **Allow flexibility** - Users can skip or modify steps
-5. **Track everything** - Maintain complete workflow state
-
-## Integration with Agents
-
-Each agent should be workflow-aware:
-
-- Know which workflow is active
-- Understand their role in the workflow
-- Access previous artifacts
-- Know expected outputs
-- Guide toward workflow goals
-
-This creates a seamless experience where the entire team works together toward the workflow's objectives.

bmad-core/workflows/brownfield-fullstack.yml

@@ -12,88 +12,243 @@ workflow:
     - integration-enhancement
 
   sequence:
+    - step: enhancement_classification
+      agent: analyst
+      action: classify enhancement scope
+      notes: |
+        Determine enhancement complexity to route to appropriate path:
+        - Single story (< 4 hours) → Use brownfield-create-story task
+        - Small feature (1-3 stories) → Use brownfield-create-epic task  
+        - Major enhancement (multiple epics) → Continue with full workflow
+        
+        Ask user: "Can you describe the enhancement scope? Is this a small fix, a feature addition, or a major enhancement requiring architectural changes?"
+
+    - step: routing_decision
+      condition: based_on_classification
+      routes:
+        single_story:
+          agent: pm
+          uses: brownfield-create-story
+          notes: "Create single story for immediate implementation. Exit workflow after story creation."
+        small_feature:
+          agent: pm
+          uses: brownfield-create-epic
+          notes: "Create focused epic with 1-3 stories. Exit workflow after epic creation."
+        major_enhancement:
+          continue: to_next_step
+          notes: "Continue with comprehensive planning workflow below."
+
+    - step: documentation_check
+      agent: analyst
+      action: check existing documentation
+      condition: major_enhancement_path
+      notes: |
+        Check if adequate project documentation exists:
+        - Look for existing architecture docs, API specs, coding standards
+        - Assess if documentation is current and comprehensive
+        - If adequate: Skip document-project, proceed to PRD
+        - If inadequate: Run document-project first
+
     - step: project_analysis
       agent: architect
       action: analyze existing project and use task document-project
-      creates: multiple documents per the document-project template
-      notes: "Review existing documentation, codebase structure, and identify integration points. Document current system understanding before proceeding."
+      creates: brownfield-architecture.md (or multiple documents)
+      condition: documentation_inadequate
+      notes: "Run document-project to capture current system state, technical debt, and constraints. Pass findings to PRD creation."
 
     - agent: pm
-      creates: brownfield-prd.md
+      creates: prd.md
       uses: brownfield-prd-tmpl
-      requires: existing_project_analysis
-      notes: "Creates comprehensive brownfield PRD with existing system analysis and enhancement planning. SAVE OUTPUT: Copy final brownfield-prd.md to your project's docs/ folder."
+      requires: existing_documentation_or_analysis
+      notes: |
+        Creates PRD for major enhancement. If document-project was run, reference its output to avoid re-analysis.
+        If skipped, use existing project documentation.
+        SAVE OUTPUT: Copy final prd.md to your project's docs/ folder.
+
+    - step: architecture_decision
+      agent: pm/architect
+      action: determine if architecture document needed
+      condition: after_prd_creation
+      notes: |
+        Review PRD to determine if architectural planning is needed:
+        - New architectural patterns → Create architecture doc
+        - New libraries/frameworks → Create architecture doc
+        - Platform/infrastructure changes → Create architecture doc
+        - Following existing patterns → Skip to story creation
 
     - agent: architect
-      creates: brownfield-architecture.md
+      creates: architecture.md
       uses: brownfield-architecture-tmpl
-      requires: brownfield-prd.md
-      notes: "Creates brownfield architecture with integration strategy and existing system constraints. SAVE OUTPUT: Copy final brownfield-architecture.md to your project's docs/ folder."
+      requires: prd.md
+      condition: architecture_changes_needed
+      notes: "Creates architecture ONLY for significant architectural changes. SAVE OUTPUT: Copy final architecture.md to your project's docs/ folder."
 
     - agent: po
       validates: all_artifacts
       uses: po-master-checklist
-      notes: "Validates all brownfield documents for integration safety and completeness. May require updates to any document."
+      notes: "Validates all documents for integration safety and completeness. May require updates to any document."
 
     - agent: various
       updates: any_flagged_documents
       condition: po_checklist_issues
       notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
 
-    - workflow_end:
-      action: move_to_ide
+    - agent: po
+      action: shard_documents
+      creates: sharded_docs
+      requires: all_artifacts_in_project
       notes: |
-        Planning phase complete! Now transition to IDE Development:
-        
-        1. ENSURE DOCUMENTS ARE IN PROJECT:
-           - Copy final prd.md to project's docs/prd.md
-           - Copy final architecture.md to project's docs/architecture.md
-           - All documents must be in the project before proceeding
-        
-        2. SHARD DOCUMENTS (in IDE):
-           - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-           - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-           - This creates docs/prd/ and docs/architecture/ folders with sharded content
-        
-        3. START DEVELOPMENT CYCLE:
-           a. SM Agent (New Chat): @sm → *create
-              - Creates next story from sharded docs
-              - Review and approve story (Draft → Approved)
-           
-           b. Dev Agent (New Chat): @dev
-              - Implements approved story
-              - Updates File List with all changes
-              - Marks story as "Review" when complete
-           
-           c. QA Agent (New Chat): @qa → review-story
-              - Senior dev review with refactoring ability
-              - Fixes small issues directly
-              - Leaves checklist for remaining items
-              - Updates story status (Review → Done or stays Review)
-           
-           d. If QA left unchecked items:
-              - Dev Agent (New Chat): Address remaining items
-              - Return to QA for final approval
-        
-        4. REPEAT: Continue cycle for all epic stories
+        Shard documents for IDE development:
+        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
+        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
+        - Creates docs/prd/ and docs/architecture/ folders with sharded content
+
+    - agent: sm
+      action: create_story
+      creates: story.md
+      requires: sharded_docs_or_brownfield_docs
+      repeats: for_each_epic_or_enhancement
+      notes: |
+        Story creation cycle:
+        - For sharded PRD: @sm → *create (uses create-next-story)
+        - For brownfield docs: @sm → use create-brownfield-story task
+        - Creates story from available documentation
+        - Story starts in "Draft" status
+        - May require additional context gathering for brownfield
+
+    - agent: analyst/pm
+      action: review_draft_story
+      updates: story.md
+      requires: story.md
+      optional: true
+      condition: user_wants_story_review
+      notes: |
+        OPTIONAL: Review and approve draft story
+        - NOTE: story-review task coming soon
+        - Review story completeness and alignment
+        - Update story status: Draft → Approved
+
+    - agent: dev
+      action: implement_story
+      creates: implementation_files
+      requires: story.md
+      notes: |
+        Dev Agent (New Chat): @dev
+        - Implements approved story
+        - Updates File List with all changes
+        - Marks story as "Review" when complete
+
+    - agent: qa
+      action: review_implementation
+      updates: implementation_files
+      requires: implementation_files
+      optional: true
+      notes: |
+        OPTIONAL: QA Agent (New Chat): @qa → review-story
+        - Senior dev review with refactoring ability
+        - Fixes small issues directly
+        - Leaves checklist for remaining items
+        - Updates story status (Review → Done or stays Review)
+
+    - agent: dev
+      action: address_qa_feedback
+      updates: implementation_files
+      condition: qa_left_unchecked_items
+      notes: |
+        If QA left unchecked items:
+        - Dev Agent (New Chat): Address remaining items
+        - Return to QA for final approval
+
+    - repeat_development_cycle:
+      action: continue_for_all_stories
+      notes: |
+        Repeat story cycle (SM → Dev → QA) for all epic stories
+        Continue until all stories in PRD are complete
+
+    - agent: po
+      action: epic_retrospective
+      creates: epic-retrospective.md
+      condition: epic_complete
+      optional: true
+      notes: |
+        OPTIONAL: After epic completion
+        - NOTE: epic-retrospective task coming soon
+        - Validate epic was completed correctly
+        - Document learnings and improvements
+
+    - workflow_end:
+      action: project_complete
+      notes: |
+        All stories implemented and reviewed!
+        Project development phase complete.
         
         Reference: data#bmad-kb:IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
     graph TD
-        A[Start: Brownfield Enhancement] --> B[analyst: analyze existing project]
-        B --> C[pm: brownfield-prd.md]
-        C --> D[architect: brownfield-architecture.md]
-        D --> E[po: validate with po-master-checklist]
-        E --> F{PO finds issues?}
-        F -->|Yes| G[Return to relevant agent for fixes]
-        F -->|No| H[Move to IDE Environment]
-        G --> E
+        A[Start: Brownfield Enhancement] --> B[analyst: classify enhancement scope]
+        B --> C{Enhancement Size?}
+        
+        C -->|Single Story| D[pm: brownfield-create-story]
+        C -->|1-3 Stories| E[pm: brownfield-create-epic]
+        C -->|Major Enhancement| F[analyst: check documentation]
+        
+        D --> END1[To Dev Implementation]
+        E --> END2[To Story Creation]
+        
+        F --> G{Docs Adequate?}
+        G -->|No| H[architect: document-project]
+        G -->|Yes| I[pm: brownfield PRD]
+        H --> I
+        
+        I --> J{Architecture Needed?}
+        J -->|Yes| K[architect: architecture.md]
+        J -->|No| L[po: validate artifacts]
+        K --> L
+        
+        L --> M{PO finds issues?}
+        M -->|Yes| N[Fix issues]
+        M -->|No| O[po: shard documents]
+        N --> L
+        
+        O --> P[sm: create story]
+        P --> Q{Story Type?}
+        Q -->|Sharded PRD| R[create-next-story]
+        Q -->|Brownfield Docs| S[create-brownfield-story]
+        
+        R --> T{Review draft?}
+        S --> T
+        T -->|Yes| U[review & approve]
+        T -->|No| V[dev: implement]
+        U --> V
+        
+        V --> W{QA review?}
+        W -->|Yes| X[qa: review]
+        W -->|No| Y{More stories?}
+        X --> Z{Issues?}
+        Z -->|Yes| AA[dev: fix]
+        Z -->|No| Y
+        AA --> X
+        Y -->|Yes| P
+        Y -->|No| AB{Retrospective?}
+        AB -->|Yes| AC[po: retrospective]
+        AB -->|No| AD[Complete]
+        AC --> AD
 
-        style H fill:#90EE90
-        style C fill:#FFE4B5
-        style D fill:#FFE4B5
+        style AD fill:#90EE90
+        style END1 fill:#90EE90
+        style END2 fill:#90EE90
+        style D fill:#87CEEB
+        style E fill:#87CEEB
+        style I fill:#FFE4B5
+        style K fill:#FFE4B5
+        style O fill:#ADD8E6
+        style P fill:#ADD8E6
+        style V fill:#ADD8E6
+        style U fill:#F0E68C
+        style X fill:#F0E68C
+        style AC fill:#F0E68C
     ```
 
   decision_guidance:
@@ -105,8 +260,38 @@ workflow:
       - Multiple team members will work on related changes
 
   handoff_prompts:
-    analyst_to_pm: "Existing project analysis complete. Create comprehensive brownfield PRD with integration strategy."
-    pm_to_architect: "Brownfield PRD ready. Save it as docs/brownfield-prd.md, then create the integration architecture."
-    architect_to_po: "Architecture complete. Save it as docs/brownfield-architecture.md. Please validate all artifacts for integration safety."
-    po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
-    complete: "All brownfield planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
+    classification_complete: |
+      Enhancement classified as: {{enhancement_type}}
+      {{if single_story}}: Proceeding with brownfield-create-story task for immediate implementation.
+      {{if small_feature}}: Creating focused epic with brownfield-create-epic task.
+      {{if major_enhancement}}: Continuing with comprehensive planning workflow.
+    
+    documentation_assessment: |
+      Documentation assessment complete:
+      {{if adequate}}: Existing documentation is sufficient. Proceeding directly to PRD creation.
+      {{if inadequate}}: Running document-project to capture current system state before PRD.
+    
+    document_project_to_pm: |
+      Project analysis complete. Key findings documented in:
+      - {{document_list}}
+      Use these findings to inform PRD creation and avoid re-analyzing the same aspects.
+    
+    pm_to_architect_decision: |
+      PRD complete and saved as docs/prd.md. 
+      Architectural changes identified: {{yes/no}}
+      {{if yes}}: Proceeding to create architecture document for: {{specific_changes}}
+      {{if no}}: No architectural changes needed. Proceeding to validation.
+    
+    architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for integration safety."
+    
+    po_to_sm: |
+      All artifacts validated. 
+      Documentation type available: {{sharded_prd / brownfield_docs}}
+      {{if sharded}}: Use standard create-next-story task.
+      {{if brownfield}}: Use create-brownfield-story task to handle varied documentation formats.
+    
+    sm_story_creation: |
+      Creating story from {{documentation_type}}.
+      {{if missing_context}}: May need to gather additional context from user during story creation.
+    
+    complete: "All planning artifacts validated and development can begin. Stories will be created based on available documentation format."

bmad-core/workflows/brownfield-service.yml

@@ -20,63 +20,113 @@ workflow:
       notes: "Review existing service documentation, codebase, performance metrics, and identify integration dependencies."
 
     - agent: pm
-      creates: brownfield-prd.md
+      creates: prd.md
       uses: brownfield-prd-tmpl
       requires: existing_service_analysis
-      notes: "Creates comprehensive brownfield PRD focused on service enhancement with existing system analysis. SAVE OUTPUT: Copy final brownfield-prd.md to your project's docs/ folder."
+      notes: "Creates comprehensive PRD focused on service enhancement with existing system analysis. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder."
 
     - agent: architect
-      creates: brownfield-architecture.md
+      creates: architecture.md
       uses: brownfield-architecture-tmpl
-      requires: brownfield-prd.md
-      notes: "Creates brownfield architecture with service integration strategy and API evolution planning. SAVE OUTPUT: Copy final brownfield-architecture.md to your project's docs/ folder."
+      requires: prd.md
+      notes: "Creates architecture with service integration strategy and API evolution planning. SAVE OUTPUT: Copy final architecture.md to your project's docs/ folder."
 
     - agent: po
       validates: all_artifacts
       uses: po-master-checklist
-      notes: "Validates all brownfield documents for service integration safety and API compatibility. May require updates to any document."
+      notes: "Validates all documents for service integration safety and API compatibility. May require updates to any document."
 
     - agent: various
       updates: any_flagged_documents
       condition: po_checklist_issues
       notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
 
-    - workflow_end:
-      action: move_to_ide
+    - agent: po
+      action: shard_documents
+      creates: sharded_docs
+      requires: all_artifacts_in_project
       notes: |
-        Planning phase complete! Now transition to IDE Development:
-        
-        1. ENSURE DOCUMENTS ARE IN PROJECT:
-           - Copy final prd.md to project's docs/prd.md
-           - Copy final architecture.md to project's docs/architecture.md
-           - All documents must be in the project before proceeding
-        
-        2. SHARD DOCUMENTS (in IDE):
-           - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-           - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-           - This creates docs/prd/ and docs/architecture/ folders with sharded content
-        
-        3. START DEVELOPMENT CYCLE:
-           a. SM Agent (New Chat): @sm → *create
-              - Creates next story from sharded docs
-              - Review and approve story (Draft → Approved)
-           
-           b. Dev Agent (New Chat): @dev
-              - Implements approved story
-              - Updates File List with all changes
-              - Marks story as "Review" when complete
-           
-           c. QA Agent (New Chat): @qa → review-story
-              - Senior dev review with refactoring ability
-              - Fixes small issues directly
-              - Leaves checklist for remaining items
-              - Updates story status (Review → Done or stays Review)
-           
-           d. If QA left unchecked items:
-              - Dev Agent (New Chat): Address remaining items
-              - Return to QA for final approval
-        
-        4. REPEAT: Continue cycle for all epic stories
+        Shard documents for IDE development:
+        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
+        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
+        - Creates docs/prd/ and docs/architecture/ folders with sharded content
+
+    - agent: sm
+      action: create_story
+      creates: story.md
+      requires: sharded_docs
+      repeats: for_each_epic
+      notes: |
+        Story creation cycle:
+        - SM Agent (New Chat): @sm → *create
+        - Creates next story from sharded docs
+        - Story starts in "Draft" status
+
+    - agent: analyst/pm
+      action: review_draft_story
+      updates: story.md
+      requires: story.md
+      optional: true
+      condition: user_wants_story_review
+      notes: |
+        OPTIONAL: Review and approve draft story
+        - NOTE: story-review task coming soon
+        - Review story completeness and alignment
+        - Update story status: Draft → Approved
+
+    - agent: dev
+      action: implement_story
+      creates: implementation_files
+      requires: story.md
+      notes: |
+        Dev Agent (New Chat): @dev
+        - Implements approved story
+        - Updates File List with all changes
+        - Marks story as "Review" when complete
+
+    - agent: qa
+      action: review_implementation
+      updates: implementation_files
+      requires: implementation_files
+      optional: true
+      notes: |
+        OPTIONAL: QA Agent (New Chat): @qa → review-story
+        - Senior dev review with refactoring ability
+        - Fixes small issues directly
+        - Leaves checklist for remaining items
+        - Updates story status (Review → Done or stays Review)
+
+    - agent: dev
+      action: address_qa_feedback
+      updates: implementation_files
+      condition: qa_left_unchecked_items
+      notes: |
+        If QA left unchecked items:
+        - Dev Agent (New Chat): Address remaining items
+        - Return to QA for final approval
+
+    - repeat_development_cycle:
+      action: continue_for_all_stories
+      notes: |
+        Repeat story cycle (SM → Dev → QA) for all epic stories
+        Continue until all stories in PRD are complete
+
+    - agent: po
+      action: epic_retrospective
+      creates: epic-retrospective.md
+      condition: epic_complete
+      optional: true
+      notes: |
+        OPTIONAL: After epic completion
+        - NOTE: epic-retrospective task coming soon
+        - Validate epic was completed correctly
+        - Document learnings and improvements
+
+    - workflow_end:
+      action: project_complete
+      notes: |
+        All stories implemented and reviewed!
+        Project development phase complete.
         
         Reference: data#bmad-kb:IDE Development Workflow
 
@@ -84,17 +134,41 @@ workflow:
     ```mermaid
     graph TD
         A[Start: Service Enhancement] --> B[analyst: analyze existing service]
-        B --> C[pm: brownfield-prd.md]
-        C --> D[architect: brownfield-architecture.md]
+        B --> C[pm: prd.md]
+        C --> D[architect: architecture.md]
         D --> E[po: validate with po-master-checklist]
         E --> F{PO finds issues?}
         F -->|Yes| G[Return to relevant agent for fixes]
-        F -->|No| H[Move to IDE Environment]
+        F -->|No| H[po: shard documents]
         G --> E
+        
+        H --> I[sm: create story]
+        I --> J{Review draft story?}
+        J -->|Yes| K[analyst/pm: review & approve story]
+        J -->|No| L[dev: implement story]
+        K --> L
+        L --> M{QA review?}
+        M -->|Yes| N[qa: review implementation]
+        M -->|No| O{More stories?}
+        N --> P{QA found issues?}
+        P -->|Yes| Q[dev: address QA feedback]
+        P -->|No| O
+        Q --> N
+        O -->|Yes| I
+        O -->|No| R{Epic retrospective?}
+        R -->|Yes| S[po: epic retrospective]
+        R -->|No| T[Project Complete]
+        S --> T
 
-        style H fill:#90EE90
+        style T fill:#90EE90
+        style H fill:#ADD8E6
+        style I fill:#ADD8E6
+        style L fill:#ADD8E6
         style C fill:#FFE4B5
         style D fill:#FFE4B5
+        style K fill:#F0E68C
+        style N fill:#F0E68C
+        style S fill:#F0E68C
     ```
 
   decision_guidance:
@@ -106,8 +180,8 @@ workflow:
       - Multiple integration points affected
 
   handoff_prompts:
-    analyst_to_pm: "Service analysis complete. Create comprehensive brownfield PRD with service integration strategy."
-    pm_to_architect: "Brownfield PRD ready. Save it as docs/brownfield-prd.md, then create the service architecture."
-    architect_to_po: "Architecture complete. Save it as docs/brownfield-architecture.md. Please validate all artifacts for service integration safety."
+    analyst_to_pm: "Service analysis complete. Create comprehensive PRD with service integration strategy."
+    pm_to_architect: "PRD ready. Save it as docs/prd.md, then create the service architecture."
+    architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for service integration safety."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
-    complete: "All brownfield planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
+    complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."

bmad-core/workflows/brownfield-ui.yml

@@ -19,71 +19,121 @@ workflow:
       notes: "Review existing frontend application, user feedback, analytics data, and identify improvement areas."
 
     - agent: pm
-      creates: brownfield-prd.md
+      creates: prd.md
       uses: brownfield-prd-tmpl
       requires: existing_ui_analysis
-      notes: "Creates comprehensive brownfield PRD focused on UI enhancement with existing system analysis. SAVE OUTPUT: Copy final brownfield-prd.md to your project's docs/ folder."
+      notes: "Creates comprehensive PRD focused on UI enhancement with existing system analysis. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder."
 
     - agent: ux-expert
       creates: front-end-spec.md
       uses: front-end-spec-tmpl
-      requires: brownfield-prd.md
-      notes: "Creates UI/UX specification for brownfield enhancement that integrates with existing design patterns. SAVE OUTPUT: Copy final front-end-spec.md to your project's docs/ folder."
+      requires: prd.md
+      notes: "Creates UI/UX specification that integrates with existing design patterns. SAVE OUTPUT: Copy final front-end-spec.md to your project's docs/ folder."
 
     - agent: architect
-      creates: brownfield-architecture.md
+      creates: architecture.md
       uses: brownfield-architecture-tmpl
       requires:
-        - brownfield-prd.md
+        - prd.md
         - front-end-spec.md
-      notes: "Creates brownfield frontend architecture with component integration strategy and migration planning. SAVE OUTPUT: Copy final brownfield-architecture.md to your project's docs/ folder."
+      notes: "Creates frontend architecture with component integration strategy and migration planning. SAVE OUTPUT: Copy final architecture.md to your project's docs/ folder."
 
     - agent: po
       validates: all_artifacts
       uses: po-master-checklist
-      notes: "Validates all brownfield documents for UI integration safety and design consistency. May require updates to any document."
+      notes: "Validates all documents for UI integration safety and design consistency. May require updates to any document."
 
     - agent: various
       updates: any_flagged_documents
       condition: po_checklist_issues
       notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
 
-    - workflow_end:
-      action: move_to_ide
+    - agent: po
+      action: shard_documents
+      creates: sharded_docs
+      requires: all_artifacts_in_project
       notes: |
-        Planning phase complete! Now transition to IDE Development:
-        
-        1. ENSURE DOCUMENTS ARE IN PROJECT:
-           - Copy final prd.md to project's docs/prd.md
-           - Copy final architecture.md to project's docs/architecture.md
-           - All documents must be in the project before proceeding
-        
-        2. SHARD DOCUMENTS (in IDE):
-           - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-           - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-           - This creates docs/prd/ and docs/architecture/ folders with sharded content
-        
-        3. START DEVELOPMENT CYCLE:
-           a. SM Agent (New Chat): @sm → *create
-              - Creates next story from sharded docs
-              - Review and approve story (Draft → Approved)
-           
-           b. Dev Agent (New Chat): @dev
-              - Implements approved story
-              - Updates File List with all changes
-              - Marks story as "Review" when complete
-           
-           c. QA Agent (New Chat): @qa → review-story
-              - Senior dev review with refactoring ability
-              - Fixes small issues directly
-              - Leaves checklist for remaining items
-              - Updates story status (Review → Done or stays Review)
-           
-           d. If QA left unchecked items:
-              - Dev Agent (New Chat): Address remaining items
-              - Return to QA for final approval
-        
-        4. REPEAT: Continue cycle for all epic stories
+        Shard documents for IDE development:
+        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
+        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
+        - Creates docs/prd/ and docs/architecture/ folders with sharded content
+
+    - agent: sm
+      action: create_story
+      creates: story.md
+      requires: sharded_docs
+      repeats: for_each_epic
+      notes: |
+        Story creation cycle:
+        - SM Agent (New Chat): @sm → *create
+        - Creates next story from sharded docs
+        - Story starts in "Draft" status
+
+    - agent: analyst/pm
+      action: review_draft_story
+      updates: story.md
+      requires: story.md
+      optional: true
+      condition: user_wants_story_review
+      notes: |
+        OPTIONAL: Review and approve draft story
+        - NOTE: story-review task coming soon
+        - Review story completeness and alignment
+        - Update story status: Draft → Approved
+
+    - agent: dev
+      action: implement_story
+      creates: implementation_files
+      requires: story.md
+      notes: |
+        Dev Agent (New Chat): @dev
+        - Implements approved story
+        - Updates File List with all changes
+        - Marks story as "Review" when complete
+
+    - agent: qa
+      action: review_implementation
+      updates: implementation_files
+      requires: implementation_files
+      optional: true
+      notes: |
+        OPTIONAL: QA Agent (New Chat): @qa → review-story
+        - Senior dev review with refactoring ability
+        - Fixes small issues directly
+        - Leaves checklist for remaining items
+        - Updates story status (Review → Done or stays Review)
+
+    - agent: dev
+      action: address_qa_feedback
+      updates: implementation_files
+      condition: qa_left_unchecked_items
+      notes: |
+        If QA left unchecked items:
+        - Dev Agent (New Chat): Address remaining items
+        - Return to QA for final approval
+
+    - repeat_development_cycle:
+      action: continue_for_all_stories
+      notes: |
+        Repeat story cycle (SM → Dev → QA) for all epic stories
+        Continue until all stories in PRD are complete
+
+    - agent: po
+      action: epic_retrospective
+      creates: epic-retrospective.md
+      condition: epic_complete
+      optional: true
+      notes: |
+        OPTIONAL: After epic completion
+        - NOTE: epic-retrospective task coming soon
+        - Validate epic was completed correctly
+        - Document learnings and improvements
+
+    - workflow_end:
+      action: project_complete
+      notes: |
+        All stories implemented and reviewed!
+        Project development phase complete.
         
         Reference: data#bmad-kb:IDE Development Workflow
 
@@ -91,19 +141,43 @@ workflow:
     ```mermaid
     graph TD
         A[Start: UI Enhancement] --> B[analyst: analyze existing UI]
-        B --> C[pm: brownfield-prd.md]
+        B --> C[pm: prd.md]
         C --> D[ux-expert: front-end-spec.md]
-        D --> E[architect: brownfield-architecture.md]
+        D --> E[architect: architecture.md]
         E --> F[po: validate with po-master-checklist]
         F --> G{PO finds issues?}
         G -->|Yes| H[Return to relevant agent for fixes]
-        G -->|No| I[Move to IDE Environment]
+        G -->|No| I[po: shard documents]
         H --> F
+        
+        I --> J[sm: create story]
+        J --> K{Review draft story?}
+        K -->|Yes| L[analyst/pm: review & approve story]
+        K -->|No| M[dev: implement story]
+        L --> M
+        M --> N{QA review?}
+        N -->|Yes| O[qa: review implementation]
+        N -->|No| P{More stories?}
+        O --> Q{QA found issues?}
+        Q -->|Yes| R[dev: address QA feedback]
+        Q -->|No| P
+        R --> O
+        P -->|Yes| J
+        P -->|No| S{Epic retrospective?}
+        S -->|Yes| T[po: epic retrospective]
+        S -->|No| U[Project Complete]
+        T --> U
 
-        style I fill:#90EE90
+        style U fill:#90EE90
+        style I fill:#ADD8E6
+        style J fill:#ADD8E6
+        style M fill:#ADD8E6
         style C fill:#FFE4B5
         style D fill:#FFE4B5
         style E fill:#FFE4B5
+        style L fill:#F0E68C
+        style O fill:#F0E68C
+        style T fill:#F0E68C
     ```
 
   decision_guidance:
@@ -115,9 +189,9 @@ workflow:
       - Multiple team members will work on related changes
 
   handoff_prompts:
-    analyst_to_pm: "UI analysis complete. Create comprehensive brownfield PRD with UI integration strategy."
-    pm_to_ux: "Brownfield PRD ready. Save it as docs/brownfield-prd.md, then create the UI/UX specification."
+    analyst_to_pm: "UI analysis complete. Create comprehensive PRD with UI integration strategy."
+    pm_to_ux: "PRD ready. Save it as docs/prd.md, then create the UI/UX specification."
     ux_to_architect: "UI/UX spec complete. Save it as docs/front-end-spec.md, then create the frontend architecture."
-    architect_to_po: "Architecture complete. Save it as docs/brownfield-architecture.md. Please validate all artifacts for UI integration safety."
+    architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for UI integration safety."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
-    complete: "All brownfield planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
+    complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."

bmad-core/workflows/greenfield-fullstack.yml

@@ -73,42 +73,92 @@ workflow:
       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."
 
-    - workflow_end:
-      action: move_to_ide
+    - agent: po
+      action: shard_documents
+      creates: sharded_docs
+      requires: all_artifacts_in_project
       notes: |
-        Planning phase complete! Now transition to IDE Development:
-        
-        1. ENSURE DOCUMENTS ARE IN PROJECT:
-           - Copy final prd.md to project's docs/prd.md
-           - Copy final architecture.md to project's docs/architecture.md
-           - All documents must be in the project before proceeding
-        
-        2. SHARD DOCUMENTS (in IDE):
-           - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-           - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-           - This creates docs/prd/ and docs/architecture/ folders with sharded content
-        
-        3. START DEVELOPMENT CYCLE:
-           a. SM Agent (New Chat): @sm → *create
-              - Creates next story from sharded docs
-              - Review and approve story (Draft → Approved)
-           
-           b. Dev Agent (New Chat): @dev
-              - Implements approved story
-              - Updates File List with all changes
-              - Marks story as "Review" when complete
-           
-           c. QA Agent (New Chat): @qa → review-story
-              - Senior dev review with refactoring ability
-              - Fixes small issues directly
-              - Leaves checklist for remaining items
-              - Updates story status (Review → Done or stays Review)
-           
-           d. If QA left unchecked items:
-              - Dev Agent (New Chat): Address remaining items
-              - Return to QA for final approval
-        
-        4. REPEAT: Continue cycle for all epic stories
+        Shard documents for IDE development:
+        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
+        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
+        - Creates docs/prd/ and docs/architecture/ folders with sharded content
+
+    - agent: sm
+      action: create_story
+      creates: story.md
+      requires: sharded_docs
+      repeats: for_each_epic
+      notes: |
+        Story creation cycle:
+        - SM Agent (New Chat): @sm → *create
+        - Creates next story from sharded docs
+        - Story starts in "Draft" status
+
+    - agent: analyst/pm
+      action: review_draft_story
+      updates: story.md
+      requires: story.md
+      optional: true
+      condition: user_wants_story_review
+      notes: |
+        OPTIONAL: Review and approve draft story
+        - NOTE: story-review task coming soon
+        - Review story completeness and alignment
+        - Update story status: Draft → Approved
+
+    - agent: dev
+      action: implement_story
+      creates: implementation_files
+      requires: story.md
+      notes: |
+        Dev Agent (New Chat): @dev
+        - Implements approved story
+        - Updates File List with all changes
+        - Marks story as "Review" when complete
+
+    - agent: qa
+      action: review_implementation
+      updates: implementation_files
+      requires: implementation_files
+      optional: true
+      notes: |
+        OPTIONAL: QA Agent (New Chat): @qa → review-story
+        - Senior dev review with refactoring ability
+        - Fixes small issues directly
+        - Leaves checklist for remaining items
+        - Updates story status (Review → Done or stays Review)
+
+    - agent: dev
+      action: address_qa_feedback
+      updates: implementation_files
+      condition: qa_left_unchecked_items
+      notes: |
+        If QA left unchecked items:
+        - Dev Agent (New Chat): Address remaining items
+        - Return to QA for final approval
+
+    - repeat_development_cycle:
+      action: continue_for_all_stories
+      notes: |
+        Repeat story cycle (SM → Dev → QA) for all epic stories
+        Continue until all stories in PRD are complete
+
+    - agent: po
+      action: epic_retrospective
+      creates: epic-retrospective.md
+      condition: epic_complete
+      optional: true
+      notes: |
+        OPTIONAL: After epic completion
+        - NOTE: epic-retrospective task coming soon
+        - Validate epic was completed correctly
+        - Document learnings and improvements
+
+    - workflow_end:
+      action: project_complete
+      notes: |
+        All stories implemented and reviewed!
+        Project development phase complete.
         
         Reference: data#bmad-kb:IDE Development Workflow
 
@@ -129,21 +179,45 @@ workflow:
         G --> H
         H --> I{PO finds issues?}
         I -->|Yes| J[Return to relevant agent for fixes]
-        I -->|No| K[Move to IDE Environment]
+        I -->|No| K[po: shard documents]
         J --> H
+        
+        K --> L[sm: create story]
+        L --> M{Review draft story?}
+        M -->|Yes| N[analyst/pm: review & approve story]
+        M -->|No| O[dev: implement story]
+        N --> O
+        O --> P{QA review?}
+        P -->|Yes| Q[qa: review implementation]
+        P -->|No| R{More stories?}
+        Q --> S{QA found issues?}
+        S -->|Yes| T[dev: address QA feedback]
+        S -->|No| R
+        T --> Q
+        R -->|Yes| L
+        R -->|No| U{Epic retrospective?}
+        U -->|Yes| V[po: epic retrospective]
+        U -->|No| W[Project Complete]
+        V --> W
 
         B -.-> B1[Optional: brainstorming]
         B -.-> B2[Optional: market research]
         D -.-> D1[Optional: user research]
         E -.-> E1[Optional: technical research]
 
-        style K fill:#90EE90
+        style W fill:#90EE90
+        style K fill:#ADD8E6
+        style L fill:#ADD8E6
+        style O fill:#ADD8E6
         style D3 fill:#E6E6FA
         style D4 fill:#E6E6FA
         style B fill:#FFE4B5
         style C fill:#FFE4B5
         style D fill:#FFE4B5
         style E fill:#FFE4B5
+        style N fill:#F0E68C
+        style Q fill:#F0E68C
+        style V fill:#F0E68C
     ```
 
   decision_guidance:

bmad-core/workflows/greenfield-service.yml

@@ -49,42 +49,92 @@ workflow:
       condition: po_checklist_issues
       notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
 
-    - workflow_end:
-      action: move_to_ide
+    - agent: po
+      action: shard_documents
+      creates: sharded_docs
+      requires: all_artifacts_in_project
       notes: |
-        Planning phase complete! Now transition to IDE Development:
-        
-        1. ENSURE DOCUMENTS ARE IN PROJECT:
-           - Copy final prd.md to project's docs/prd.md
-           - Copy final architecture.md to project's docs/architecture.md
-           - All documents must be in the project before proceeding
-        
-        2. SHARD DOCUMENTS (in IDE):
-           - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-           - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-           - This creates docs/prd/ and docs/architecture/ folders with sharded content
-        
-        3. START DEVELOPMENT CYCLE:
-           a. SM Agent (New Chat): @sm → *create
-              - Creates next story from sharded docs
-              - Review and approve story (Draft → Approved)
-           
-           b. Dev Agent (New Chat): @dev
-              - Implements approved story
-              - Updates File List with all changes
-              - Marks story as "Review" when complete
-           
-           c. QA Agent (New Chat): @qa → review-story
-              - Senior dev review with refactoring ability
-              - Fixes small issues directly
-              - Leaves checklist for remaining items
-              - Updates story status (Review → Done or stays Review)
-           
-           d. If QA left unchecked items:
-              - Dev Agent (New Chat): Address remaining items
-              - Return to QA for final approval
-        
-        4. REPEAT: Continue cycle for all epic stories
+        Shard documents for IDE development:
+        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
+        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
+        - Creates docs/prd/ and docs/architecture/ folders with sharded content
+
+    - agent: sm
+      action: create_story
+      creates: story.md
+      requires: sharded_docs
+      repeats: for_each_epic
+      notes: |
+        Story creation cycle:
+        - SM Agent (New Chat): @sm → *create
+        - Creates next story from sharded docs
+        - Story starts in "Draft" status
+
+    - agent: analyst/pm
+      action: review_draft_story
+      updates: story.md
+      requires: story.md
+      optional: true
+      condition: user_wants_story_review
+      notes: |
+        OPTIONAL: Review and approve draft story
+        - NOTE: story-review task coming soon
+        - Review story completeness and alignment
+        - Update story status: Draft → Approved
+
+    - agent: dev
+      action: implement_story
+      creates: implementation_files
+      requires: story.md
+      notes: |
+        Dev Agent (New Chat): @dev
+        - Implements approved story
+        - Updates File List with all changes
+        - Marks story as "Review" when complete
+
+    - agent: qa
+      action: review_implementation
+      updates: implementation_files
+      requires: implementation_files
+      optional: true
+      notes: |
+        OPTIONAL: QA Agent (New Chat): @qa → review-story
+        - Senior dev review with refactoring ability
+        - Fixes small issues directly
+        - Leaves checklist for remaining items
+        - Updates story status (Review → Done or stays Review)
+
+    - agent: dev
+      action: address_qa_feedback
+      updates: implementation_files
+      condition: qa_left_unchecked_items
+      notes: |
+        If QA left unchecked items:
+        - Dev Agent (New Chat): Address remaining items
+        - Return to QA for final approval
+
+    - repeat_development_cycle:
+      action: continue_for_all_stories
+      notes: |
+        Repeat story cycle (SM → Dev → QA) for all epic stories
+        Continue until all stories in PRD are complete
+
+    - agent: po
+      action: epic_retrospective
+      creates: epic-retrospective.md
+      condition: epic_complete
+      optional: true
+      notes: |
+        OPTIONAL: After epic completion
+        - NOTE: epic-retrospective task coming soon
+        - Validate epic was completed correctly
+        - Document learnings and improvements
+
+    - workflow_end:
+      action: project_complete
+      notes: |
+        All stories implemented and reviewed!
+        Service development phase complete.
         
         Reference: data#bmad-kb:IDE Development Workflow
 
@@ -100,17 +150,41 @@ workflow:
         F --> G
         G --> H{PO finds issues?}
         H -->|Yes| I[Return to relevant agent for fixes]
-        H -->|No| J[Move to IDE Environment]
+        H -->|No| J[po: shard documents]
         I --> G
+        
+        J --> K[sm: create story]
+        K --> L{Review draft story?}
+        L -->|Yes| M[analyst/pm: review & approve story]
+        L -->|No| N[dev: implement story]
+        M --> N
+        N --> O{QA review?}
+        O -->|Yes| P[qa: review implementation]
+        O -->|No| Q{More stories?}
+        P --> R{QA found issues?}
+        R -->|Yes| S[dev: address QA feedback]
+        R -->|No| Q
+        S --> P
+        Q -->|Yes| K
+        Q -->|No| T{Epic retrospective?}
+        T -->|Yes| U[po: epic retrospective]
+        T -->|No| V[Project Complete]
+        U --> V
 
         B -.-> B1[Optional: brainstorming]
         B -.-> B2[Optional: market research]
         D -.-> D1[Optional: technical research]
 
-        style J fill:#90EE90
+        style V fill:#90EE90
+        style J fill:#ADD8E6
+        style K fill:#ADD8E6
+        style N fill:#ADD8E6
         style B fill:#FFE4B5
         style C fill:#FFE4B5
         style D fill:#FFE4B5
+        style M fill:#F0E68C
+        style P fill:#F0E68C
+        style U fill:#F0E68C
     ```
 
   decision_guidance:

bmad-core/workflows/greenfield-ui.yml

@@ -68,42 +68,92 @@ workflow:
       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."
 
-    - workflow_end:
-      action: move_to_ide
+    - agent: po
+      action: shard_documents
+      creates: sharded_docs
+      requires: all_artifacts_in_project
       notes: |
-        Planning phase complete! Now transition to IDE Development:
-        
-        1. ENSURE DOCUMENTS ARE IN PROJECT:
-           - Copy final prd.md to project's docs/prd.md
-           - Copy final architecture.md to project's docs/architecture.md
-           - All documents must be in the project before proceeding
-        
-        2. SHARD DOCUMENTS (in IDE):
-           - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-           - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-           - This creates docs/prd/ and docs/architecture/ folders with sharded content
-        
-        3. START DEVELOPMENT CYCLE:
-           a. SM Agent (New Chat): @sm → *create
-              - Creates next story from sharded docs
-              - Review and approve story (Draft → Approved)
-           
-           b. Dev Agent (New Chat): @dev
-              - Implements approved story
-              - Updates File List with all changes
-              - Marks story as "Review" when complete
-           
-           c. QA Agent (New Chat): @qa → review-story
-              - Senior dev review with refactoring ability
-              - Fixes small issues directly
-              - Leaves checklist for remaining items
-              - Updates story status (Review → Done or stays Review)
-           
-           d. If QA left unchecked items:
-              - Dev Agent (New Chat): Address remaining items
-              - Return to QA for final approval
-        
-        4. REPEAT: Continue cycle for all epic stories
+        Shard documents for IDE development:
+        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
+        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
+        - Creates docs/prd/ and docs/architecture/ folders with sharded content
+
+    - agent: sm
+      action: create_story
+      creates: story.md
+      requires: sharded_docs
+      repeats: for_each_epic
+      notes: |
+        Story creation cycle:
+        - SM Agent (New Chat): @sm → *create
+        - Creates next story from sharded docs
+        - Story starts in "Draft" status
+
+    - agent: analyst/pm
+      action: review_draft_story
+      updates: story.md
+      requires: story.md
+      optional: true
+      condition: user_wants_story_review
+      notes: |
+        OPTIONAL: Review and approve draft story
+        - NOTE: story-review task coming soon
+        - Review story completeness and alignment
+        - Update story status: Draft → Approved
+
+    - agent: dev
+      action: implement_story
+      creates: implementation_files
+      requires: story.md
+      notes: |
+        Dev Agent (New Chat): @dev
+        - Implements approved story
+        - Updates File List with all changes
+        - Marks story as "Review" when complete
+
+    - agent: qa
+      action: review_implementation
+      updates: implementation_files
+      requires: implementation_files
+      optional: true
+      notes: |
+        OPTIONAL: QA Agent (New Chat): @qa → review-story
+        - Senior dev review with refactoring ability
+        - Fixes small issues directly
+        - Leaves checklist for remaining items
+        - Updates story status (Review → Done or stays Review)
+
+    - agent: dev
+      action: address_qa_feedback
+      updates: implementation_files
+      condition: qa_left_unchecked_items
+      notes: |
+        If QA left unchecked items:
+        - Dev Agent (New Chat): Address remaining items
+        - Return to QA for final approval
+
+    - repeat_development_cycle:
+      action: continue_for_all_stories
+      notes: |
+        Repeat story cycle (SM → Dev → QA) for all epic stories
+        Continue until all stories in PRD are complete
+
+    - agent: po
+      action: epic_retrospective
+      creates: epic-retrospective.md
+      condition: epic_complete
+      optional: true
+      notes: |
+        OPTIONAL: After epic completion
+        - NOTE: epic-retrospective task coming soon
+        - Validate epic was completed correctly
+        - Document learnings and improvements
+
+    - workflow_end:
+      action: project_complete
+      notes: |
+        All stories implemented and reviewed!
+        Project development phase complete.
         
         Reference: data#bmad-kb:IDE Development Workflow
 
@@ -124,21 +174,45 @@ workflow:
         G --> H
         H --> I{PO finds issues?}
         I -->|Yes| J[Return to relevant agent for fixes]
-        I -->|No| K[Move to IDE Environment]
+        I -->|No| K[po: shard documents]
         J --> H
+        
+        K --> L[sm: create story]
+        L --> M{Review draft story?}
+        M -->|Yes| N[analyst/pm: review & approve story]
+        M -->|No| O[dev: implement story]
+        N --> O
+        O --> P{QA review?}
+        P -->|Yes| Q[qa: review implementation]
+        P -->|No| R{More stories?}
+        Q --> S{QA found issues?}
+        S -->|Yes| T[dev: address QA feedback]
+        S -->|No| R
+        T --> Q
+        R -->|Yes| L
+        R -->|No| U{Epic retrospective?}
+        U -->|Yes| V[po: epic retrospective]
+        U -->|No| W[Project Complete]
+        V --> W
 
         B -.-> B1[Optional: brainstorming]
         B -.-> B2[Optional: market research]
         D -.-> D1[Optional: user research]
         E -.-> E1[Optional: technical research]
 
-        style K fill:#90EE90
+        style W fill:#90EE90
+        style K fill:#ADD8E6
+        style L fill:#ADD8E6
+        style O fill:#ADD8E6
         style D3 fill:#E6E6FA
         style D4 fill:#E6E6FA
         style B fill:#FFE4B5
         style C fill:#FFE4B5
         style D fill:#FFE4B5
         style E fill:#FFE4B5
+        style N fill:#F0E68C
+        style Q fill:#F0E68C
+        style V fill:#F0E68C
     ```
 
   decision_guidance:

common/tasks/create-doc.md

@@ -0,0 +1,91 @@
+# Create Document from Template Task
+
+## Purpose
+
+Generate documents from templates by EXECUTING (not just reading) embedded instructions from the perspective of the selected agent persona.
+
+## CRITICAL RULES
+
+1. **Templates are PROGRAMS** - Execute every [[LLM:]] instruction exactly as written
+2. **NEVER show markup** - Hide all [[LLM:]], {{placeholders}}, @{examples}, and template syntax
+3. **STOP and EXECUTE** - When you see "apply tasks#" or "execute tasks#", STOP and run that task immediately
+4. **WAIT for user input** - At review points and after elicitation tasks
+
+## Execution Flow
+
+### 0. Check Workflow Plan (if configured)
+
+[[LLM: Check if plan tracking is enabled in core-config.yml]]
+
+- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
+- If plan exists and this document creation is part of the plan:
+  - Verify this is the expected next step
+  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
+  - If out of sequence and `enforceSequence: false`, ask for confirmation
+- Continue with normal execution after plan check
+
+### 1. Identify Template
+
+- Load from `templates#*` or `{root}/templates directory`
+- Agent-specific templates are listed in agent's dependencies
+- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
+
+### 2. Ask Interaction Mode
+
+> 1. **Incremental** - Section by section with reviews
+> 2. **YOLO Mode** - Complete draft then review (user can type `/yolo` anytime to switch)
+
+### 3. Execute Template
+
+- Replace {{placeholders}} with real content
+- Execute [[LLM:]] instructions as you encounter them
+- Process <<REPEAT>> loops and ^^CONDITIONS^^
+- Use @{examples} for guidance but never output them
+
+### 4. Key Execution Patterns
+
+**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
+
+- Draft the content
+- Present it to user
+- IMMEDIATELY execute the task
+- Wait for completion before continuing
+
+**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
+
+- Finish the section
+- STOP and execute the task
+- Wait for user input
+
+### 5. Validation & Final Presentation
+
+- Run any specified checklists
+- Present clean, formatted content only
+- No truncation or summarization
+- Begin directly with content (no preamble)
+- Include any handoff prompts from template
+
+### 6. Update Workflow Plan (if applicable)
+
+[[LLM: After successful document creation]]
+
+- If plan tracking is enabled and document was part of plan:
+  - Call update-workflow-plan task to mark step complete
+  - Parameters: task: create-doc, step_id: {from plan}, status: complete
+  - Show next recommended step from plan
+
+## Common Mistakes to Avoid
+
+❌ Skipping elicitation tasks
+❌ Showing template markup to users
+❌ Continuing past STOP signals
+❌ Combining multiple review points
+
+✅ Execute ALL instructions in sequence
+✅ Present only clean, formatted content
+✅ Stop at every elicitation point
+✅ Wait for user confirmation when instructed
+
+## Remember
+
+Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.

common/tasks/execute-checklist.md

@@ -2,13 +2,9 @@
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
 ## Available Checklists
 
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
 
 ## Instructions
 
@@ -17,7 +13,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
+     - Load the appropriate checklist from {root}/checklists/
    - If no checklist specified:
      - Ask the user which checklist they want to use
      - Present the available options from the files in the checklists folder

common/utils/workflow-management.md

@@ -0,0 +1,69 @@
+# Workflow Management
+
+Enables BMAD orchestrator to manage and execute team workflows.
+
+## Dynamic Workflow Loading
+
+Read available workflows from current team configuration's `workflows` field. Each team bundle defines its own supported workflows.
+
+**Key Commands**:
+
+- `/workflows` - List workflows in current bundle or workflows folder
+- `/agent-list` - Show agents in current bundle
+
+## Workflow Commands
+
+### /workflows
+
+Lists available workflows with titles and descriptions.
+
+### /workflow-start {workflow-id}
+
+Starts workflow and transitions to first agent.
+
+### /workflow-status
+
+Shows current progress, completed artifacts, and next steps.
+
+### /workflow-resume
+
+Resumes workflow from last position. User can provide completed artifacts.
+
+### /workflow-next
+
+Shows next recommended agent and action.
+
+## Execution Flow
+
+1. **Starting**: Load definition → Identify first stage → Transition to agent → Guide artifact creation
+
+2. **Stage Transitions**: Mark complete → Check conditions → Load next agent → Pass artifacts
+
+3. **Artifact Tracking**: Track status, creator, timestamps in workflow_state
+
+4. **Interruption Handling**: Analyze provided artifacts → Determine position → Suggest next step
+
+## Context Passing
+
+When transitioning, pass:
+
+- Previous artifacts
+- Current workflow stage
+- Expected outputs
+- Decisions/constraints
+
+## Multi-Path Workflows
+
+Handle conditional paths by asking clarifying questions when needed.
+
+## Best Practices
+
+1. Show progress
+2. Explain transitions
+3. Preserve context
+4. Allow flexibility
+5. Track state
+
+## Agent Integration
+
+Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.

dist/agents/analyst.txt

@@ -652,76 +652,93 @@ Present these numbered options to the user:
 
 ## Purpose
 
-- Generate documents from any specified template following embedded instructions from the perspective of the selected agent persona
+Generate documents from templates by EXECUTING (not just reading) embedded instructions from the perspective of the selected agent persona.
 
-## Instructions
+## CRITICAL RULES
 
-### 1. Identify Template and Context
+1. **Templates are PROGRAMS** - Execute every [[LLM:]] instruction exactly as written
+2. **NEVER show markup** - Hide all [[LLM:]], {{placeholders}}, @{examples}, and template syntax
+3. **STOP and EXECUTE** - When you see "apply tasks#" or "execute tasks#", STOP and run that task immediately
+4. **WAIT for user input** - At review points and after elicitation tasks
 
-- Determine which template to use (user-provided or list available for selection to user)
+## Execution Flow
 
-  - Agent-specific templates are listed in the agent's dependencies under `templates`. For each template listed, consider it a document the agent can create. So if an agent has:
+### 0. Check Workflow Plan (if configured)
 
-    @{example}
-    dependencies:
-    templates: - prd-tmpl - architecture-tmpl
-    @{/example}
+[[LLM: Check if plan tracking is enabled in core-config.yml]]
 
-    You would offer to create "PRD" and "Architecture" documents when the user asks what you can help with.
+- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
+- If plan exists and this document creation is part of the plan:
+  - Verify this is the expected next step
+  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
+  - If out of sequence and `enforceSequence: false`, ask for confirmation
+- Continue with normal execution after plan check
 
-- Gather all relevant inputs, or ask for them, or else rely on user providing necessary details to complete the document
-- Understand the document purpose and target audience
+### 1. Identify Template
 
-### 2. Determine Interaction Mode
+- Load from `templates#*` or `{root}/templates directory`
+- Agent-specific templates are listed in agent's dependencies
+- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
 
-Confirm with the user their preferred interaction style:
+### 2. Ask Interaction Mode
 
-- **Incremental:** Work through chunks of the document.
-- **YOLO Mode:** Draft complete document making reasonable assumptions in one shot. (Can be entered also after starting incremental by just typing /yolo)
+> 1. **Incremental** - Section by section with reviews
+> 2. **YOLO Mode** - Complete draft then review (user can type `/yolo` anytime to switch)
 
 ### 3. Execute Template
 
-- Load specified template from `templates#*` or the /templates directory
-- Follow ALL embedded LLM instructions within the template
-- Process template markup according to `utils#template-format` conventions
-
-### 4. Template Processing Rules
-
-#### CRITICAL: Never display template markup, LLM instructions, or examples to users
-
-- Replace all {{placeholders}} with actual content
-- Execute all [[LLM: instructions]] internally
-- Process `<<REPEAT>>` sections as needed
-- Evaluate ^^CONDITION^^ blocks and include only if applicable
+- Replace {{placeholders}} with real content
+- Execute [[LLM:]] instructions as you encounter them
+- Process <<REPEAT>> loops and ^^CONDITIONS^^
 - Use @{examples} for guidance but never output them
 
-### 5. Content Generation
+### 4. Key Execution Patterns
 
-- **Incremental Mode**: Present each major section for review before proceeding
-- **YOLO Mode**: Generate all sections, then review complete document with user
-- Apply any elicitation protocols specified in template
-- Incorporate user feedback and iterate as needed
+**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
 
-### 6. Validation
+- Draft the content
+- Present it to user
+- IMMEDIATELY execute the task
+- Wait for completion before continuing
 
-If template specifies a checklist:
+**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
 
-- Run the appropriate checklist against completed document
-- Document completion status for each item
-- Address any deficiencies found
-- Present validation summary to user
+- Finish the section
+- STOP and execute the task
+- Wait for user input
 
-### 7. Final Presentation
+### 5. Validation & Final Presentation
 
+- Run any specified checklists
 - Present clean, formatted content only
-- Ensure all sections are complete
-- DO NOT truncate or summarize content
-- Begin directly with document content (no preamble)
-- Include any handoff prompts specified in template
+- No truncation or summarization
+- Begin directly with content (no preamble)
+- Include any handoff prompts from template
 
-## Important Notes
+### 6. Update Workflow Plan (if applicable)
 
-- Template markup is for AI processing only - never expose to users
+[[LLM: After successful document creation]]
+
+- If plan tracking is enabled and document was part of plan:
+  - Call update-workflow-plan task to mark step complete
+  - Parameters: task: create-doc, step_id: {from plan}, status: complete
+  - Show next recommended step from plan
+
+## Common Mistakes to Avoid
+
+❌ Skipping elicitation tasks
+❌ Showing template markup to users
+❌ Continuing past STOP signals
+❌ Combining multiple review points
+
+✅ Execute ALL instructions in sequence
+✅ Present only clean, formatted content
+✅ Stop at every elicitation point
+✅ Wait for user confirmation when instructed
+
+## Remember
+
+Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
 ==================== END: tasks#create-doc ====================
 
 ==================== START: tasks#advanced-elicitation ====================
@@ -2013,7 +2030,7 @@ BMAD transforms you into a "Vibe CEO" - directing a team of specialized AI agent
 5. Type `/help` to see available commands
 
 #### Option 2: IDE Integration
-**Best for**: Cursor, Claude Code, Windsurf, Cline, Roo Code users
+**Best for**: Cursor, Claude Code, Windsurf, Cline, Roo Code, VS Code Copilot users
 
 ```bash
 # Interactive installation (recommended)
@@ -2028,6 +2045,7 @@ npx bmad-method install
   - **Windsurf**: Built-in AI capabilities
   - **Cline**: VS Code extension with AI features
   - **Roo Code**: Web-based IDE with agent support
+  - **VS Code Copilot**: AI-powered coding assistant
 
 **Note for VS Code Users**: BMAD-METHOD assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMAD agents. The installer includes built-in support for Cline and Roo.
 
@@ -2213,6 +2231,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 - **Cursor**: `@agent-name` (e.g., `@bmad-master`)
 - **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
 - **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
+- **VS Code Copilot**: Open the Chat view (`⌃⌘I` on Mac, `Ctrl+Alt+I` on Windows/Linux) and select **Agent** from the chat mode selector.
 
 **Chat Management Guidelines**:
 - **Claude Code, Cursor, Windsurf**: Start new chats when switching agents
@@ -2654,7 +2673,7 @@ Expansion packs extend BMAD-METHOD beyond traditional software development into
 ### Using Expansion Packs
 
 1. **Browse Available Packs**: Check `expansion-packs/` directory
-2. **Get Inspiration**: See `docs/expansion-pack-ideas.md` for detailed examples
+2. **Get Inspiration**: See `docs/expansion-packs.md` for detailed examples and ideas
 3. **Install via CLI**: 
    ```bash
    npx bmad-method install

dist/agents/architect.txt

@@ -107,76 +107,93 @@ dependencies:
 
 ## Purpose
 
-- Generate documents from any specified template following embedded instructions from the perspective of the selected agent persona
+Generate documents from templates by EXECUTING (not just reading) embedded instructions from the perspective of the selected agent persona.
 
-## Instructions
+## CRITICAL RULES
 
-### 1. Identify Template and Context
+1. **Templates are PROGRAMS** - Execute every [[LLM:]] instruction exactly as written
+2. **NEVER show markup** - Hide all [[LLM:]], {{placeholders}}, @{examples}, and template syntax
+3. **STOP and EXECUTE** - When you see "apply tasks#" or "execute tasks#", STOP and run that task immediately
+4. **WAIT for user input** - At review points and after elicitation tasks
 
-- Determine which template to use (user-provided or list available for selection to user)
+## Execution Flow
 
-  - Agent-specific templates are listed in the agent's dependencies under `templates`. For each template listed, consider it a document the agent can create. So if an agent has:
+### 0. Check Workflow Plan (if configured)
 
-    @{example}
-    dependencies:
-    templates: - prd-tmpl - architecture-tmpl
-    @{/example}
+[[LLM: Check if plan tracking is enabled in core-config.yml]]
 
-    You would offer to create "PRD" and "Architecture" documents when the user asks what you can help with.
+- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
+- If plan exists and this document creation is part of the plan:
+  - Verify this is the expected next step
+  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
+  - If out of sequence and `enforceSequence: false`, ask for confirmation
+- Continue with normal execution after plan check
 
-- Gather all relevant inputs, or ask for them, or else rely on user providing necessary details to complete the document
-- Understand the document purpose and target audience
+### 1. Identify Template
 
-### 2. Determine Interaction Mode
+- Load from `templates#*` or `{root}/templates directory`
+- Agent-specific templates are listed in agent's dependencies
+- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
 
-Confirm with the user their preferred interaction style:
+### 2. Ask Interaction Mode
 
-- **Incremental:** Work through chunks of the document.
-- **YOLO Mode:** Draft complete document making reasonable assumptions in one shot. (Can be entered also after starting incremental by just typing /yolo)
+> 1. **Incremental** - Section by section with reviews
+> 2. **YOLO Mode** - Complete draft then review (user can type `/yolo` anytime to switch)
 
 ### 3. Execute Template
 
-- Load specified template from `templates#*` or the /templates directory
-- Follow ALL embedded LLM instructions within the template
-- Process template markup according to `utils#template-format` conventions
-
-### 4. Template Processing Rules
-
-#### CRITICAL: Never display template markup, LLM instructions, or examples to users
-
-- Replace all {{placeholders}} with actual content
-- Execute all [[LLM: instructions]] internally
-- Process `<<REPEAT>>` sections as needed
-- Evaluate ^^CONDITION^^ blocks and include only if applicable
+- Replace {{placeholders}} with real content
+- Execute [[LLM:]] instructions as you encounter them
+- Process <<REPEAT>> loops and ^^CONDITIONS^^
 - Use @{examples} for guidance but never output them
 
-### 5. Content Generation
+### 4. Key Execution Patterns
 
-- **Incremental Mode**: Present each major section for review before proceeding
-- **YOLO Mode**: Generate all sections, then review complete document with user
-- Apply any elicitation protocols specified in template
-- Incorporate user feedback and iterate as needed
+**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
 
-### 6. Validation
+- Draft the content
+- Present it to user
+- IMMEDIATELY execute the task
+- Wait for completion before continuing
 
-If template specifies a checklist:
+**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
 
-- Run the appropriate checklist against completed document
-- Document completion status for each item
-- Address any deficiencies found
-- Present validation summary to user
+- Finish the section
+- STOP and execute the task
+- Wait for user input
 
-### 7. Final Presentation
+### 5. Validation & Final Presentation
 
+- Run any specified checklists
 - Present clean, formatted content only
-- Ensure all sections are complete
-- DO NOT truncate or summarize content
-- Begin directly with document content (no preamble)
-- Include any handoff prompts specified in template
+- No truncation or summarization
+- Begin directly with content (no preamble)
+- Include any handoff prompts from template
 
-## Important Notes
+### 6. Update Workflow Plan (if applicable)
 
-- Template markup is for AI processing only - never expose to users
+[[LLM: After successful document creation]]
+
+- If plan tracking is enabled and document was part of plan:
+  - Call update-workflow-plan task to mark step complete
+  - Parameters: task: create-doc, step_id: {from plan}, status: complete
+  - Show next recommended step from plan
+
+## Common Mistakes to Avoid
+
+❌ Skipping elicitation tasks
+❌ Showing template markup to users
+❌ Continuing past STOP signals
+❌ Combining multiple review points
+
+✅ Execute ALL instructions in sequence
+✅ Present only clean, formatted content
+✅ Stop at every elicitation point
+✅ Wait for user confirmation when instructed
+
+## Remember
+
+Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
 ==================== END: tasks#create-doc ====================
 
 ==================== START: tasks#create-deep-research-prompt ====================
@@ -808,13 +825,9 @@ Apply the advanced elicitation task after major sections to refine based on user
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
 ## Available Checklists
 
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
 
 ## Instructions
 
@@ -823,7 +836,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
+     - Load the appropriate checklist from {root}/checklists/
    - If no checklist specified:
      - Ask the user which checklist they want to use
      - Present the available options from the files in the checklists folder

dist/agents/dev.txt

@@ -83,7 +83,7 @@ task-execution:
   updates-ONLY:
     - 'Checkboxes: [ ] not started | [-] in progress | [x] complete'
     - 'Debug Log: | Task | File | Change | Reverted? |'
-    - 'Completion Notes: Deviations only, <50 words'
+    - 'Completion Notes: Deviations from AC or tasks during execution only, <50 words'
     - 'Change Log: Requirement changes only'
     - 'File List: CRITICAL - Maintain complete list of ALL files created/modified during implementation'
   blocking: Unapproved deps | Ambiguous after story check | 3 failures | Missing config | Failing validations
@@ -102,13 +102,9 @@ dependencies:
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
 ## Available Checklists
 
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
 
 ## Instructions
 
@@ -117,7 +113,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
+     - Load the appropriate checklist from {root}/checklists/
    - If no checklist specified:
      - Ask the user which checklist they want to use
      - Present the available options from the files in the checklists folder

dist/agents/pm.txt

@@ -104,76 +104,93 @@ dependencies:
 
 ## Purpose
 
-- Generate documents from any specified template following embedded instructions from the perspective of the selected agent persona
+Generate documents from templates by EXECUTING (not just reading) embedded instructions from the perspective of the selected agent persona.
 
-## Instructions
+## CRITICAL RULES
 
-### 1. Identify Template and Context
+1. **Templates are PROGRAMS** - Execute every [[LLM:]] instruction exactly as written
+2. **NEVER show markup** - Hide all [[LLM:]], {{placeholders}}, @{examples}, and template syntax
+3. **STOP and EXECUTE** - When you see "apply tasks#" or "execute tasks#", STOP and run that task immediately
+4. **WAIT for user input** - At review points and after elicitation tasks
 
-- Determine which template to use (user-provided or list available for selection to user)
+## Execution Flow
 
-  - Agent-specific templates are listed in the agent's dependencies under `templates`. For each template listed, consider it a document the agent can create. So if an agent has:
+### 0. Check Workflow Plan (if configured)
 
-    @{example}
-    dependencies:
-    templates: - prd-tmpl - architecture-tmpl
-    @{/example}
+[[LLM: Check if plan tracking is enabled in core-config.yml]]
 
-    You would offer to create "PRD" and "Architecture" documents when the user asks what you can help with.
+- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
+- If plan exists and this document creation is part of the plan:
+  - Verify this is the expected next step
+  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
+  - If out of sequence and `enforceSequence: false`, ask for confirmation
+- Continue with normal execution after plan check
 
-- Gather all relevant inputs, or ask for them, or else rely on user providing necessary details to complete the document
-- Understand the document purpose and target audience
+### 1. Identify Template
 
-### 2. Determine Interaction Mode
+- Load from `templates#*` or `{root}/templates directory`
+- Agent-specific templates are listed in agent's dependencies
+- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
 
-Confirm with the user their preferred interaction style:
+### 2. Ask Interaction Mode
 
-- **Incremental:** Work through chunks of the document.
-- **YOLO Mode:** Draft complete document making reasonable assumptions in one shot. (Can be entered also after starting incremental by just typing /yolo)
+> 1. **Incremental** - Section by section with reviews
+> 2. **YOLO Mode** - Complete draft then review (user can type `/yolo` anytime to switch)
 
 ### 3. Execute Template
 
-- Load specified template from `templates#*` or the /templates directory
-- Follow ALL embedded LLM instructions within the template
-- Process template markup according to `utils#template-format` conventions
-
-### 4. Template Processing Rules
-
-#### CRITICAL: Never display template markup, LLM instructions, or examples to users
-
-- Replace all {{placeholders}} with actual content
-- Execute all [[LLM: instructions]] internally
-- Process `<<REPEAT>>` sections as needed
-- Evaluate ^^CONDITION^^ blocks and include only if applicable
+- Replace {{placeholders}} with real content
+- Execute [[LLM:]] instructions as you encounter them
+- Process <<REPEAT>> loops and ^^CONDITIONS^^
 - Use @{examples} for guidance but never output them
 
-### 5. Content Generation
+### 4. Key Execution Patterns
 
-- **Incremental Mode**: Present each major section for review before proceeding
-- **YOLO Mode**: Generate all sections, then review complete document with user
-- Apply any elicitation protocols specified in template
-- Incorporate user feedback and iterate as needed
+**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
 
-### 6. Validation
+- Draft the content
+- Present it to user
+- IMMEDIATELY execute the task
+- Wait for completion before continuing
 
-If template specifies a checklist:
+**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
 
-- Run the appropriate checklist against completed document
-- Document completion status for each item
-- Address any deficiencies found
-- Present validation summary to user
+- Finish the section
+- STOP and execute the task
+- Wait for user input
 
-### 7. Final Presentation
+### 5. Validation & Final Presentation
 
+- Run any specified checklists
 - Present clean, formatted content only
-- Ensure all sections are complete
-- DO NOT truncate or summarize content
-- Begin directly with document content (no preamble)
-- Include any handoff prompts specified in template
+- No truncation or summarization
+- Begin directly with content (no preamble)
+- Include any handoff prompts from template
 
-## Important Notes
+### 6. Update Workflow Plan (if applicable)
 
-- Template markup is for AI processing only - never expose to users
+[[LLM: After successful document creation]]
+
+- If plan tracking is enabled and document was part of plan:
+  - Call update-workflow-plan task to mark step complete
+  - Parameters: task: create-doc, step_id: {from plan}, status: complete
+  - Show next recommended step from plan
+
+## Common Mistakes to Avoid
+
+❌ Skipping elicitation tasks
+❌ Showing template markup to users
+❌ Continuing past STOP signals
+❌ Combining multiple review points
+
+✅ Execute ALL instructions in sequence
+✅ Present only clean, formatted content
+✅ Stop at every elicitation point
+✅ Wait for user confirmation when instructed
+
+## Remember
+
+Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
 ==================== END: tasks#create-doc ====================
 
 ==================== START: tasks#correct-course ====================
@@ -874,13 +891,9 @@ The story creation is successful when:
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
 ## Available Checklists
 
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
 
 ## Instructions
 
@@ -889,7 +902,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
+     - Load the appropriate checklist from {root}/checklists/
    - If no checklist specified:
      - Ask the user which checklist they want to use
      - Present the available options from the files in the checklists folder
@@ -1393,34 +1406,45 @@ Do not proceed with any recommendations until the user has validated your unders
 
 ### Existing Project Overview
 
-[[LLM: If working in IDE with project loaded, analyze the project structure and existing documentation. If working in web interface, request project upload or detailed project information from user.]]
+[[LLM: Check if document-project analysis was already performed. If yes, reference that output instead of re-analyzing.]]
 
-**Project Location**: [[LLM: Note if this is IDE-based analysis or user-provided information]]
+**Analysis Source**: [[LLM: Indicate one of the following:
+- Document-project output available at: {{path}}
+- IDE-based fresh analysis
+- User-provided information
+]]
 
-**Current Project State**: [[LLM: Brief description of what the project currently does and its primary purpose]]
+**Current Project State**: [[LLM: 
+- If document-project output exists: Extract summary from "High Level Architecture" and "Technical Summary" sections
+- Otherwise: Brief description of what the project currently does and its primary purpose
+]]
 
 ### Available Documentation Analysis
 
-[[LLM: Check for existing documentation in docs folder or provided by user. List what documentation is available and assess its completeness. Required documents include:
+[[LLM: 
+If document-project was run:
+- Note: "Document-project analysis available - using existing technical documentation"
+- List key documents created by document-project
+- Skip the missing documentation check below
 
-- Tech stack documentation
-- Source tree/architecture overview
-- Coding standards
-- API documentation or OpenAPI specs
-- External API integrations
-- UX/UI guidelines or existing patterns]]
+Otherwise, check for existing documentation:
+]]
 
 **Available Documentation**:
 
-- [ ] Tech Stack Documentation
-- [ ] Source Tree/Architecture
-- [ ] Coding Standards
-- [ ] API Documentation
-- [ ] External API Documentation
-- [ ] UX/UI Guidelines
+- [ ] Tech Stack Documentation [[LLM: If from document-project, check ✓]]
+- [ ] Source Tree/Architecture [[LLM: If from document-project, check ✓]]
+- [ ] Coding Standards [[LLM: If from document-project, may be partial]]
+- [ ] API Documentation [[LLM: If from document-project, check ✓]]
+- [ ] External API Documentation [[LLM: If from document-project, check ✓]]
+- [ ] UX/UI Guidelines [[LLM: May not be in document-project]]
+- [ ] Technical Debt Documentation [[LLM: If from document-project, check ✓]]
 - [ ] Other: \***\*\_\_\_\*\***
 
-[[LLM: If critical documentation is missing, STOP and recommend: "I recommend running the document-project task first to generate baseline documentation including tech-stack, source-tree, coding-standards, APIs, external-APIs, and UX/UI information. This will provide the foundation needed for a comprehensive brownfield PRD."]]
+[[LLM: 
+- If document-project was already run: "Using existing project analysis from document-project output."
+- If critical documentation is missing and no document-project: "I recommend running the document-project task first..."
+]]
 
 ### Enhancement Scope Definition
 
@@ -1510,13 +1534,19 @@ Do not proceed with any recommendations until the user has validated your unders
 
 ### Existing Technology Stack
 
-[[LLM: Document the current technology stack that must be maintained or integrated with]]
+[[LLM: 
+If document-project output available:
+- Extract from "Actual Tech Stack" table in High Level Architecture section
+- Include version numbers and any noted constraints
 
-**Languages**: [[LLM: Current programming languages in use]]
-**Frameworks**: [[LLM: Current frameworks and their versions]]
-**Database**: [[LLM: Current database technology and schema considerations]]
-**Infrastructure**: [[LLM: Current deployment and hosting infrastructure]]
-**External Dependencies**: [[LLM: Current third-party services and APIs]]
+Otherwise, document the current technology stack:
+]]
+
+**Languages**: [[LLM: From document-project or fresh analysis]]
+**Frameworks**: [[LLM: From document-project or fresh analysis]]
+**Database**: [[LLM: From document-project or fresh analysis]]
+**Infrastructure**: [[LLM: From document-project or fresh analysis]]
+**External Dependencies**: [[LLM: From document-project "External Services" section or fresh analysis]]
 
 ### Integration Approach
 
@@ -1547,12 +1577,19 @@ Do not proceed with any recommendations until the user has validated your unders
 
 ### Risk Assessment and Mitigation
 
-[[LLM: Identify risks specific to working with existing codebase]]
+[[LLM: 
+If document-project output available:
+- Reference "Technical Debt and Known Issues" section
+- Include "Workarounds and Gotchas" that might impact enhancement
+- Note any identified constraints from "Critical Technical Debt"
 
-**Technical Risks**: [[LLM: Risks related to modifying existing code]]
-**Integration Risks**: [[LLM: Risks in integrating with existing systems]]
-**Deployment Risks**: [[LLM: Risks in deploying alongside existing features]]
-**Mitigation Strategies**: [[LLM: Specific strategies to address identified risks]]
+Build risk assessment incorporating existing known issues:
+]]
+
+**Technical Risks**: [[LLM: Include risks from document-project + new enhancement risks]]
+**Integration Risks**: [[LLM: Reference integration constraints from document-project]]
+**Deployment Risks**: [[LLM: Include deployment gotchas from document-project]]
+**Mitigation Strategies**: [[LLM: Address both existing and new risks]]
 
 ## Epic and Story Structure
 

dist/agents/po.txt

@@ -106,13 +106,9 @@ dependencies:
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
 ## Available Checklists
 
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
 
 ## Instructions
 
@@ -121,7 +117,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
+     - Load the appropriate checklist from {root}/checklists/
    - If no checklist specified:
      - Ask the user which checklist they want to use
      - Present the available options from the files in the checklists folder

dist/agents/sm.txt

@@ -118,6 +118,22 @@ To identify the next logical story based on project progress and epic definition
   - `architecture.architectureSharded`: Whether architecture is sharded
   - `architecture.architectureFile`: Location of monolithic architecture
   - `architecture.architectureShardedLocation`: Location of sharded architecture files
+  - `workflow.trackProgress`: Whether workflow plan tracking is enabled
+  - `workflow.planFile`: Location of workflow plan (if tracking enabled)
+
+### 0.5 Check Workflow Plan (if configured)
+
+[[LLM: Check if workflow plan tracking is enabled]]
+
+- If `workflow.trackProgress: true`, check for active plan at `workflow.planFile`
+- If plan exists:
+  - Parse plan to check if story creation is the expected next step
+  - If out of sequence and `workflow.enforceSequence: true`:
+    - Show warning: "The workflow plan indicates you should complete {expected_step} before creating stories."
+    - Block execution unless user explicitly overrides
+  - If out of sequence and `workflow.enforceSequence: false`:
+    - Show warning but allow continuation with confirmation
+- Continue with story identification after plan check
 
 ### 1. Identify Next Story for Preparation
 
@@ -341,6 +357,15 @@ Provide a summary to the user including:
 - Recommendations for story review before approval
 - Next steps: Story should be reviewed by PO for approval before dev work begins
 
+### 10. Update Workflow Plan (if applicable)
+
+[[LLM: After successful story creation]]
+
+- If `workflow.trackProgress: true` and `workflow.updateOnCompletion: true`:
+  - Call update-workflow-plan task to mark story creation step complete
+  - Parameters: task: create-next-story, step_id: {from plan}, status: complete
+  - If plan shows next step, mention it in completion message
+
 [[LLM: Remember - The success of this task depends on extracting real, specific technical details from the architecture shards. The dev agent should have everything they need in the story file without having to search through multiple documents.]]
 ==================== END: tasks#create-next-story ====================
 
@@ -349,13 +374,9 @@ Provide a summary to the user including:
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
 ## Available Checklists
 
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
 
 ## Instructions
 
@@ -364,7 +385,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
+     - Load the appropriate checklist from {root}/checklists/
    - If no checklist specified:
      - Ask the user which checklist they want to use
      - Present the available options from the files in the checklists folder

dist/agents/ux-expert.txt

@@ -464,76 +464,93 @@ Present these numbered options to the user:
 
 ## Purpose
 
-- Generate documents from any specified template following embedded instructions from the perspective of the selected agent persona
+Generate documents from templates by EXECUTING (not just reading) embedded instructions from the perspective of the selected agent persona.
 
-## Instructions
+## CRITICAL RULES
 
-### 1. Identify Template and Context
+1. **Templates are PROGRAMS** - Execute every [[LLM:]] instruction exactly as written
+2. **NEVER show markup** - Hide all [[LLM:]], {{placeholders}}, @{examples}, and template syntax
+3. **STOP and EXECUTE** - When you see "apply tasks#" or "execute tasks#", STOP and run that task immediately
+4. **WAIT for user input** - At review points and after elicitation tasks
 
-- Determine which template to use (user-provided or list available for selection to user)
+## Execution Flow
 
-  - Agent-specific templates are listed in the agent's dependencies under `templates`. For each template listed, consider it a document the agent can create. So if an agent has:
+### 0. Check Workflow Plan (if configured)
 
-    @{example}
-    dependencies:
-    templates: - prd-tmpl - architecture-tmpl
-    @{/example}
+[[LLM: Check if plan tracking is enabled in core-config.yml]]
 
-    You would offer to create "PRD" and "Architecture" documents when the user asks what you can help with.
+- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
+- If plan exists and this document creation is part of the plan:
+  - Verify this is the expected next step
+  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
+  - If out of sequence and `enforceSequence: false`, ask for confirmation
+- Continue with normal execution after plan check
 
-- Gather all relevant inputs, or ask for them, or else rely on user providing necessary details to complete the document
-- Understand the document purpose and target audience
+### 1. Identify Template
 
-### 2. Determine Interaction Mode
+- Load from `templates#*` or `{root}/templates directory`
+- Agent-specific templates are listed in agent's dependencies
+- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
 
-Confirm with the user their preferred interaction style:
+### 2. Ask Interaction Mode
 
-- **Incremental:** Work through chunks of the document.
-- **YOLO Mode:** Draft complete document making reasonable assumptions in one shot. (Can be entered also after starting incremental by just typing /yolo)
+> 1. **Incremental** - Section by section with reviews
+> 2. **YOLO Mode** - Complete draft then review (user can type `/yolo` anytime to switch)
 
 ### 3. Execute Template
 
-- Load specified template from `templates#*` or the /templates directory
-- Follow ALL embedded LLM instructions within the template
-- Process template markup according to `utils#template-format` conventions
-
-### 4. Template Processing Rules
-
-#### CRITICAL: Never display template markup, LLM instructions, or examples to users
-
-- Replace all {{placeholders}} with actual content
-- Execute all [[LLM: instructions]] internally
-- Process `<<REPEAT>>` sections as needed
-- Evaluate ^^CONDITION^^ blocks and include only if applicable
+- Replace {{placeholders}} with real content
+- Execute [[LLM:]] instructions as you encounter them
+- Process <<REPEAT>> loops and ^^CONDITIONS^^
 - Use @{examples} for guidance but never output them
 
-### 5. Content Generation
+### 4. Key Execution Patterns
 
-- **Incremental Mode**: Present each major section for review before proceeding
-- **YOLO Mode**: Generate all sections, then review complete document with user
-- Apply any elicitation protocols specified in template
-- Incorporate user feedback and iterate as needed
+**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
 
-### 6. Validation
+- Draft the content
+- Present it to user
+- IMMEDIATELY execute the task
+- Wait for completion before continuing
 
-If template specifies a checklist:
+**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
 
-- Run the appropriate checklist against completed document
-- Document completion status for each item
-- Address any deficiencies found
-- Present validation summary to user
+- Finish the section
+- STOP and execute the task
+- Wait for user input
 
-### 7. Final Presentation
+### 5. Validation & Final Presentation
 
+- Run any specified checklists
 - Present clean, formatted content only
-- Ensure all sections are complete
-- DO NOT truncate or summarize content
-- Begin directly with document content (no preamble)
-- Include any handoff prompts specified in template
+- No truncation or summarization
+- Begin directly with content (no preamble)
+- Include any handoff prompts from template
 
-## Important Notes
+### 6. Update Workflow Plan (if applicable)
 
-- Template markup is for AI processing only - never expose to users
+[[LLM: After successful document creation]]
+
+- If plan tracking is enabled and document was part of plan:
+  - Call update-workflow-plan task to mark step complete
+  - Parameters: task: create-doc, step_id: {from plan}, status: complete
+  - Show next recommended step from plan
+
+## Common Mistakes to Avoid
+
+❌ Skipping elicitation tasks
+❌ Showing template markup to users
+❌ Continuing past STOP signals
+❌ Combining multiple review points
+
+✅ Execute ALL instructions in sequence
+✅ Present only clean, formatted content
+✅ Stop at every elicitation point
+✅ Wait for user confirmation when instructed
+
+## Remember
+
+Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
 ==================== END: tasks#create-doc ====================
 
 ==================== START: tasks#execute-checklist ====================
@@ -541,13 +558,9 @@ If template specifies a checklist:
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
 ## Available Checklists
 
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
 
 ## Instructions
 
@@ -556,7 +569,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
+     - Load the appropriate checklist from {root}/checklists/
    - If no checklist specified:
      - Ask the user which checklist they want to use
      - Present the available options from the files in the checklists folder

dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt

@@ -104,76 +104,93 @@ dependencies:
 
 ## Purpose
 
-- Generate documents from any specified template following embedded instructions from the perspective of the selected agent persona
+Generate documents from templates by EXECUTING (not just reading) embedded instructions from the perspective of the selected agent persona.
 
-## Instructions
+## CRITICAL RULES
 
-### 1. Identify Template and Context
+1. **Templates are PROGRAMS** - Execute every [[LLM:]] instruction exactly as written
+2. **NEVER show markup** - Hide all [[LLM:]], {{placeholders}}, @{examples}, and template syntax
+3. **STOP and EXECUTE** - When you see "apply tasks#" or "execute tasks#", STOP and run that task immediately
+4. **WAIT for user input** - At review points and after elicitation tasks
 
-- Determine which template to use (user-provided or list available for selection to user)
+## Execution Flow
 
-  - Agent-specific templates are listed in the agent's dependencies under `templates`. For each template listed, consider it a document the agent can create. So if an agent has:
+### 0. Check Workflow Plan (if configured)
 
-    @{example}
-    dependencies:
-    templates: - prd-tmpl - architecture-tmpl
-    @{/example}
+[[LLM: Check if plan tracking is enabled in core-config.yml]]
 
-    You would offer to create "PRD" and "Architecture" documents when the user asks what you can help with.
+- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
+- If plan exists and this document creation is part of the plan:
+  - Verify this is the expected next step
+  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
+  - If out of sequence and `enforceSequence: false`, ask for confirmation
+- Continue with normal execution after plan check
 
-- Gather all relevant inputs, or ask for them, or else rely on user providing necessary details to complete the document
-- Understand the document purpose and target audience
+### 1. Identify Template
 
-### 2. Determine Interaction Mode
+- Load from `templates#*` or `{root}/templates directory`
+- Agent-specific templates are listed in agent's dependencies
+- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
 
-Confirm with the user their preferred interaction style:
+### 2. Ask Interaction Mode
 
-- **Incremental:** Work through chunks of the document.
-- **YOLO Mode:** Draft complete document making reasonable assumptions in one shot. (Can be entered also after starting incremental by just typing /yolo)
+> 1. **Incremental** - Section by section with reviews
+> 2. **YOLO Mode** - Complete draft then review (user can type `/yolo` anytime to switch)
 
 ### 3. Execute Template
 
-- Load specified template from `templates#*` or the /templates directory
-- Follow ALL embedded LLM instructions within the template
-- Process template markup according to `utils#template-format` conventions
-
-### 4. Template Processing Rules
-
-#### CRITICAL: Never display template markup, LLM instructions, or examples to users
-
-- Replace all {{placeholders}} with actual content
-- Execute all [[LLM: instructions]] internally
-- Process `<<REPEAT>>` sections as needed
-- Evaluate ^^CONDITION^^ blocks and include only if applicable
+- Replace {{placeholders}} with real content
+- Execute [[LLM:]] instructions as you encounter them
+- Process <<REPEAT>> loops and ^^CONDITIONS^^
 - Use @{examples} for guidance but never output them
 
-### 5. Content Generation
+### 4. Key Execution Patterns
 
-- **Incremental Mode**: Present each major section for review before proceeding
-- **YOLO Mode**: Generate all sections, then review complete document with user
-- Apply any elicitation protocols specified in template
-- Incorporate user feedback and iterate as needed
+**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
 
-### 6. Validation
+- Draft the content
+- Present it to user
+- IMMEDIATELY execute the task
+- Wait for completion before continuing
 
-If template specifies a checklist:
+**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
 
-- Run the appropriate checklist against completed document
-- Document completion status for each item
-- Address any deficiencies found
-- Present validation summary to user
+- Finish the section
+- STOP and execute the task
+- Wait for user input
 
-### 7. Final Presentation
+### 5. Validation & Final Presentation
 
+- Run any specified checklists
 - Present clean, formatted content only
-- Ensure all sections are complete
-- DO NOT truncate or summarize content
-- Begin directly with document content (no preamble)
-- Include any handoff prompts specified in template
+- No truncation or summarization
+- Begin directly with content (no preamble)
+- Include any handoff prompts from template
 
-## Important Notes
+### 6. Update Workflow Plan (if applicable)
 
-- Template markup is for AI processing only - never expose to users
+[[LLM: After successful document creation]]
+
+- If plan tracking is enabled and document was part of plan:
+  - Call update-workflow-plan task to mark step complete
+  - Parameters: task: create-doc, step_id: {from plan}, status: complete
+  - Show next recommended step from plan
+
+## Common Mistakes to Avoid
+
+❌ Skipping elicitation tasks
+❌ Showing template markup to users
+❌ Continuing past STOP signals
+❌ Combining multiple review points
+
+✅ Execute ALL instructions in sequence
+✅ Present only clean, formatted content
+✅ Stop at every elicitation point
+✅ Wait for user confirmation when instructed
+
+## Remember
+
+Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
 ==================== END: tasks#create-doc ====================
 
 ==================== START: tasks#execute-checklist ====================
@@ -181,13 +198,9 @@ If template specifies a checklist:
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
 ## Available Checklists
 
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
 
 ## Instructions
 
@@ -196,7 +209,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
+     - Load the appropriate checklist from {root}/checklists/
    - If no checklist specified:
      - Ask the user which checklist they want to use
      - Present the available options from the files in the checklists folder

dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt

@@ -112,13 +112,9 @@ dependencies:
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
 ## Available Checklists
 
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
 
 ## Instructions
 
@@ -127,7 +123,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
+     - Load the appropriate checklist from {root}/checklists/
    - If no checklist specified:
      - Ask the user which checklist they want to use
      - Present the available options from the files in the checklists folder

dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt

@@ -316,13 +316,9 @@ This task ensures game development stories are immediately actionable and enable
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
 ## Available Checklists
 
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
 
 ## Instructions
 
@@ -331,7 +327,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
+     - Load the appropriate checklist from {root}/checklists/
    - If no checklist specified:
      - Ask the user which checklist they want to use
      - Present the available options from the files in the checklists folder

dist/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.txt

@@ -736,17 +736,17 @@ IMPORTANT: Work through plan.md checklist systematically!
 
 **Step 2: Copy Core Utilities**
 
-Before proceeding, copy these essential files from bmad-core:
+Before proceeding, copy these essential files from common:
 
 ```bash
 # Copy core task utilities
-cp bmad-core/tasks/create-doc.md expansion-packs/{pack-name}/tasks/
-cp bmad-core/tasks/execute-checklist.md expansion-packs/{pack-name}/tasks/
+cp common/tasks/create-doc.md expansion-packs/{pack-name}/tasks/
+cp common/tasks/execute-checklist.md expansion-packs/{pack-name}/tasks/
 
 # Copy core utility files
 mkdir -p expansion-packs/{pack-name}/utils
-cp bmad-core/utils/template-format.md expansion-packs/{pack-name}/utils/
-cp bmad-core/utils/workflow-management.md expansion-packs/{pack-name}/utils/
+cp common/utils/template-format.md expansion-packs/{pack-name}/utils/
+cp common/utils/workflow-management.md expansion-packs/{pack-name}/utils/
 ```
 
 **Step 3: Technical Implementation**

dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt

@@ -105,76 +105,93 @@ dependencies:
 
 ## Purpose
 
-- Generate documents from any specified template following embedded instructions from the perspective of the selected agent persona
+Generate documents from templates by EXECUTING (not just reading) embedded instructions from the perspective of the selected agent persona.
 
-## Instructions
+## CRITICAL RULES
 
-### 1. Identify Template and Context
+1. **Templates are PROGRAMS** - Execute every [[LLM:]] instruction exactly as written
+2. **NEVER show markup** - Hide all [[LLM:]], {{placeholders}}, @{examples}, and template syntax
+3. **STOP and EXECUTE** - When you see "apply tasks#" or "execute tasks#", STOP and run that task immediately
+4. **WAIT for user input** - At review points and after elicitation tasks
 
-- Determine which template to use (user-provided or list available for selection to user)
+## Execution Flow
 
-  - Agent-specific templates are listed in the agent's dependencies under `templates`. For each template listed, consider it a document the agent can create. So if an agent has:
+### 0. Check Workflow Plan (if configured)
 
-    @{example}
-    dependencies:
-    templates: - prd-tmpl - architecture-tmpl
-    @{/example}
+[[LLM: Check if plan tracking is enabled in core-config.yml]]
 
-    You would offer to create "PRD" and "Architecture" documents when the user asks what you can help with.
+- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
+- If plan exists and this document creation is part of the plan:
+  - Verify this is the expected next step
+  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
+  - If out of sequence and `enforceSequence: false`, ask for confirmation
+- Continue with normal execution after plan check
 
-- Gather all relevant inputs, or ask for them, or else rely on user providing necessary details to complete the document
-- Understand the document purpose and target audience
+### 1. Identify Template
 
-### 2. Determine Interaction Mode
+- Load from `templates#*` or `{root}/templates directory`
+- Agent-specific templates are listed in agent's dependencies
+- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
 
-Confirm with the user their preferred interaction style:
+### 2. Ask Interaction Mode
 
-- **Incremental:** Work through chunks of the document.
-- **YOLO Mode:** Draft complete document making reasonable assumptions in one shot. (Can be entered also after starting incremental by just typing /yolo)
+> 1. **Incremental** - Section by section with reviews
+> 2. **YOLO Mode** - Complete draft then review (user can type `/yolo` anytime to switch)
 
 ### 3. Execute Template
 
-- Load specified template from `templates#*` or the /templates directory
-- Follow ALL embedded LLM instructions within the template
-- Process template markup according to `utils#template-format` conventions
-
-### 4. Template Processing Rules
-
-#### CRITICAL: Never display template markup, LLM instructions, or examples to users
-
-- Replace all {{placeholders}} with actual content
-- Execute all [[LLM: instructions]] internally
-- Process `<<REPEAT>>` sections as needed
-- Evaluate ^^CONDITION^^ blocks and include only if applicable
+- Replace {{placeholders}} with real content
+- Execute [[LLM:]] instructions as you encounter them
+- Process <<REPEAT>> loops and ^^CONDITIONS^^
 - Use @{examples} for guidance but never output them
 
-### 5. Content Generation
+### 4. Key Execution Patterns
 
-- **Incremental Mode**: Present each major section for review before proceeding
-- **YOLO Mode**: Generate all sections, then review complete document with user
-- Apply any elicitation protocols specified in template
-- Incorporate user feedback and iterate as needed
+**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
 
-### 6. Validation
+- Draft the content
+- Present it to user
+- IMMEDIATELY execute the task
+- Wait for completion before continuing
 
-If template specifies a checklist:
+**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
 
-- Run the appropriate checklist against completed document
-- Document completion status for each item
-- Address any deficiencies found
-- Present validation summary to user
+- Finish the section
+- STOP and execute the task
+- Wait for user input
 
-### 7. Final Presentation
+### 5. Validation & Final Presentation
 
+- Run any specified checklists
 - Present clean, formatted content only
-- Ensure all sections are complete
-- DO NOT truncate or summarize content
-- Begin directly with document content (no preamble)
-- Include any handoff prompts specified in template
+- No truncation or summarization
+- Begin directly with content (no preamble)
+- Include any handoff prompts from template
 
-## Important Notes
+### 6. Update Workflow Plan (if applicable)
 
-- Template markup is for AI processing only - never expose to users
+[[LLM: After successful document creation]]
+
+- If plan tracking is enabled and document was part of plan:
+  - Call update-workflow-plan task to mark step complete
+  - Parameters: task: create-doc, step_id: {from plan}, status: complete
+  - Show next recommended step from plan
+
+## Common Mistakes to Avoid
+
+❌ Skipping elicitation tasks
+❌ Showing template markup to users
+❌ Continuing past STOP signals
+❌ Combining multiple review points
+
+✅ Execute ALL instructions in sequence
+✅ Present only clean, formatted content
+✅ Stop at every elicitation point
+✅ Wait for user confirmation when instructed
+
+## Remember
+
+Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
 ==================== END: tasks#create-doc ====================
 
 ==================== START: tasks#review-infrastructure ====================

docs/agentic-tools/claude-code-guide.md

@@ -0,0 +1,36 @@
+# BMAD Method Guide for Claude Code
+
+This guide covers Claude Code-specific setup and usage with BMAD Method. For the complete workflow, see the [BMAD Workflow Guide](../bmad-workflow-guide.md).
+
+## Installation
+
+When running `npx bmad-method install`, select **Claude Code** as your IDE. This creates:
+
+- `.bmad-core/` folder with all agents
+- `.claude/commands/` folder with agent command files (`.md`)
+
+## Using BMAD Agents in Claude Code
+
+Type `/agent-name` in your chat to activate an agent:
+
+- `/bmad-master` - Universal task executor
+- `/sm` - Scrum Master
+- `/dev` - Full-stack developer
+- `/architect` - Solution architect
+- `/pm` - Product manager
+- `/analyst` - Business analyst
+- `/qa` - QA specialist
+- `/po` - Product owner
+- `/ux-expert` - UX specialist
+
+## Claude Code-Specific Features
+
+- **Command files**: Stored in `.claude/commands/` as `.md` files
+- **Activation**: Use forward slash `/` prefix for all agents
+- **Chat management**: Start new chats when switching agents for clean context
+
+## Tips for Claude Code Users
+
+- Commands are auto-suggested as you type `/`
+- Each agent supports `*help` to see available commands
+- Claude Code maintains excellent context within each chat

docs/agentic-tools/cline-guide.md

@@ -0,0 +1,42 @@
+# BMAD Method Guide for Cline (VS Code)
+
+This guide covers Cline-specific setup and usage with BMAD Method. For the complete workflow, see the [BMAD Workflow Guide](../bmad-workflow-guide.md).
+
+## Installation
+
+When running `npx bmad-method install`, select **Cline** as your IDE. This creates:
+
+- `.clinerules/` directory with numbered agent rule files (`.md`)
+- Agents ordered by priority (bmad-master first)
+
+## Using BMAD Agents in Cline
+
+1. **Open Cline panel** in VS Code
+2. **Type `@agent-name`** in the chat (e.g., `@dev`, `@sm`, `@architect`)
+3. The agent adopts that persona for the conversation
+
+## Available Agents
+
+All agents use `@` prefix:
+
+- `@bmad-master` - Universal task executor
+- `@sm` - Scrum Master
+- `@dev` - Full-stack developer
+- `@architect` - Solution architect
+- `@pm` - Product manager
+- `@analyst` - Business analyst
+- `@qa` - QA specialist
+- `@po` - Product owner
+- `@ux-expert` - UX specialist
+
+## Cline-Specific Features
+
+- **Rule files**: Stored as numbered files in `.clinerules/` (e.g., `01-bmad-master.md`)
+- **Agent ordering**: Prioritized list with core agents first
+- **VS Code integration**: Works within VS Code's Cline extension panel
+
+## Tips for Cline Users
+
+- Cline maintains conversation context well
+- Use `@agent-name` at the start of your message for best results
+- Agent rules are loaded automatically when mentioned

docs/agentic-tools/cursor-guide.md

@@ -0,0 +1,37 @@
+# BMAD Method Guide for Cursor
+
+This guide covers Cursor-specific setup and usage with BMAD Method. For the complete workflow, see the [BMAD Workflow Guide](../bmad-workflow-guide.md).
+
+## Installation
+
+When running `npx bmad-method install`, select **Cursor** as your IDE. This creates:
+
+- `.bmad-core/` folder with all agents
+- `.cursor/rules/` folder with agent rule files (`.mdc`)
+
+## Using BMAD Agents in Cursor
+
+Type `@agent-name` in chat (Ctrl+L / Cmd+L) to activate an agent:
+
+- `@bmad-master` - Universal task executor
+- `@sm` - Scrum Master
+- `@dev` - Full-stack developer
+- `@architect` - Solution architect
+- `@pm` - Product manager
+- `@analyst` - Business analyst
+- `@qa` - QA specialist
+- `@po` - Product owner
+- `@ux-expert` - UX specialist
+
+## Cursor-Specific Features
+
+- **Rule files**: Stored in `.cursor/rules/` as `.mdc` files
+- **Auto-completion**: Cursor suggests agents as you type `@`
+- **Context awareness**: Agents can see your current file selection
+- **Custom agents**: For better performance, copy agent content into Cursor's custom modes
+
+## Tips for Cursor Users
+
+- Start new chats when switching agents
+- Each agent supports `*help` to see available commands
+- Leverage Cursor's file context for more accurate assistance

docs/agentic-tools/gemini-cli-guide.md

@@ -0,0 +1,46 @@
+# BMAD Method Guide for Gemini CLI
+
+This guide covers Gemini CLI-specific setup and usage with BMAD Method. For the complete workflow, see the [BMAD Workflow Guide](../bmad-workflow-guide.md).
+
+## Installation
+
+When running `npx bmad-method install`, select **Gemini CLI** as your IDE. This creates:
+
+- `.gemini/agents/` directory with all agent context files
+- `.gemini/settings.json` configured to load all agents automatically
+
+## Using BMAD Agents with Gemini CLI
+
+Simply mention the agent in your prompt:
+
+- "As @dev, implement the login feature"
+- "Acting as @architect, review this system design"
+- "@sm, create the next story for our project"
+
+The Gemini CLI automatically loads the appropriate agent context.
+
+## Available Agents
+
+All agents are referenced with `@` in prompts:
+
+- `@bmad-master` - Universal task executor
+- `@sm` - Scrum Master
+- `@dev` - Full-stack developer
+- `@architect` - Solution architect
+- `@pm` - Product manager
+- `@analyst` - Business analyst
+- `@qa` - QA specialist
+- `@po` - Product owner
+- `@ux-expert` - UX specialist
+
+## Gemini CLI-Specific Features
+
+- **Context files**: All agents loaded as context in `.gemini/agents/`
+- **Automatic loading**: Settings.json ensures agents are always available
+- **Natural language**: No special syntax needed, just mention the agent
+
+## Tips for Gemini CLI Users
+
+- Be explicit about which agent you're addressing
+- You can switch agents mid-conversation by mentioning a different one
+- The CLI maintains context across your session

docs/agentic-tools/roo-code-guide.md

@@ -0,0 +1,46 @@
+# BMAD Method Guide for Roo Code
+
+This guide covers Roo Code-specific setup and usage with BMAD Method. For the complete workflow, see the [BMAD Workflow Guide](../bmad-workflow-guide.md).
+
+## Installation
+
+When running `npx bmad-method install`, select **Roo Code** as your IDE. This creates:
+
+- `.bmad-core/` folder with all agents
+- `.roomodes` file in project root with custom modes
+
+## Using BMAD Agents in Roo Code
+
+Select mode from the mode selector (usually in status bar):
+
+- `bmad-bmad-master` - 🧙 Universal task executor
+- `bmad-sm` - 🏃 Scrum Master
+- `bmad-dev` - 💻 Full-stack developer
+- `bmad-architect` - 🏗️ Solution architect
+- `bmad-pm` - 📋 Product manager
+- `bmad-analyst` - 📊 Business analyst
+- `bmad-qa` - 🧪 QA specialist
+- `bmad-po` - 🎯 Product owner
+- `bmad-ux-expert` - 🎨 UX specialist
+
+## Roo Code-Specific Features
+
+- **Mode file**: `.roomodes` in project root
+- **Mode switching**: Use mode selector instead of starting new chats
+- **Context preservation**: Maintains context across mode switches
+- **File permissions**: Each agent has specific file access:
+
+### File Permission Summary
+
+- **Documentation agents** (analyst, pm, po, sm): `.md`, `.txt` only
+- **bmad-architect**: `.md`, `.txt`, `.yml`, `.yaml`, `.json`
+- **bmad-qa**: Test files (`.test.*`, `.spec.*`) and `.md`
+- **bmad-ux-expert**: `.md`, `.css`, `.scss`, `.html`, `.jsx`, `.tsx`
+- **Full access**: `bmad-dev`, `bmad-bmad-master`, `bmad-orchestrator`
+
+## Tips for Roo Code Users
+
+- Switch modes instead of starting new chats
+- Each mode supports `*help` to see available commands
+- Agents respect file permission boundaries
+- Context persists across mode switches

docs/agentic-tools/windsurf-guide.md

@@ -0,0 +1,37 @@
+# BMAD Method Guide for Windsurf
+
+This guide covers Windsurf-specific setup and usage with BMAD Method. For the complete workflow, see the [BMAD Workflow Guide](../bmad-workflow-guide.md).
+
+## Installation
+
+When running `npx bmad-method install`, select **Windsurf** as your IDE. This creates:
+
+- `.bmad-core/` folder with all agents
+- `.windsurf/rules/` folder with agent rule files (`.md`)
+
+## Using BMAD Agents in Windsurf
+
+Type `@agent-name` in chat to activate an agent:
+
+- `@bmad-master` - Universal task executor
+- `@sm` - Scrum Master
+- `@dev` - Full-stack developer
+- `@architect` - Solution architect
+- `@pm` - Product manager
+- `@analyst` - Business analyst
+- `@qa` - QA specialist
+- `@po` - Product owner
+- `@ux-expert` - UX specialist
+
+## Windsurf-Specific Features
+
+- **Rule files**: Stored in `.windsurf/rules/` as `.md` files
+- **Activation**: Use `@` prefix to mention agents
+- **Collaborative features**: Works well with BMAD's agent-switching pattern
+- **Project context**: Agents have access to your full project context
+
+## Tips for Windsurf Users
+
+- Start new chats when switching agents
+- Each agent supports `*help` to see available commands
+- Leverage Windsurf's collaboration features for team reviews

docs/bmad-workflow-guide.md

@@ -22,7 +22,7 @@ The BMAD Method follows a structured approach to AI-assisted software developmen
    ```
 
    - Choose "Complete installation"
-   - Select your IDE (Cursor, Claude Code, Windsurf, or Roo Code)
+   - Select your IDE (Cursor, Claude Code, Windsurf, Roo Code, or VS Code Copilot)
 
 2. **Verify installation**:
    - `.bmad-core/` folder created with all agents
@@ -113,6 +113,7 @@ Follow the SM → Dev cycle for systematic story development:
 - **Cursor**: `@agent-name` (e.g., `@bmad-master`)
 - **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
 - **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
+- **VS Code Copilot**: Open the Chat view (`⌃⌘I` on Mac, `Ctrl+Alt+I` on Windows/Linux) and select **Agent** from the chat mode selector.
 
 ### Chat Management:
 

docs/claude-code-guide.md

@@ -1,121 +0,0 @@
-# BMAD Method Guide for Claude Code
-
-This guide walks you through the complete BMAD workflow using Claude Code as your AI-powered IDE.
-
-## Step 1: Install BMAD in Your Project
-
-1. Navigate to your project directory
-2. Run the BMAD installer:
-
-   ```bash
-   npx bmad-method install
-   ```
-
-3. When prompted:
-   - **Installation Type**: Choose "Complete installation (recommended)"
-   - **IDE**: Select "Claude Code"
-
-This creates a `.bmad-core` folder with all agents and a `.claude/commands` folder with agent commands.
-
-## Step 2: Set Up Team Fullstack in Gemini
-
-For ideation and planning, use Google's Gemini Custom Gem with the team-fullstack configuration:
-
-1. Open [Google gems](https://gemini.google.com/gems/view)
-2. Create a new Gem - give it a title and description
-3. Copy the contents of `.<install location>/<web-bundles>/teams/team-fullstack.txt` (location can vary if you chose a non default installation location for the bundles) - or just use the bundle premade from the repo dist folder.
-4. Paste this content into Gemini to set up the team
-
-### Gemini Planning Phase
-
-In Gemini, ask the BMAD team to help you:
-
-- **Ideate** your project concept
-- **Brainstorm** features and requirements
-- **Create a PRD** (Product Requirements Document)
-- **Design the architecture**
-
-Ask questions like:
-
-- "Help me brainstorm a [type of application] that does [core functionality]"
-- "Create a comprehensive PRD for this concept"
-- "Design the technical architecture for this system"
-
-Copy the PRD and architecture documents that Gemini creates into your project's `docs/` folder:
-
-- `docs/prd.md`
-- `docs/architecture.md`
-
-## Step 3: Back to Claude Code - Document Sharding
-
-Once you have your PRD and architecture documents in the `docs/` folder:
-
-1. **Start a new chat in Claude Code**
-2. **Load the bmad-master agent**: Type `/bmad-master`
-3. **Shard the PRD**: Type `*shard-doc docs/prd.md prd`
-4. **Shard the architecture**: Type `*shard-doc docs/architecture.md architecture`
-
-This creates organized folders:
-
-- `docs/prd/` - Contains broken down PRD sections
-- `docs/architecture/` - Contains broken down architecture sections
-
-## Step 4: Story Development Cycle
-
-Now begin the iterative development cycle:
-
-### Create Stories (Scrum Master)
-
-1. **Start a new chat**
-2. **Load SM agent**: Type `/sm`
-3. **Create story**: Type `*create` (this runs the create-next-story task)
-4. **Review the generated story**
-5. **If approved**: Set story status to "Approved" in the story file
-
-### Implement Stories (Developer)
-
-1. **Start a new chat**
-2. **Load Dev agent**: Type `/dev`
-3. **The agent will ask which story to implement**
-4. **Follow the development tasks** the agent provides
-5. **When story is complete**: Mark status as "Done"
-
-### Repeat the Cycle
-
-1. **Start a new chat with SM agent** (`/sm`)
-2. **Create next story**: Type `*create`
-3. **Review and approve**
-4. **Start new chat with Dev agent** (`/dev`)
-5. **Implement the story**
-6. **Repeat until project complete**
-
-## Available Commands in Claude Code
-
-All BMAD agents are available as Claude Code commands:
-
-- `/bmad-master` - Universal task executor
-- `/sm` - Scrum Master for story creation
-- `/dev` - Full-stack developer for implementation
-- `/architect` - Solution architect for design
-- `/pm` - Product manager for planning
-- `/analyst` - Business analyst for requirements
-- `/qa` - QA specialist for testing
-- `/po` - Product owner for prioritization
-- `/ux-expert` - UX specialist for design
-
-## Key Workflow Principles
-
-1. **Always start new chats** when switching agents to avoid context confusion
-2. **Use Gemini for initial planning** and ideation with the team-fullstack bundle
-3. **Use bmad-master for document management** (sharding, templates, etc.)
-4. **Follow the SM → Dev cycle** for consistent story development
-5. **Review and approve stories** before implementation begins
-
-## Tips for Success
-
-- **Keep chats focused**: Each chat should have one agent and one primary task
-- **Use \*help command**: Every agent supports `*help` to see available commands
-- **Review generated content**: Always review and approve stories before marking them ready
-- **Maintain status updates**: Keep story statuses current (Draft → Approved → InProgress → Done)
-
-This workflow ensures systematic, AI-assisted development following agile principles with clear handoffs between planning, story creation, and implementation phases.

docs/core-architecture.md

@@ -204,12 +204,181 @@ graph TD
     F -->|Approved| G["Dev: Implement Story"]
     F -->|Needs Changes| E
     G --> H["Dev: Complete story Tasks"]
-    H --> I{"User Verification"}
-    I -->|Verified Complete| J["Mark Story as Done"]
-    I -->|Needs Fixes| G
-    J --> E
+    H --> I["Dev: Mark Ready for Review"]
+    I --> J{"User Verification"}
+    J -->|Request QA Review| K["QA: Run review-story task"]
+    J -->|Approve Without QA| M["Mark Story as Done"]
+    K --> L{"QA Review Results"}
+    L -->|Needs Work| G
+    L -->|Approved| M["Mark Story as Done"]
+    J -->|Needs Fixes| G
+    M --> E
 
-    style J fill:#34a853,color:#fff
+    style M fill:#34a853,color:#fff
+    style K fill:#f9ab00,color:#fff
 ```
 
-This cycle continues, with the Scrum Master and Developer agents working in tandem, until all stories in the epic are completed.
+This cycle continues, with the Scrum Master, Developer, and optionally QA agents working together. The QA agent provides senior developer review capabilities through the `review-story` task, offering code refactoring, quality improvements, and knowledge transfer. This ensures high code quality while maintaining development velocity.
+
+## 8. Complete Source Tree
+
+The BMAD-METHOD project structure is designed for clarity, modularity, and extensibility. Here's the complete source tree with explanations:
+
+```plaintext
+bmad-method/
+├── .bmad-core/                    # Core framework (installed in user projects)
+│   ├── agents/                    # Individual agent definitions
+│   │   ├── analyst.md            # Business analyst agent
+│   │   ├── architect.md          # Solution architect agent
+│   │   ├── bmad-master.md        # Universal expert agent
+│   │   ├── bmad-orchestrator.md  # Multi-agent coordinator
+│   │   ├── dev.md                # Full-stack developer agent
+│   │   ├── pm.md                 # Product manager agent
+│   │   ├── po.md                 # Product owner agent
+│   │   ├── qa.md                 # QA specialist agent
+│   │   ├── sm.md                 # Scrum master agent
+│   │   └── ux-expert.md          # UX designer agent
+│   ├── agent-teams/              # Pre-configured agent teams
+│   │   ├── team-all.yml          # All agents bundle
+│   │   ├── team-fullstack.yml    # Full-stack development team
+│   │   ├── team-ide-minimal.yml  # Minimal IDE-focused team
+│   │   └── team-no-ui.yml        # Backend-only team
+│   ├── checklists/               # Quality assurance checklists
+│   │   ├── architect-checklist.md
+│   │   ├── po-master-checklist.md
+│   │   └── story-dod-checklist.md
+│   ├── data/                     # Knowledge base and preferences
+│   │   ├── bmad-kb.md            # Core knowledge base
+│   │   └── technical-preferences.md  # User tech preferences
+│   ├── tasks/                    # Reusable task definitions
+│   │   ├── advanced-elicitation.md   # Deep diving techniques
+│   │   ├── create-doc.md         # Document creation task
+│   │   ├── create-next-story.md  # Story generation task
+│   │   ├── doc-migration-task.md # V3 to V4 migration
+│   │   ├── execute-checklist.md  # Checklist runner
+│   │   └── shard-doc.md          # Document sharding task
+│   ├── templates/                # Document templates
+│   │   ├── full-stack-architecture-tmpl.md
+│   │   ├── prd-tmpl.md
+│   │   ├── project-brief-tmpl.md
+│   │   ├── story-tmpl.md
+│   │   └── [other templates...]
+│   ├── utils/                    # Utility components
+│   │   ├── agent-switcher.web    # Web UI agent switching
+│   │   ├── template-format.md    # Template markup spec
+│   │   └── workflow-management.md # Workflow helpers
+│   ├── workflows/                # Development workflows
+│   │   ├── brownfield-enhancement.yml
+│   │   ├── greenfield-fullstack.yml
+│   │   ├── greenfield-service.yml
+│   │   └── greenfield-simple.yml
+│   └── core-config.yml           # V4 configuration system
+│
+├── dist/                         # Pre-built bundles (generated)
+│   ├── agents/                   # Individual agent bundles
+│   │   ├── analyst.txt
+│   │   ├── architect.txt
+│   │   └── [other agents...]
+│   ├── teams/                    # Team bundles for web UI
+│   │   ├── team-all.txt
+│   │   ├── team-fullstack.txt
+│   │   └── [other teams...]
+│   └── expansion-packs/          # Expansion pack bundles
+│
+├── docs/                         # Documentation
+│   ├── agentic-tools/           # IDE-specific guides
+│   │   ├── claude-code-guide.md
+│   │   ├── cursor-guide.md
+│   │   ├── cline-guide.md
+│   │   ├── gemini-cli-guide.md
+│   │   ├── roo-code-guide.md
+│   │   ├── windsurf-guide.md
+│   │   └── vs-code-copilot-guide.md
+│   ├── bmad-workflow-guide.md    # Universal workflow guide
+│   ├── core-architecture.md      # This document
+│   ├── expansion-packs.md        # Expansion pack guide
+│   ├── user-guide.md            # Comprehensive user guide
+│   └── [other docs...]
+│
+├── expansion-packs/              # Domain-specific extensions
+│   ├── bmad-2d-phaser-game-dev/ # Game development pack
+│   ├── bmad-creator-tools/      # Agent creation tools
+│   ├── bmad-infrastructure-devops/ # DevOps pack
+│   └── README.md
+│
+├── tools/                        # Build and installation tools
+│   ├── builders/                 # Build system
+│   │   └── web-builder.js       # Bundle generator
+│   ├── cli.js                   # Main CLI tool
+│   ├── installer/               # NPX installer
+│   │   ├── index.js             # Installer entry point
+│   │   ├── config/              # Installation configs
+│   │   ├── lib/                 # Installer utilities
+│   │   └── templates/           # IDE template files
+│   └── lib/                     # Shared libraries
+│       ├── bundle-utils.js
+│       ├── dependency-resolver.js
+│       └── file-processor.js
+│
+├── .github/                     # GitHub configuration
+│   ├── workflows/               # GitHub Actions
+│   └── ISSUE_TEMPLATE/         # Issue templates
+│
+├── common/                      # Shared resources
+│   ├── tasks/                   # Common tasks
+│   └── utils/                   # Common utilities
+│
+├── bmad-core/                   # Source for .bmad-core
+│   └── [mirrors .bmad-core structure]
+│
+├── package.json                 # Node.js configuration
+├── README.md                    # Project readme
+├── CONTRIBUTING.md              # Contribution guidelines
+├── GUIDING-PRINCIPLES.md        # Core principles
+└── LICENSE                      # MIT license
+```
+
+### Directory Purposes
+
+#### Core Framework (.bmad-core/)
+
+- **agents/**: Individual AI agent personalities and capabilities
+- **agent-teams/**: Bundles of agents for specific workflows
+- **checklists/**: Quality assurance and validation steps
+- **data/**: Knowledge base and user preferences
+- **tasks/**: Reusable procedures agents can execute
+- **templates/**: Document templates with embedded AI instructions
+- **utils/**: Helper components for agents
+- **workflows/**: Structured development processes
+
+#### Generated Bundles (dist/)
+
+- Pre-built text files ready for web UI upload
+- Automatically generated by the build system
+- Includes resolved dependencies for each agent/team
+
+#### Tools (tools/)
+
+- **cli.js**: Main build tool for creating bundles
+- **installer/**: NPX-based installer for projects
+- **builders/**: Bundle generation logic
+- **lib/**: Shared utilities for build system
+
+#### Expansion Packs (expansion-packs/)
+
+- Domain-specific agent collections
+- Extend BMAD beyond software development
+- Each pack is self-contained with its own agents, tasks, and templates
+
+#### Documentation (docs/)
+
+- Comprehensive guides for users
+- Technical architecture documentation
+- IDE-specific setup instructions
+
+### Key Files
+
+- **core-config.yml**: V4's flexible configuration system
+- **bmad-kb.md**: Central knowledge base loaded by most agents
+- **template-format.md**: Specification for BMAD's template markup
+- **dependency-resolver.js**: Manages agent resource loading

docs/cursor-guide.md

@@ -1,131 +0,0 @@
-# BMAD Method Guide for Cursor
-
-This guide walks you through the complete BMAD workflow using Cursor as your AI-powered IDE.
-
-## Step 1: Install BMAD in Your Project
-
-1. Navigate to your project directory
-2. Run the BMAD installer:
-
-   ```bash
-   npx bmad-method install
-   ```
-
-3. When prompted:
-   - **Installation Type**: Choose "Complete installation (recommended)"
-   - **IDE**: Select "Cursor"
-
-This creates a `.bmad-core` folder with all agents and a `.cursor/rules` folder with agent rules.
-
-## Step 2: Set Up Team Fullstack in Gemini
-
-For ideation and planning, use Google's Gemini Custom Gem with the team-fullstack configuration:
-
-1. Open [Google gems](https://gemini.google.com/gems/view)
-2. Create a new Gem - give it a title and description
-3. Copy the contents of `.<install location>/<web-bundles>/teams/team-fullstack.txt` (location can vary if you chose a non default installation location for the bundles) - or just use the bundle premade from the repo dist folder.
-4. Paste this content into Gemini to set up the team
-
-### Gemini Planning Phase
-
-In Gemini, ask the BMAD team to help you:
-
-- **Ideate** your project concept
-- **Brainstorm** features and requirements
-- **Create a PRD** (Product Requirements Document)
-- **Design the architecture**
-
-Ask questions like:
-
-- "Help me brainstorm a [type of application] that does [core functionality]"
-- "Create a comprehensive PRD for this concept"
-- "Design the technical architecture for this system"
-
-Copy the PRD and architecture documents that Gemini creates into your project's `docs/` folder:
-
-- `docs/prd.md`
-- `docs/architecture.md`
-
-## Step 3: Back to Cursor - Document Sharding
-
-Once you have your PRD and architecture documents in the `docs/` folder:
-
-1. **Start a new chat in Cursor**
-2. **Load the bmad-master agent**: Type `@bmad-master`
-3. **Shard the PRD**: Type `*shard-doc docs/prd.md prd`
-4. **Shard the architecture**: Type `*shard-doc docs/architecture.md architecture`
-
-This creates organized folders:
-
-- `docs/prd/` - Contains broken down PRD sections
-- `docs/architecture/` - Contains broken down architecture sections
-
-## Step 4: Story Development Cycle
-
-Now begin the iterative development cycle:
-
-### Create Stories (Scrum Master)
-
-1. **Start a new chat**
-2. **Load SM agent**: Type `@sm`
-3. **Create story**: Type `*create` (this runs the create-next-story task)
-4. **Review the generated story**
-5. **If approved**: Set story status to "Approved" in the story file
-
-### Implement Stories (Developer)
-
-1. **Start a new chat**
-2. **Load Dev agent**: Type `@dev`
-3. **The agent will ask which story to implement**
-4. **Follow the development tasks** the agent provides
-5. **When story is complete**: Mark status as "Done"
-
-### Repeat the Cycle
-
-1. **Start a new chat with SM agent** (`@sm`)
-2. **Create next story**: Type `*create`
-3. **Review and approve**
-4. **Start new chat with Dev agent** (`@dev`)
-5. **Implement the story**
-6. **Repeat until project complete**
-
-## Available Agent Rules in Cursor
-
-All BMAD agents are available as Cursor rules (use `@` prefix):
-
-- `@bmad-master` - Universal task executor
-- `@sm` - Scrum Master for story creation
-- `@dev` - Full-stack developer for implementation
-- `@architect` - Solution architect for design
-- `@pm` - Product manager for planning
-- `@analyst` - Business analyst for requirements
-- `@qa` - QA specialist for testing
-- `@po` - Product owner for prioritization
-- `@ux-expert` - UX specialist for design
-
-Alternatively, and more performance - you can copy the contents of an agent file into a custom mode - see the cursor docs on how to use custom agents.
-
-## Cursor-Specific Features
-
-- **Agent rules are stored in**: `.cursor/rules/` as `.mdc` files
-- **Auto-completion**: Cursor will suggest `@agent-name` as you type
-- **Rule activation**: Rules activate automatically when you mention `@agent-name`
-- **Context awareness**: Agents have access to your current file context
-
-## Key Workflow Principles
-
-1. **Always start new chats** when switching agents to avoid context confusion
-2. **Use Gemini for initial planning** and ideation with the team-fullstack bundle
-3. **Use bmad-master for document management** (sharding, templates, etc.)
-4. **Follow the SM → Dev cycle** for consistent story development
-5. **Review and approve stories** before implementation begins
-
-## Tips for Success
-
-- **Keep chats focused**: Each chat should have one agent and one primary task
-- **Use \*help command**: Every agent supports `*help` to see available commands
-- **Review generated content**: Always review and approve stories before marking them ready
-- **Maintain status updates**: Keep story statuses current (Draft → Approved → InProgress → Done)
-- **Leverage Cursor's context**: Agents can see your current file selection for better assistance
-
-This workflow ensures systematic, AI-assisted development following agile principles with clear handoffs between planning, story creation, and implementation phases.

docs/expansion-pack-ideas.md

@@ -1,121 +0,0 @@
-# Expansion Pack Ideas
-
-The BMAD Method's natural language framework can be applied to any domain. Here are ideas to inspire your own expansion packs:
-
-## Health & Wellness Pack
-
-### Agents
-
-- **Fitness Coach** - Creates personalized workout plans
-- **Nutrition Advisor** - Designs meal plans and tracks nutrition
-- **Meditation Guide** - Leads mindfulness sessions
-- **Sleep Optimizer** - Improves sleep habits
-
-### Tasks
-
-- `create-workout-plan` - Generates weekly exercise routines
-- `analyze-nutrition` - Reviews dietary habits
-- `design-meditation` - Creates guided meditation scripts
-
-### Templates
-
-- `workout-plan-tmpl` - Structured exercise program
-- `meal-plan-tmpl` - Weekly nutrition guide
-- `wellness-journal-tmpl` - Progress tracking
-
-## Creative Writing Pack
-
-### Agents
-
-- **Story Architect** - Plots narratives and story structures
-- **Character Developer** - Creates deep, complex characters
-- **World Builder** - Designs fictional universes
-- **Dialog Master** - Crafts authentic conversations
-
-### Tasks
-
-- `develop-plot` - Creates story outlines
-- `build-character` - Develops character profiles
-- `create-world` - Designs settings and cultures
-
-### Templates
-
-- `story-outline-tmpl` - Three-act structure
-- `character-sheet-tmpl` - Detailed character profile
-- `world-bible-tmpl` - Universe documentation
-
-## Business Strategy Pack
-
-### Agents
-
-- **Strategy Consultant** - Develops business strategies
-- **Market Analyst** - Researches market opportunities
-- **Financial Advisor** - Creates financial projections
-- **Operations Expert** - Optimizes business processes
-
-### Tasks
-
-- `swot-analysis` - Conducts SWOT analysis
-- `market-research` - Analyzes market conditions
-- `financial-forecast` - Projects revenue/costs
-
-### Templates
-
-- `business-plan-tmpl` - Complete business plan
-- `market-analysis-tmpl` - Market research report
-- `pitch-deck-tmpl` - Investor presentation
-
-## Education Pack
-
-### Agents
-
-- **Curriculum Designer** - Creates learning pathways
-- **Lesson Planner** - Develops engaging lessons
-- **Assessment Creator** - Designs fair evaluations
-- **Learning Coach** - Provides personalized guidance
-
-### Tasks
-
-- `design-curriculum` - Creates course structure
-- `plan-lesson` - Develops lesson content
-- `create-assessment` - Builds tests/quizzes
-
-### Templates
-
-- `course-outline-tmpl` - Semester plan
-- `lesson-plan-tmpl` - Daily lesson structure
-- `rubric-tmpl` - Assessment criteria
-
-## Personal Development Pack
-
-### Agents
-
-- **Life Coach** - Guides personal growth
-- **Goal Strategist** - Helps achieve objectives
-- **Habit Builder** - Creates lasting habits
-- **Mindset Mentor** - Develops positive thinking
-
-### Tasks
-
-- `goal-setting` - Defines SMART goals
-- `habit-tracking` - Monitors habit formation
-- `reflection-exercise` - Facilitates self-reflection
-
-### Templates
-
-- `goal-plan-tmpl` - Goal achievement roadmap
-- `habit-tracker-tmpl` - Daily habit log
-- `journal-prompts-tmpl` - Reflection questions
-
-## Creating Your Own
-
-To create an expansion pack:
-
-1. **Identify the domain** - What area of expertise?
-2. **Define agent roles** - Who are the experts?
-3. **Create tasks** - What procedures do they follow?
-4. **Design templates** - What outputs do they produce?
-5. **Test with users** - Does it provide value?
-6. **Share with community** - Help others benefit!
-
-Remember: The BMAD Method works anywhere natural language instructions can guide AI assistance!

docs/expansion-packs.md

@@ -132,6 +132,21 @@ Property investment and management:
 - **Flip Strategist**: Renovation ROI, project planning
 - **Agent Assistant**: Listing optimization, showing prep
 
+### Personal Development Pack
+
+Complete personal growth system:
+
+- **Life Coach**: Guides personal growth and transformation
+- **Goal Strategist**: Helps achieve objectives with SMART goals
+- **Habit Builder**: Creates lasting habits with accountability
+- **Mindset Mentor**: Develops positive thinking patterns
+
+Key tasks include:
+
+- `goal-setting`: Defines SMART goals with action plans
+- `habit-tracking`: Monitors habit formation progress
+- `reflection-exercise`: Facilitates deep self-reflection
+
 ## Unique & Innovative Packs
 
 ### Role-Playing Game Master Pack

docs/how-to-contribute-with-pull-requests.md

@@ -8,7 +8,15 @@ A pull request (PR) is how you propose changes to a project on GitHub. Think of
 
 ## Before You Start
 
-⚠️ **Important**: Please keep your contributions small and focused! We prefer many small, clear changes rather than one massive change. If you're planning something big, please [open an issue](https://github.com/bmadcode/bmad-method/issues) or start a [discussion](https://github.com/bmadcode/bmad-method/discussions) first.
+⚠️ **Important**: Please keep your contributions small and focused! We prefer many small, clear changes rather than one massive change.
+
+**Required before submitting PRs:**
+
+- **For bug fixes**: Create an issue using the [bug report template](https://github.com/bmadcode/bmad-method/issues/new?template=bug_report.md)
+- **For new features**:
+  1. Discuss in Discord [#general-dev channel](https://discord.gg/g6ypHytrCB)
+  2. Create an issue using the [feature request template](https://github.com/bmadcode/bmad-method/issues/new?template=feature_request.md)
+- **For large changes**: Always open an issue first to discuss alignment
 
 ## Step-by-Step Guide
 
@@ -82,9 +90,15 @@ git push origin fix/typo-in-readme
 
 1. Go to your fork on GitHub
 2. You'll see a green "Compare & pull request" button - click it
-3. Fill out the PR template:
-   - **Title**: Clear, descriptive title
-   - **Description**: Explain what you changed and why
+3. Select the correct target branch:
+   - **`next` branch** for most contributions (features, docs, enhancements)
+   - **`main` branch** only for critical fixes
+4. Fill out the PR description using the template in CONTRIBUTING.md:
+   - **What**: 1-2 sentences describing what changed
+   - **Why**: 1-2 sentences explaining why
+   - **How**: 2-3 bullets on implementation
+   - **Testing**: How you tested
+5. Reference the related issue number (e.g., "Fixes #123")
 
 ### 8. Wait for Review
 
@@ -117,9 +131,12 @@ git push origin fix/typo-in-readme
 
 ## Need Help?
 
-- 💬 Join our [Discord Community](https://discord.gg/g6ypHytrCB) for real-time help
-- 💬 Ask questions in [Discussions](https://github.com/bmadcode/bmad-method/discussions)
-- 🐛 Report bugs in [Issues](https://github.com/bmadcode/bmad-method/issues)
+- 💬 Join our [Discord Community](https://discord.gg/g6ypHytrCB) for real-time help:
+  - **#general-dev** - Technical questions and feature discussions
+  - **#bugs-issues** - Get help with bugs before filing issues
+- 💬 Ask questions in [GitHub Discussions](https://github.com/bmadcode/bmad-method/discussions)
+- 🐛 Report bugs using the [bug report template](https://github.com/bmadcode/bmad-method/issues/new?template=bug_report.md)
+- 💡 Suggest features using the [feature request template](https://github.com/bmadcode/bmad-method/issues/new?template=feature_request.md)
 - 📖 Read the full [Contributing Guidelines](../CONTRIBUTING.md)
 
 ## Example: Good vs Bad PRs

docs/roo-code-guide.md

@@ -1,142 +0,0 @@
-# BMAD Method Guide for Roo Code
-
-This guide walks you through the complete BMAD workflow using Roo Code as your AI-powered IDE.
-
-## Step 1: Install BMAD in Your Project
-
-1. Navigate to your project directory
-2. Run the BMAD installer:
-
-   ```bash
-   npx bmad-method install
-   ```
-
-3. When prompted:
-   - **Installation Type**: Choose "Complete installation (recommended)"
-   - **IDE**: Select "Roo Code"
-
-This creates a `.bmad-core` folder with all agents and a `.roomodes` file (in the project root) with custom modes.
-
-## Step 2: Set Up Team Fullstack in Gemini
-
-For ideation and planning, use Google's Gemini Custom Gem with the team-fullstack configuration:
-
-1. Open [Google gems](https://gemini.google.com/gems/view)
-2. Create a new Gem - give it a title and description
-3. Copy the contents of `.<install location>/<web-bundles>/teams/team-fullstack.txt` (location can vary if you chose a non default installation location for the bundles) - or just use the bundle premade from the repo dist folder.
-4. Paste this content into Gemini to set up the team
-
-### Gemini Planning Phase
-
-In Gemini, ask the BMAD team to help you:
-
-- **Ideate** your project concept
-- **Brainstorm** features and requirements
-- **Create a PRD** (Product Requirements Document)
-- **Design the architecture**
-
-Ask questions like:
-
-- "Help me brainstorm a [type of application] that does [core functionality]"
-- "Create a comprehensive PRD for this concept"
-- "Design the technical architecture for this system"
-
-Copy the PRD and architecture documents that Gemini creates into your project's `docs/` folder:
-
-- `docs/prd.md`
-- `docs/architecture.md`
-
-## Step 3: Back to Roo Code - Document Sharding
-
-Once you have your PRD and architecture documents in the `docs/` folder:
-
-1. **Open your project in Roo Code**
-2. **Select the bmad-master mode** from the mode selector (usually in status bar)
-3. **Shard the PRD**: Type `*shard-doc docs/prd.md prd`
-4. **Shard the architecture**: Type `*shard-doc docs/architecture.md architecture`
-
-This creates organized folders:
-
-- `docs/prd/` - Contains broken down PRD sections
-- `docs/architecture/` - Contains broken down architecture sections
-
-## Step 4: Story Development Cycle
-
-Now begin the iterative development cycle:
-
-### Create Stories (Scrum Master)
-
-1. **Start a new chat or conversation**
-2. **Switch to SM mode**: Select `bmad-sm` from the mode selector
-3. **Create story**: Type `*create` (this runs the create-next-story task)
-4. **Review the generated story**
-5. **If approved**: Set story status to "Approved" in the story file
-
-### Implement Stories (Developer)
-
-1. **Start a new conversation**
-2. **Switch to Dev mode**: Select `bmad-dev` from the mode selector
-3. **The agent will ask which story to implement**
-4. **Follow the development tasks** the agent provides
-5. **When story is complete**: Mark status as "Done"
-
-### Repeat the Cycle
-
-1. **Switch to SM mode** (`bmad-sm`)
-2. **Create next story**: Type `*create`
-3. **Review and approve**
-4. **Switch to Dev mode** (`bmad-dev`)
-5. **Implement the story**
-6. **Repeat until project complete**
-
-## Available Custom Modes in Roo Code
-
-All BMAD agents are available as custom modes:
-
-- `bmad-bmad-master` - 🧙 Universal task executor
-- `bmad-sm` - 🏃 Scrum Master for story creation
-- `bmad-dev` - 💻 Full-stack developer for implementation
-- `bmad-architect` - 🏗️ Solution architect for design
-- `bmad-pm` - 📋 Product manager for planning
-- `bmad-analyst` - 📊 Business analyst for requirements
-- `bmad-qa` - 🧪 QA specialist for testing
-- `bmad-po` - 🎯 Product owner for prioritization
-- `bmad-ux-expert` - 🎨 UX specialist for design
-
-## Roo Code-Specific Features
-
-- **Custom modes are stored in**: `.roomodes` file (in the project root)
-- **Mode switching**: Use the mode selector in Roo Code's interface
-- **File permissions**: Each agent has specific file access permissions
-  - **Documentation agents** (SM, PM, PO, Analyst): Limited to `.md` and `.txt` files
-  - **Technical agents** (Dev, Architect, Master): Full file access
-  - **QA agents**: Access to test files and documentation
-  - **UX agents**: Access to design-related files
-- **Context preservation**: Modes maintain context within conversations
-
-## Key Workflow Principles
-
-1. **Switch modes instead of starting new chats** - Roo Code handles context better with mode switching
-2. **Use Gemini for initial planning** and ideation with the team-fullstack bundle
-3. **Use bmad-master mode for document management** (sharding, templates, etc.)
-4. **Follow the SM → Dev mode cycle** for consistent story development
-5. **Review and approve stories** before implementation begins
-
-## Tips for Success
-
-- **Use mode selector effectively**: Switch modes as needed for different tasks
-- **Respect file permissions**: Agents can only edit files they have permission for
-- **Use \*help command**: Every mode supports `*help` to see available commands
-- **Review generated content**: Always review and approve stories before marking them ready
-- **Maintain status updates**: Keep story statuses current (Draft → Approved → InProgress → Done)
-- **Leverage Roo's context**: Modes can maintain context across the conversation
-
-## File Permission Summary
-
-- **bmad-analyst, bmad-pm, bmad-po, bmad-sm**: `.md`, `.txt` files only
-- **bmad-architect**: `.md`, `.txt`, `.yml`, `.yaml`, `.json` files
-- **bmad-qa**: Test files (`.test.js`, `.spec.ts`, etc.) and `.md` files
-- **bmad-ux-expert**: `.md`, `.css`, `.scss`, `.html`, `.jsx`, `.tsx` files
-- **bmad-dev, bmad-bmad-master, bmad-orchestrator**: Full file access
-
-This workflow ensures systematic, AI-assisted development following agile principles with clear handoffs between planning, story creation, and implementation phases.

docs/user-guide.md

@@ -1,6 +1,6 @@
-# BMAD-METHOD User Guide
+# BMAD-METHOD Agentic Agile Driven Development User Guide
 
-This comprehensive guide will help you understand and effectively use the BMAD-METHOD framework for AI-assisted software development.
+This comprehensive guide will help you understand and effectively use the BMad Method framework for AI-assisted software development.
 
 ## Table of Contents
 
@@ -61,6 +61,19 @@ Best for: Cursor, Claude Code, Windsurf, VS Code users
 npx bmad-method install
 ```
 
+### CLI Commands
+
+```bash
+# List all available agents
+npx bmad-method list
+
+# Install or update (automatically detects existing installations)
+npx bmad-method install
+
+# Check installation status
+npx bmad-method status
+```
+
 ### First Steps
 
 1. **Choose Your Environment**: Web UI or IDE
@@ -68,20 +81,47 @@ npx bmad-method install
 3. **Initialize Project**: Run `/help` or `*help` to see capabilities
 4. **Start Development**: Begin with planning or jump into coding
 
+### Upgrading from V3 to V4
+
+If you have an existing BMAD-METHOD V3 project, simply run the installer in your project directory:
+
+```bash
+npx bmad-method install
+# The installer will automatically detect your V3 installation and offer to upgrade
+```
+
+The upgrade process will:
+
+1. Create a backup of your V3 files in `.bmad-v3-backup/`
+2. Install the new V4 `.bmad-core/` structure
+3. Migrate your documents (PRD, Architecture, Stories, Epics)
+4. Set up IDE integration for all V4 agents
+5. Create an install manifest for future updates
+
+After upgrading:
+
+1. Review your documents in the `docs/` folder - if you had a PRD or architecture in your old project, copy it from the backup to the docs folder if they are not there.
+2. Optionally run the `doc-migration-task` to align your documents with V4 templates - you can do this with your agent by saying something like: 'run {drag in task} against {drag prd or arch file from docs} to align with {drag the template from .bmad-core/templates/full-stack-architecture.md}'
+3. If you have separate front-end and backend architecture docs you can modify step 2 to merge both into a single full stack architecture or separate Front and Back end.
+
+The reason #2 and #3 are optional is because now BMAD V4 makes sharding optional for the SM. See [Core Configuration](#core-configuration-coreconfigyml)
+
+**Note**: The agents in `.bmad-core/` fully replace the items in `bmad-agent/` - you can remove the backup folder versions.
+
 ## Agent System
 
 ### Core Development Team
 
-| Agent       | Role               | Primary Functions                       | When to Use                            |
-| ----------- | ------------------ | --------------------------------------- | -------------------------------------- |
-| `analyst`   | Business Analyst   | Market research, requirements gathering | Project planning, competitive analysis |
-| `pm`        | Product Manager    | PRD creation, feature prioritization    | Strategic planning, roadmaps           |
-| `architect` | Solution Architect | System design, technical architecture   | Complex systems, scalability planning  |
-| `dev`       | Developer          | Code implementation, debugging          | All development tasks                  |
-| `qa`        | QA Specialist      | Test planning, quality assurance        | Testing strategies, bug validation     |
-| `ux-expert` | UX Designer        | UI/UX design, prototypes                | User experience, interface design      |
-| `po`        | Product Owner      | Backlog management, story validation    | Story refinement, acceptance criteria  |
-| `sm`        | Scrum Master       | Sprint planning, story creation         | Project management, workflow           |
+| Agent       | Role               | Primary Functions                              | When to Use                                       |
+| ----------- | ------------------ | ---------------------------------------------- | ------------------------------------------------- |
+| `analyst`   | Business Analyst   | Market research, requirements gathering        | Project planning, competitive analysis            |
+| `pm`        | Product Manager    | PRD creation, feature prioritization           | Strategic planning, roadmaps                      |
+| `architect` | Solution Architect | System design, technical architecture          | Complex systems, scalability planning             |
+| `dev`       | Developer          | Sequential task execution, testing, validation | Story implementation with test-driven development |
+| `qa`        | QA Specialist      | Code review, refactoring, test validation      | Senior developer review via `review-story` task   |
+| `ux-expert` | UX Designer        | UI/UX design, prototypes                       | User experience, interface design                 |
+| `po`        | Product Owner      | Backlog management, story validation           | Story refinement, acceptance criteria             |
+| `sm`        | Scrum Master       | Sprint planning, story creation                | Project management, workflow                      |
 
 ### Meta Agents
 
@@ -284,20 +324,29 @@ Once planning is complete and documents are sharded, BMAD follows a structured d
 
 ```mermaid
 graph TD
-    A["Start: Planning Artifacts Complete"] --> B["PO: Shard Epics"]
-    B --> C["PO: Shard Arch"]
-    C --> D["Development Phase"]
-    D --> E["Scrum Master: Drafts next story from sharded epic"]
-    E --> F{"User Approval"}
-    F -->|Approved| G["Dev: Implement Story"]
-    F -->|Needs Changes| E
-    G --> H["Dev: Complete story Tasks"]
-    H --> I{"User Verification"}
-    I -->|Verified Complete| J["Mark Story as Done"]
-    I -->|Needs Fixes| G
-    J --> E
+    A["Development Phase Start"] --> B["SM: Reviews Previous Story Dev/QA Notes"]
+    B --> B2["SM: Drafts Next Story from Sharded Epic + Architecture"]
+    B2 --> C{"User Approval"}
+    C -->|Approved| D["Dev: Sequential Task Execution"]
+    C -->|Needs Changes| B2
+    D --> E["Dev: Implement Tasks + Tests"]
+    E --> F["Dev: Run All Validations"]
+    F --> G["Dev: Mark Ready for Review + Add Notes"]
+    G --> H{"User Verification"}
+    H -->|Request QA Review| I["QA: Senior Dev Review + Active Refactoring"]
+    H -->|Approve Without QA| K["Mark Story as Done"]
+    I --> J["QA: Review, Refactor Code, Add Tests, Document Notes"]
+    J --> L{"QA Decision"}
+    L -->|Needs Dev Work| D
+    L -->|Approved| K
+    H -->|Needs Fixes| D
+    K --> B
 
-    style J fill:#34a853,color:#fff
+    style K fill:#34a853,color:#fff
+    style I fill:#f9ab00,color:#fff
+    style J fill:#ffd54f,color:#000
+    style E fill:#e3f2fd,color:#000
+    style B fill:#e8f5e9,color:#000
 ```
 
 ### Workflow Phases
@@ -319,15 +368,213 @@ graph TD
 
 - **SM**: Draft next story from sharded epic
 - **User**: Review and approve story
-- **Dev**: Implement all story tasks
+- **Dev**: Sequential task execution:
+  - Reads each task in the story
+  - Implements code for the task
+  - Writes tests alongside implementation
+  - Runs validations (linting, tests)
+  - Updates task checkbox [x] only if all validations pass
+  - Maintains Debug Log for temporary changes
+  - Updates File List with all created/modified files
+- **Dev**: After all tasks complete:
+  - Runs integration tests (if specified)
+  - Runs E2E tests (if specified)
+  - Validates Definition of Done checklist
+  - Marks story as "Ready for Review"
 - **User**: Verify implementation
+- **Optional QA Review**: User can request QA to run `review-story` task
 - **Repeat**: Until all stories complete
 
-#### 4. Quality Assurance
+#### Dev Agent Workflow Details
 
-- **QA**: Test planning and execution
-- **Dev**: Bug fixes and refinements
-- **PO**: Acceptance criteria validation
+The Dev agent follows a strict test-driven sequential workflow:
+
+**Key Behaviors:**
+
+- **Story-Centric**: Works only from the story file, never loads PRD/architecture unless specified in dev notes
+- **Sequential Execution**: Completes tasks one by one, marking [x] only after validations pass
+- **Test-Driven**: Writes tests alongside code for every task
+- **Quality Gates**: Never marks tasks complete if validations fail
+- **Debug Logging**: Tracks temporary changes in the story's Debug Log table
+- **File Tracking**: Maintains complete File List of all created/modified files
+
+**Blocking Conditions:**
+The Dev agent will stop and request help if:
+
+- Story is not approved
+- Requirements are ambiguous after checking the story
+- Validations fail 3 times for the same task
+- Critical configuration files are missing
+- Automated tests or linting fails
+
+#### 4. Quality Assurance Integration
+
+The QA agent plays a crucial role after development:
+
+- **When Dev marks "Ready for Review"**: Story is ready for user verification
+- **User Options**:
+  - **Direct Approval**: If satisfied, mark story as "Done"
+  - **Request Changes**: Send back to Dev with specific feedback
+  - **Request QA Review**: Ask QA to run the `review-story` task for senior developer review
+- **QA Review Process** (`/qa run review-story`):
+
+  - Reviews code as a senior developer with authority to refactor
+  - **Active Refactoring**: Makes improvements directly in the code
+  - **Comprehensive Review Focus**:
+    - Code architecture and design patterns
+    - Refactoring opportunities and code duplication
+    - Performance optimizations and security concerns
+    - Best practices and patterns
+  - **Standards Compliance**: Verifies adherence to:
+    - `docs/coding-standards.md`
+    - `docs/unified-project-structure.md`
+    - `docs/testing-strategy.md`
+  - **Test Coverage Review**: Can add missing tests if critical coverage is lacking
+  - **Documentation**: Adds comments for complex logic if missing
+  - **Results Documentation** in story's QA Results section:
+    - Code quality assessment
+    - Refactoring performed with WHY and HOW explanations
+    - Compliance check results
+    - Improvements checklist (completed vs. pending items)
+    - Security and performance findings
+    - Final approval status
+
+### Understanding the SM/Dev/QA Story Workflow
+
+The story file is the central artifact that enables seamless collaboration between the Scrum Master (SM), Developer (Dev), and Quality Assurance (QA) agents. Here's how they work together:
+
+#### Why We Have the Scrum Master
+
+The SM agent serves as a critical bridge between high-level planning and technical implementation:
+
+1. **Document Synthesis**: Reads sharded PRD epics and architecture documents to extract relevant technical details
+2. **Story Enrichment**: Creates self-contained stories with all technical context needed for implementation
+3. **Continuous Learning**: Uses notes from previous stories to improve future story preparation
+4. **Developer Efficiency**: Ensures developers have everything needed without searching multiple documents
+
+#### The Story Creation Process
+
+When the SM agent executes the `create-next-story` task:
+
+1. **Loads Configuration**: Reads `core-config.yml` to understand project structure
+2. **Identifies Next Story**: Sequentially processes stories from epics (1.1, 1.2, 2.1, etc.)
+3. **Gathers Architecture Context**: Reads relevant sharded architecture documents based on story type:
+
+   - Backend stories: data models, API specs, database schemas
+   - Frontend stories: component specs, UI patterns, workflows
+   - Full-stack: both backend and frontend documents
+
+4. **Reviews Previous Story**: Extracts Dev and QA notes to learn from past implementation
+
+#### The Story Template Structure
+
+The story template contains embedded LLM instructions for different agents:
+
+**SM Agent Instructions**:
+
+- Populate Dev Notes with specific technical details from architecture
+- Include source references for all technical guidance
+- Create detailed tasks based on architecture constraints
+- Add testing requirements from testing strategy
+
+**Dev Agent Instructions**:
+
+- Update Debug Log References during implementation
+- Document any deviations in Completion Notes
+- Maintain comprehensive File List of all changes
+- Track requirement changes in Change Log
+
+**QA Agent Instructions**:
+
+- Append review results in QA Results section
+- Document refactoring performed with explanations
+- Note security and performance considerations
+
+#### How Agents Pass Information
+
+##### SM → Dev Flow
+
+The SM prepares the story with:
+
+- **Dev Notes**: Specific technical guidance extracted from architecture
+- **Testing Requirements**: Unit, integration, and E2E test specifications
+- **Tasks/Subtasks**: Detailed implementation steps with AC mappings
+
+##### Dev → SM Flow
+
+The Dev agent provides feedback through:
+
+- **Completion Notes**: Deviations or discoveries that impact future stories
+- **Debug Log References**: Technical challenges and solutions
+- **File List**: Complete inventory of created/modified files
+- **Change Log**: Any requirement modifications during development
+
+##### QA → SM Flow
+
+The QA agent contributes:
+
+- **Code Quality Assessment**: Senior developer perspective on implementation quality
+- **Refactoring Performed**: Direct code improvements with:
+  - What was changed
+  - Why the change was made
+  - How it improves the code
+- **Compliance Results**: Verification against coding standards, project structure, and testing strategy
+- **Test Coverage**: Added tests for critical missing coverage
+- **Security Review**: Any security concerns found and whether addressed
+- **Performance Considerations**: Performance issues found and optimizations made
+- **Improvements Checklist**: Items completed (marked [x]) vs. items for Dev to address (marked [ ])
+- **Learning Opportunities**: Explanations for junior/mid-level developer growth
+
+#### Example: How Notes Flow Between Stories
+
+**Story 1.1 Completion**:
+
+```markdown
+### Completion Notes List
+
+- Discovered that user authentication requires additional session management not specified in architecture
+- Created new SessionManager service in services/auth/session-manager.ts
+- Recommend updating architecture to include session management patterns
+```
+
+**Story 1.2 Creation** (SM uses the above notes):
+
+```markdown
+## Dev Notes
+
+### Previous Story Insights
+
+- Story 1.1 created SessionManager service for auth (services/auth/session-manager.ts)
+- Consider using SessionManager for this story's user profile feature
+- Architecture update pending for session management patterns
+```
+
+This continuous feedback loop ensures each story benefits from lessons learned in previous implementations.
+
+#### QA Agent Key Principles
+
+When the QA agent performs the review-story task:
+
+- **Senior Developer Authority**: Reviews as a senior developer with authority to refactor directly
+- **Active Improvement**: Makes code improvements rather than just identifying issues
+- **Teaching Focus**: Explains all changes for developer learning and growth
+- **Pragmatic Balance**: Focuses on significant improvements, not nitpicks
+- **Quality Gates**: Can block story completion if critical issues exist
+
+**QA Blocking Conditions**:
+The QA will stop and request clarification if:
+
+- Story file is incomplete or missing critical sections
+- File List is empty or clearly incomplete
+- No tests exist when they were required
+- Code changes don't align with story requirements
+- Critical architectural issues require discussion
+
+- **Benefits of QA Review**:
+  - Code quality improvements and refactoring
+  - Knowledge transfer through documented explanations
+  - Catching edge cases and security issues
+  - Ensuring architectural consistency
 
 ### Workflow Types
 
@@ -528,7 +775,7 @@ Web UI agents focus on planning and documentation. Here's how to interact with e
 
 ### Dynamic Resource Loading
 
-BMAD's dependency system ensures agents only load necessary resources:
+BMad's dependency system ensures agents only load necessary resources:
 
 - **Templates**: Only relevant document templates
 - **Tasks**: Only required automation tasks
@@ -595,7 +842,7 @@ phases:
 
 Templates are self-contained documents that embed both output structure and processing instructions. Follow these patterns from existing templates:
 
-#### Template Structure
+#### Template Structure Example
 
 ```markdown
 # {{Project Name}} Document Title
@@ -1135,7 +1382,7 @@ Add specialized capabilities:
 - **Data Pack**: Analytics, ML integration
 - **Security Pack**: Security analysis, compliance
 
-## Troubleshooting
+## Troubleshooting Guide
 
 ### Common Issues
 
@@ -1178,7 +1425,7 @@ Add specialized capabilities:
 - **Documentation**: [Browse docs](https://github.com/bmadcode/bmad-method/tree/main/docs)
 - **YouTube**: [BMadCode Channel](https://www.youtube.com/@BMadCode)
 
-## Best Practices
+## Best Practices and Tips
 
 ### Project Organization
 
@@ -1201,7 +1448,7 @@ project/
 - Version control all BMAD-generated content
 - Regular backups of `.bmad-core/` customizations
 
-### Development Workflow
+### Recommended Development Flow
 
 #### Planning Phase
 

docs/versioning-and-releases.md

@@ -2,7 +2,7 @@
 
 ## Automated Releases (Recommended)
 
-The easiest way to release new versions is through **automatic semantic releases**. Just commit with the right message format and push - everything else happens automatically!
+The easiest way to release new versions is through **automatic semantic releases**. Just commit with the right message format and push and everything else happens automatically.
 
 ### Commit Message Format
 
@@ -58,7 +58,7 @@ npm run release:test    # Safe to run locally - tests the config
 
 ## Manual Release Methods (Exceptions Only)
 
-**⚠️ Only use these methods if you need to bypass the automatic system**
+⚠️ Only use these methods if you need to bypass the automatic system
 
 ### Quick Manual Version Bump
 
@@ -75,11 +75,3 @@ git push && git push --tags
 ### Manual GitHub Actions Trigger
 
 You can also trigger releases manually through GitHub Actions workflow dispatch if needed.
-
----
-
-## Summary
-
-**For 99% of releases**: Just use `fix:` or `feat:` commit messages and push. Everything else is automatic!
-
-**Manual methods**: Only needed for special cases or if you want to bypass the automated system.

docs/versions.md

@@ -16,7 +16,6 @@ Guiding Principles of V4:
 - Helpers for installers and web builders that will work with any OS and IDE easily
 - Align all agents to be the same for IDE and Web, without losing the power of the web versions, or the leanness of the files in the IDE to reduce context
 - Further improvements to the two most important agents - the SM and DEV
-- Expansion Packs - Coming soon...
 
 ## V3
 

docs/windsurf-guide.md

@@ -1,129 +0,0 @@
-# BMAD Method Guide for Windsurf
-
-This guide walks you through the complete BMAD workflow using Windsurf as your AI-powered IDE.
-
-## Step 1: Install BMAD in Your Project
-
-1. Navigate to your project directory
-2. Run the BMAD installer:
-
-   ```bash
-   npx bmad-method install
-   ```
-
-3. When prompted:
-   - **Installation Type**: Choose "Complete installation (recommended)"
-   - **IDE**: Select "Windsurf"
-
-This creates a `.bmad-core` folder with all agents and a `.windsurf/rules` folder with agent rules.
-
-## Step 2: Set Up Team Fullstack in Gemini
-
-For ideation and planning, use Google's Gemini Custom Gem with the team-fullstack configuration:
-
-1. Open [Google gems](https://gemini.google.com/gems/view)
-2. Create a new Gem - give it a title and description
-3. Copy the contents of `.<install location>/<web-bundles>/teams/team-fullstack.txt` (location can vary if you chose a non default installation location for the bundles) - or just use the bundle premade from the repo dist folder.
-4. Paste this content into Gemini to set up the team
-
-### Gemini Planning Phase
-
-In Gemini, ask the BMAD team to help you:
-
-- **Ideate** your project concept
-- **Brainstorm** features and requirements
-- **Create a PRD** (Product Requirements Document)
-- **Design the architecture**
-
-Ask questions like:
-
-- "Help me brainstorm a [type of application] that does [core functionality]"
-- "Create a comprehensive PRD for this concept"
-- "Design the technical architecture for this system"
-
-Copy the PRD and architecture documents that Gemini creates into your project's `docs/` folder:
-
-- `docs/prd.md`
-- `docs/architecture.md`
-
-## Step 3: Back to Windsurf - Document Sharding
-
-Once you have your PRD and architecture documents in the `docs/` folder:
-
-1. **Start a new chat in Windsurf**
-2. **Load the bmad-master agent**: Type `@bmad-master`
-3. **Shard the PRD**: Type `*shard-doc docs/prd.md prd`
-4. **Shard the architecture**: Type `*shard-doc docs/architecture.md architecture`
-
-This creates organized folders:
-
-- `docs/prd/` - Contains broken down PRD sections
-- `docs/architecture/` - Contains broken down architecture sections
-
-## Step 4: Story Development Cycle
-
-Now begin the iterative development cycle:
-
-### Create Stories (Scrum Master)
-
-1. **Start a new chat**
-2. **Load SM agent**: Type `@sm`
-3. **Create story**: Type `*create` (this runs the create-next-story task)
-4. **Review the generated story**
-5. **If approved**: Set story status to "Approved" in the story file
-
-### Implement Stories (Developer)
-
-1. **Start a new chat**
-2. **Load Dev agent**: Type `@dev`
-3. **The agent will ask which story to implement**
-4. **Follow the development tasks** the agent provides
-5. **When story is complete**: Mark status as "Done"
-
-### Repeat the Cycle
-
-1. **Start a new chat with SM agent** (`@sm`)
-2. **Create next story**: Type `*create`
-3. **Review and approve**
-4. **Start new chat with Dev agent** (`@dev`)
-5. **Implement the story**
-6. **Repeat until project complete**
-
-## Available Agent Rules in Windsurf
-
-All BMAD agents are available as Windsurf rules (use `@` prefix):
-
-- `@bmad-master` - Universal task executor
-- `@sm` - Scrum Master for story creation
-- `@dev` - Full-stack developer for implementation
-- `@architect` - Solution architect for design
-- `@pm` - Product manager for planning
-- `@analyst` - Business analyst for requirements
-- `@qa` - QA specialist for testing
-- `@po` - Product owner for prioritization
-- `@ux-expert` - UX specialist for design
-
-## Windsurf-Specific Features
-
-- **Agent rules are stored in**: `.windsurf/rules/` as `.md` files
-- **Rule activation**: Rules activate when you mention `@agent-name` in chat
-- **Collaborative workflow**: Windsurf's collaborative features work well with BMAD's agent-switching pattern
-- **Context awareness**: Agents have access to your project context
-
-## Key Workflow Principles
-
-1. **Always start new chats** when switching agents to avoid context confusion
-2. **Use Gemini for initial planning** and ideation with the team-fullstack bundle
-3. **Use bmad-master for document management** (sharding, templates, etc.)
-4. **Follow the SM → Dev cycle** for consistent story development
-5. **Review and approve stories** before implementation begins
-
-## Tips for Success
-
-- **Keep chats focused**: Each chat should have one agent and one primary task
-- **Use \*help command**: Every agent supports `*help` to see available commands
-- **Review generated content**: Always review and approve stories before marking them ready
-- **Maintain status updates**: Keep story statuses current (Draft → Approved → InProgress → Done)
-- **Leverage Windsurf's collaboration**: Use the collaborative features for team reviews
-
-This workflow ensures systematic, AI-assisted development following agile principles with clear handoffs between planning, story creation, and implementation phases.

docs/working-in-the-brownfield.md

@@ -1,22 +1,18 @@
 # Working in the Brownfield: A Complete Guide
 
-> 🚀 **HIGHLY RECOMMENDED: Use Gemini Web for Brownfield Documentation!**
+> 🚀 **HIGHLY RECOMMENDED: Use Gemini Web or Gemini CLI for Brownfield Documentation!**
 >
-> Gemini Web's 1M+ token context window can analyze your ENTIRE codebase at once:
+> Gemini Web's 1M+ token context window or Gemini CLI (when its working) can analyze your ENTIRE codebase at once:
 >
 > - Upload via GitHub URL
 > - Upload up to 1000 files
 > - Upload zipped project
->
-> This is MUCH more cost-effective than IDE analysis which reads files one by one!
 
 ## What is Brownfield Development?
 
 Brownfield development refers to adding features, fixing bugs, or modernizing existing software projects. Unlike greenfield (new) projects, brownfield work requires understanding existing code, respecting constraints, and ensuring new changes integrate seamlessly without breaking existing functionality.
 
-## When to Use BMAD for Brownfield
-
-BMAD-METHOD excels at brownfield development when you need to:
+## When to Use BMad for Brownfield
 
 - Add significant new features to existing applications
 - Modernize legacy codebases
@@ -29,7 +25,7 @@ BMAD-METHOD excels at brownfield development when you need to:
 
 ### Choose Your Approach
 
-#### Approach A: PRD-First (Recommended for Large Codebases/Monorepos)
+#### Approach A: PRD-First (Recommended if adding very large and complex new features, single or multiple epics or massive changes)
 
 **Best for**: Large codebases, monorepos, or when you know exactly what you want to build
 
@@ -116,7 +112,7 @@ The analyst will generate comprehensive documentation of everything.
 
 #### Option A: Full Brownfield Workflow (Recommended for Major Changes)
 
-**1. Create Brownfield PRD**
+**1. Create Brownfield PRD**:
 
 ```bash
 @pm
@@ -143,7 +139,7 @@ The PM agent will:
 - "What are the critical constraints we must respect?"
 - "What is your timeline and team size?"
 
-**2. Create Brownfield Architecture**
+**2. Create Brownfield Architecture**:
 
 ```bash
 @architect

expansion-packs/bmad-2d-phaser-game-dev/config.yml

@@ -0,0 +1,7 @@
+name: bmad-2d-phaser-game-dev
+version: 1.2.0
+short-title: 2D game development with Phaser 3 & TypeScript
+description: >-
+  2D Game Development expansion pack for BMAD Method - Phaser 3 & TypeScript
+  focused
+author: Brian (BMad)

expansion-packs/bmad-2d-phaser-game-dev/manifest.yml

@@ -1,45 +0,0 @@
-name: bmad-2d-phaser-game-dev
-version: 1.0.0
-description: 2D Game Development expansion pack for BMAD Method - Phaser 3 & TypeScript focused
-author: BMAD Team
-files:
-  - source: agents/game-designer.md
-    destination: .bmad-core/agents/game-designer.md
-  - source: agents/game-developer.md
-    destination: .bmad-core/agents/game-developer.md
-  - source: agents/game-sm.md
-    destination: .bmad-core/agents/game-sm.md
-  - source: team-game-dev.yml
-    destination: .bmad-core/agent-teams/team-game-dev.yml
-  - source: templates/game-design-doc-tmpl.md
-    destination: .bmad-core/templates/game-design-doc-tmpl.md
-  - source: templates/game-architecture-tmpl.md
-    destination: .bmad-core/templates/game-architecture-tmpl.md
-  - source: templates/level-design-doc-tmpl.md
-    destination: .bmad-core/templates/level-design-doc-tmpl.md
-  - source: templates/game-story-tmpl.md
-    destination: .bmad-core/templates/game-story-tmpl.md
-  - source: templates/game-brief-tmpl.md
-    destination: .bmad-core/templates/game-brief-tmpl.md
-  - source: tasks/create-game-story.md
-    destination: .bmad-core/tasks/create-game-story.md
-  - source: tasks/game-design-brainstorming.md
-    destination: .bmad-core/tasks/game-design-brainstorming.md
-  - source: tasks/advanced-elicitation.md
-    destination: .bmad-core/tasks/advanced-elicitation.md
-  - source: checklists/game-story-dod-checklist.md
-    destination: .bmad-core/checklists/game-story-dod-checklist.md
-  - source: checklists/game-design-checklist.md
-    destination: .bmad-core/checklists/game-design-checklist.md
-  - source: data/bmad-kb.md
-    destination: .bmad-core/data/bmad-kb.md
-  - source: data/development-guidelines.md
-    destination: .bmad-core/data/development-guidelines.md
-  - source: workflows/game-dev-greenfield.yml
-    destination: .bmad-core/workflows/game-dev-greenfield.yml
-  - source: workflows/game-prototype.yml
-    destination: .bmad-core/workflows/game-prototype.yml
-dependencies:
-  - architect
-  - developer
-  - sm

expansion-packs/bmad-creator-tools/config.yml

@@ -0,0 +1,5 @@
+name: bmad-creator-tools
+version: 1.1.0
+short-title: Tools for creating BMAD framework components
+description: Tools for creating and extending BMAD framework components.
+author: Brian (BMad)

expansion-packs/bmad-creator-tools/tasks/generate-expansion-pack.md

@@ -436,17 +436,17 @@ IMPORTANT: Work through plan.md checklist systematically!
 
 **Step 2: Copy Core Utilities**
 
-Before proceeding, copy these essential files from bmad-core:
+Before proceeding, copy these essential files from common:
 
 ```bash
 # Copy core task utilities
-cp bmad-core/tasks/create-doc.md expansion-packs/{pack-name}/tasks/
-cp bmad-core/tasks/execute-checklist.md expansion-packs/{pack-name}/tasks/
+cp common/tasks/create-doc.md expansion-packs/{pack-name}/tasks/
+cp common/tasks/execute-checklist.md expansion-packs/{pack-name}/tasks/
 
 # Copy core utility files
 mkdir -p expansion-packs/{pack-name}/utils
-cp bmad-core/utils/template-format.md expansion-packs/{pack-name}/utils/
-cp bmad-core/utils/workflow-management.md expansion-packs/{pack-name}/utils/
+cp common/utils/template-format.md expansion-packs/{pack-name}/utils/
+cp common/utils/workflow-management.md expansion-packs/{pack-name}/utils/
 ```
 
 **Step 3: Technical Implementation**

expansion-packs/bmad-infrastructure-devops/config.yml

@@ -0,0 +1,8 @@
+name: bmad-infrastructure-devops
+version: 1.1.0
+short-title: Infrastructure and DevOps capabilities
+description: >-
+  This expansion pack extends BMAD Method with comprehensive infrastructure and
+  DevOps capabilities. It's designed for teams that need to define, implement,
+  and manage cloud infrastructure alongside their application development.
+author: Brian (BMad)

expansion-packs/bmad-infrastructure-devops/manifest.yml

@@ -1,23 +0,0 @@
-name: bmad-infrastructure-devops
-version: 1.0.0
-description: Infrastructure & DevOps expansion pack for BMAD Method - Platform engineering and cloud infrastructure focused
-author: BMAD Team
-files:
-  - source: agents/infra-devops-platform.md
-    destination: .bmad-core/agents/infra-devops-platform.md
-  - source: templates/infrastructure-architecture-tmpl.md
-    destination: .bmad-core/templates/infrastructure-architecture-tmpl.md
-  - source: templates/infrastructure-platform-from-arch-tmpl.md
-    destination: .bmad-core/templates/infrastructure-platform-from-arch-tmpl.md
-  - source: tasks/create-doc.md
-    destination: .bmad-core/tasks/create-doc.md
-  - source: tasks/review-infrastructure.md
-    destination: .bmad-core/tasks/review-infrastructure.md
-  - source: tasks/validate-infrastructure.md
-    destination: .bmad-core/tasks/validate-infrastructure.md
-  - source: checklists/infrastructure-checklist.md
-    destination: .bmad-core/checklists/infrastructure-checklist.md
-dependencies:
-  - architect
-  - operations-specialist
-  - security-specialist

expansion-packs/bmad-infrastructure-devops/tasks/create-doc.md

@@ -1,74 +0,0 @@
-# Create Document from Template Task
-
-## Purpose
-
-- Generate documents from any specified template following embedded instructions from the perspective of the selected agent persona
-
-## Instructions
-
-### 1. Identify Template and Context
-
-- Determine which template to use (user-provided or list available for selection to user)
-
-  - Agent-specific templates are listed in the agent's dependencies under `templates`. For each template listed, consider it a document the agent can create. So if an agent has:
-
-    @{example}
-    dependencies:
-    templates: - prd-tmpl - architecture-tmpl
-    @{/example}
-
-    You would offer to create "PRD" and "Architecture" documents when the user asks what you can help with.
-
-- Gather all relevant inputs, or ask for them, or else rely on user providing necessary details to complete the document
-- Understand the document purpose and target audience
-
-### 2. Determine Interaction Mode
-
-Confirm with the user their preferred interaction style:
-
-- **Incremental:** Work through chunks of the document.
-- **YOLO Mode:** Draft complete document making reasonable assumptions in one shot. (Can be entered also after starting incremental by just typing /yolo)
-
-### 3. Execute Template
-
-- Load specified template from `templates#*` or the /templates directory
-- Follow ALL embedded LLM instructions within the template
-- Process template markup according to `utils#template-format` conventions
-
-### 4. Template Processing Rules
-
-#### CRITICAL: Never display template markup, LLM instructions, or examples to users
-
-- Replace all {{placeholders}} with actual content
-- Execute all [[LLM: instructions]] internally
-- Process `<<REPEAT>>` sections as needed
-- Evaluate ^^CONDITION^^ blocks and include only if applicable
-- Use @{examples} for guidance but never output them
-
-### 5. Content Generation
-
-- **Incremental Mode**: Present each major section for review before proceeding
-- **YOLO Mode**: Generate all sections, then review complete document with user
-- Apply any elicitation protocols specified in template
-- Incorporate user feedback and iterate as needed
-
-### 6. Validation
-
-If template specifies a checklist:
-
-- Run the appropriate checklist against completed document
-- Document completion status for each item
-- Address any deficiencies found
-- Present validation summary to user
-
-### 7. Final Presentation
-
-- Present clean, formatted content only
-- Ensure all sections are complete
-- DO NOT truncate or summarize content
-- Begin directly with document content (no preamble)
-- Include any handoff prompts specified in template
-
-## Important Notes
-
-- Template markup is for AI processing only - never expose to users

expansion-packs/expansion-creator/common-tasks/create-doc.md

@@ -1,74 +0,0 @@
-# Create Document from Template Task
-
-## Purpose
-
-- Generate documents from any specified template following embedded instructions from the perspective of the selected agent persona
-
-## Instructions
-
-### 1. Identify Template and Context
-
-- Determine which template to use (user-provided or list available for selection to user)
-
-  - Agent-specific templates are listed in the agent's dependencies under `templates`. For each template listed, consider it a document the agent can create. So if an agent has:
-
-    @{example}
-    dependencies:
-    templates: - prd-tmpl - architecture-tmpl
-    @{/example}
-
-    You would offer to create "PRD" and "Architecture" documents when the user asks what you can help with.
-
-- Gather all relevant inputs, or ask for them, or else rely on user providing necessary details to complete the document
-- Understand the document purpose and target audience
-
-### 2. Determine Interaction Mode
-
-Confirm with the user their preferred interaction style:
-
-- **Incremental:** Work through chunks of the document.
-- **YOLO Mode:** Draft complete document making reasonable assumptions in one shot. (Can be entered also after starting incremental by just typing /yolo)
-
-### 3. Execute Template
-
-- Load specified template from `templates#*` or the /templates directory
-- Follow ALL embedded LLM instructions within the template
-- Process template markup according to `utils#template-format` conventions
-
-### 4. Template Processing Rules
-
-#### CRITICAL: Never display template markup, LLM instructions, or examples to users
-
-- Replace all {{placeholders}} with actual content
-- Execute all [[LLM: instructions]] internally
-- Process `<<REPEAT>>` sections as needed
-- Evaluate ^^CONDITION^^ blocks and include only if applicable
-- Use @{examples} for guidance but never output them
-
-### 5. Content Generation
-
-- **Incremental Mode**: Present each major section for review before proceeding
-- **YOLO Mode**: Generate all sections, then review complete document with user
-- Apply any elicitation protocols specified in template
-- Incorporate user feedback and iterate as needed
-
-### 6. Validation
-
-If template specifies a checklist:
-
-- Run the appropriate checklist against completed document
-- Document completion status for each item
-- Address any deficiencies found
-- Present validation summary to user
-
-### 7. Final Presentation
-
-- Present clean, formatted content only
-- Ensure all sections are complete
-- DO NOT truncate or summarize content
-- Begin directly with document content (no preamble)
-- Include any handoff prompts specified in template
-
-## Important Notes
-
-- Template markup is for AI processing only - never expose to users

expansion-packs/expansion-creator/manifest.yml

@@ -1,12 +0,0 @@
-name: bmad-creator-tools
-version: 1.0.0
-description: Tools for creating and extending BMAD framework components
-type: creator-tools
-compatibility:
-  bmad-version: '>=4.0.0'
-components:
-  agents:
-    - bmad-the-creator
-  tasks:
-    - create-agent
-    - generate-expansion-pack

expansion-packs/expansion-creator/utils/template-format.md

@@ -1,26 +0,0 @@
-# Template Format Conventions
-
-Templates in the BMAD method use standardized markup for AI processing. These conventions ensure consistent document generation.
-
-## Template Markup Elements
-
-- **{{placeholders}}**: Variables to be replaced with actual content
-- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
-- **REPEAT** sections: Content blocks that may be repeated as needed
-- **^^CONDITION^^** blocks: Conditional content included only if criteria are met
-- **@{examples}**: Example content for guidance (never output to users)
-
-## Processing Rules
-
-- Replace all {{placeholders}} with project-specific content
-- Execute all [[LLM: instructions]] internally without showing users
-- Process conditional and repeat blocks as specified
-- Use examples for guidance but never include them in final output
-- Present only clean, formatted content to users
-
-## Critical Guidelines
-
-- **NEVER display template markup, LLM instructions, or examples to users**
-- Template elements are for AI processing only
-- Focus on faithful template execution and clean output
-- All template-specific instructions are embedded within templates

expansion-packs/expansion-creator/utils/workflow-management.md

@@ -1,223 +0,0 @@
-# Workflow Management
-
-This utility enables the BMAD orchestrator to manage and execute team workflows.
-
-## Important: Dynamic Workflow Loading
-
-The BMAD orchestrator MUST read the available workflows from the current team configuration's `workflows` field. Do not use hardcoded workflow lists. Each team bundle defines its own set of supported workflows based on the agents it includes.
-
-**Critical Distinction**:
-
-- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
-- Use `/agent-list` to show agents in the current bundle
-- Use `/workflows` to show workflows in the current bundle, NOT any creation tasks
-
-### Workflow Descriptions
-
-When displaying workflows, use these descriptions based on the workflow ID:
-
-- **greenfield-fullstack**: Build a new full-stack application from concept to development
-- **brownfield-fullstack**: Enhance an existing full-stack application with new features
-- **greenfield-service**: Build a new backend service or API from concept to development
-- **brownfield-service**: Enhance an existing backend service or API
-- **greenfield-ui**: Build a new frontend/UI application from concept to development
-- **brownfield-ui**: Enhance an existing frontend/UI application
-
-## Workflow Commands
-
-### /workflows
-
-Lists all available workflows for the current team. The available workflows are determined by the team configuration and may include workflows such as:
-
-- greenfield-fullstack
-- brownfield-fullstack
-- greenfield-service
-- brownfield-service
-- greenfield-ui
-- brownfield-ui
-
-The actual list depends on which team bundle is loaded. When responding to this command, display the workflows that are configured in the current team's `workflows` field.
-
-Example response format:
-
-```text
-Available workflows for [Team Name]:
-1. [workflow-id] - [Brief description based on workflow type]
-2. [workflow-id] - [Brief description based on workflow type]
-[... etc. ...]
-
-Use /workflow-start {number or id} to begin a workflow.
-```
-
-### /workflow-start {workflow-id}
-
-Starts a specific workflow and transitions to the first agent.
-
-Example: `/workflow-start greenfield-fullstack`
-
-### /workflow-status
-
-Shows current workflow progress, completed artifacts, and next steps.
-
-Example response:
-
-```text
-Current Workflow: Greenfield Full-Stack Development
-Stage: Product Planning (2 of 6)
-Completed:
-  ✓ Discovery & Requirements
-    - project-brief (completed by Mary)
-
-In Progress:
-  ⚡ Product Planning
-    - Create PRD (John) - awaiting input
-
-Next: Technical Architecture
-```
-
-### /workflow-resume
-
-Resumes a workflow from where it left off, useful when starting a new chat.
-
-User can provide completed artifacts:
-
-```text
-User: /workflow-resume greenfield-fullstack
-      I have completed: project-brief, PRD
-BMad: I see you've completed Discovery and part of Product Planning.
-      Based on the greenfield-fullstack workflow, the next step is:
-      - UX Strategy with Sally (ux-expert)
-
-      Would you like me to load Sally to continue?
-```
-
-### /workflow-next
-
-Shows the next recommended agent and action in the current workflow.
-
-## Workflow Execution Flow
-
-### 1. Starting a Workflow
-
-When a workflow is started:
-
-1. Load the workflow definition
-2. Identify the first stage and step
-3. Transition to the required agent
-4. Provide context about expected inputs/outputs
-5. Guide artifact creation
-
-### 2. Stage Transitions
-
-After each artifact is completed:
-
-1. Mark the step as complete
-2. Check transition conditions
-3. If stage is complete, move to next stage
-4. Load the appropriate agent
-5. Pass relevant artifacts as context
-
-### 3. Artifact Tracking
-
-Track all created artifacts:
-
-```yaml
-workflow_state:
-  current_workflow: greenfield-fullstack
-  current_stage: planning
-  current_step: 2
-  artifacts:
-    project-brief:
-      status: completed
-      created_by: analyst
-      timestamp: 2024-01-15T10:30:00.000Z
-    prd:
-      status: in-progress
-      created_by: pm
-      started: 2024-01-15T11:00:00.000Z
-```
-
-### 4. Workflow Interruption Handling
-
-When user returns after interruption:
-
-1. Ask if continuing previous workflow
-2. Request any completed artifacts
-3. Analyze provided artifacts
-4. Determine workflow position
-5. Suggest next appropriate step
-
-Example:
-
-```text
-User: I'm working on a new app. Here's my PRD and architecture doc.
-BMad: I see you have a PRD and architecture document. Based on these artifacts,
-      it looks like you're following the greenfield-fullstack workflow and have completed
-      stages 1-3. The next recommended step would be:
-
-      Stage 4: Validation & Refinement
-      - Load Sarah (Product Owner) to validate all artifacts
-
-      Would you like to continue with this workflow?
-```
-
-## Workflow Context Passing
-
-When transitioning between agents, pass:
-
-1. Previous artifacts created
-2. Current workflow stage
-3. Expected outputs
-4. Any decisions or constraints identified
-
-Example transition:
-
-```text
-BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
-      the next step is UX Strategy with Sally.
-
-      /ux-expert
-
-Sally: I see we're in the Product Planning stage of the greenfield-fullstack workflow.
-       I have access to:
-       - Project Brief from Mary
-       - PRD from John
-
-       Let's create the UX strategy and UI specifications. First, let me review
-       the PRD to understand the features we're designing for...
-```
-
-## Multi-Path Workflows
-
-Some workflows may have multiple paths:
-
-```yaml
-conditional_paths:
-  - condition: project_type == 'mobile'
-    next_stage: mobile-specific-design
-  - condition: project_type == 'web'
-    next_stage: web-architecture
-  - default: fullstack-architecture
-```
-
-Handle these by asking clarifying questions when needed.
-
-## Workflow Best Practices
-
-1. **Always show progress** - Users should know where they are
-2. **Explain transitions** - Why moving to next agent
-3. **Preserve context** - Pass relevant information forward
-4. **Allow flexibility** - Users can skip or modify steps
-5. **Track everything** - Maintain complete workflow state
-
-## Integration with Agents
-
-Each agent should be workflow-aware:
-
-- Know which workflow is active
-- Understand their role in the workflow
-- Access previous artifacts
-- Know expected outputs
-- Guide toward workflow goals
-
-This creates a seamless experience where the entire team works together toward the workflow's objectives.

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "bmad-method",
-  "version": "4.14.1",
+  "version": "4.24.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "bmad-method",
-      "version": "4.14.1",
+      "version": "4.24.0",
       "license": "MIT",
       "dependencies": {
         "@kayvan/markdown-tree-parser": "^1.5.0",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.14.1",
+  "version": "4.24.0",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "main": "tools/cli.js",
   "bin": {
@@ -18,6 +18,20 @@
     "version:patch": "node tools/version-bump.js patch",
     "version:minor": "node tools/version-bump.js minor",
     "version:major": "node tools/version-bump.js major",
+    "version:core": "node tools/bump-core-version.js",
+    "version:core:major": "node tools/bump-core-version.js major",
+    "version:core:minor": "node tools/bump-core-version.js minor",
+    "version:core:patch": "node tools/bump-core-version.js patch",
+    "version:expansion": "node tools/bump-expansion-version.js",
+    "version:expansion:set": "node tools/update-expansion-version.js",
+    "version:all": "node tools/bump-all-versions.js",
+    "version:all:minor": "node tools/bump-all-versions.js minor",
+    "version:all:major": "node tools/bump-all-versions.js major",
+    "version:all:patch": "node tools/bump-all-versions.js patch",
+    "version:expansion:all": "node tools/bump-all-versions.js",
+    "version:expansion:all:minor": "node tools/bump-all-versions.js minor",
+    "version:expansion:all:major": "node tools/bump-all-versions.js major",
+    "version:expansion:all:patch": "node tools/bump-all-versions.js patch",
     "release": "semantic-release",
     "release:test": "semantic-release --dry-run --no-ci || echo 'Config test complete - authentication errors are expected locally'",
     "prepare": "husky"

tools/builders/web-builder.js

@@ -9,8 +9,8 @@ class WebBuilder {
     this.resolver = new DependencyResolver(this.rootDir);
     this.templatePath = path.join(
       this.rootDir,
-      "bmad-core",
-      "utils",
+      "tools",
+      "md-assets",
       "web-agent-startup-instructions.md"
     );
   }
@@ -117,35 +117,39 @@ class WebBuilder {
     const yamlContent = yamlMatch[1];
     const yamlStartIndex = content.indexOf(yamlMatch[0]);
     const yamlEndIndex = yamlStartIndex + yamlMatch[0].length;
-    
+
     // Parse YAML and remove root and IDE-FILE-RESOLUTION properties
     try {
       const yaml = require("js-yaml");
       const parsed = yaml.load(yamlContent);
-      
+
       // Remove the properties if they exist at root level
       delete parsed.root;
-      delete parsed['IDE-FILE-RESOLUTION'];
-      delete parsed['REQUEST-RESOLUTION'];
-      
+      delete parsed["IDE-FILE-RESOLUTION"];
+      delete parsed["REQUEST-RESOLUTION"];
+
       // Also remove from activation-instructions if they exist
-      if (parsed['activation-instructions'] && Array.isArray(parsed['activation-instructions'])) {
-        parsed['activation-instructions'] = parsed['activation-instructions'].filter(instruction => {
-          return !instruction.startsWith('IDE-FILE-RESOLUTION:') && 
-                 !instruction.startsWith('REQUEST-RESOLUTION:');
-        });
+      if (parsed["activation-instructions"] && Array.isArray(parsed["activation-instructions"])) {
+        parsed["activation-instructions"] = parsed["activation-instructions"].filter(
+          (instruction) => {
+            return (
+              !instruction.startsWith("IDE-FILE-RESOLUTION:") &&
+              !instruction.startsWith("REQUEST-RESOLUTION:")
+            );
+          }
+        );
       }
-      
+
       // Reconstruct the YAML
       const cleanedYaml = yaml.dump(parsed, { lineWidth: -1 });
-      
+
       // Get the agent name from the YAML for the header
-      const agentName = parsed.agent?.id || 'agent';
-      
+      const agentName = parsed.agent?.id || "agent";
+
       // Build the new content with just the agent header and YAML
       const newHeader = `# ${agentName}\n\nCRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:\n\n`;
       const afterYaml = content.substring(yamlEndIndex);
-      
+
       return newHeader + "```yaml\n" + cleanedYaml.trim() + "\n```" + afterYaml;
     } catch (error) {
       console.warn("Failed to process agent YAML:", error.message);
@@ -156,12 +160,12 @@ class WebBuilder {
 
   formatSection(path, content) {
     const separator = "====================";
-    
+
     // Process agent content if this is an agent file
     if (path.startsWith("agents#")) {
       content = this.processAgentContent(content);
     }
-    
+
     return [
       `${separator} START: ${path} ${separator}`,
       content.trim(),
@@ -341,6 +345,28 @@ class WebBuilder {
                   }
                 }
 
+                // If not found in core, try common folder
+                if (!found) {
+                  for (const ext of extensions) {
+                    const commonPath = path.join(
+                      this.rootDir,
+                      "common",
+                      resourceType,
+                      `${resourceName}${ext}`
+                    );
+                    try {
+                      const commonContent = await fs.readFile(commonPath, "utf8");
+                      sections.push(
+                        this.formatSection(`${resourceType}#${resourceName}`, commonContent)
+                      );
+                      found = true;
+                      break;
+                    } catch (error) {
+                      // Not in common either, continue
+                    }
+                  }
+                }
+
                 if (!found) {
                   console.warn(
                     `    ⚠ Dependency ${resourceType}#${resourceName} not found in expansion pack or core`
@@ -516,6 +542,21 @@ class WebBuilder {
         }
       }
 
+      // If not found in core, try common folder
+      if (!found) {
+        for (const ext of extensions) {
+          const commonPath = path.join(this.rootDir, "common", dep.type, `${dep.name}${ext}`);
+          try {
+            const content = await fs.readFile(commonPath, "utf8");
+            sections.push(this.formatSection(key, content));
+            found = true;
+            break;
+          } catch (error) {
+            // Not in common either, continue
+          }
+        }
+      }
+
       if (!found) {
         console.warn(`    ⚠ Dependency ${key} not found in expansion pack or core`);
       }

tools/bump-all-versions.js

@@ -0,0 +1,107 @@
+#!/usr/bin/env node
+
+const fs = require('fs');
+const path = require('path');
+const yaml = require('js-yaml');
+
+const args = process.argv.slice(2);
+const bumpType = args[0] || 'minor'; // default to minor
+
+if (!['major', 'minor', 'patch'].includes(bumpType)) {
+  console.log('Usage: node bump-all-versions.js [major|minor|patch]');
+  console.log('Default: minor');
+  process.exit(1);
+}
+
+function bumpVersion(currentVersion, type) {
+  const [major, minor, patch] = currentVersion.split('.').map(Number);
+  
+  switch (type) {
+    case 'major':
+      return `${major + 1}.0.0`;
+    case 'minor':
+      return `${major}.${minor + 1}.0`;
+    case 'patch':
+      return `${major}.${minor}.${patch + 1}`;
+    default:
+      return currentVersion;
+  }
+}
+
+async function bumpAllVersions() {
+  const updatedItems = [];
+  
+  // First, bump the core version
+  const coreConfigPath = path.join(__dirname, '..', 'bmad-core', 'core-config.yml');
+  try {
+    const coreConfigContent = fs.readFileSync(coreConfigPath, 'utf8');
+    const coreConfig = yaml.load(coreConfigContent);
+    const oldCoreVersion = coreConfig.version || '1.0.0';
+    const newCoreVersion = bumpVersion(oldCoreVersion, bumpType);
+    
+    coreConfig.version = newCoreVersion;
+    
+    const updatedCoreYaml = yaml.dump(coreConfig, { indent: 2 });
+    fs.writeFileSync(coreConfigPath, updatedCoreYaml);
+    
+    updatedItems.push({ type: 'core', name: 'BMad Core', oldVersion: oldCoreVersion, newVersion: newCoreVersion });
+    console.log(`✓ BMad Core: ${oldCoreVersion} → ${newCoreVersion}`);
+  } catch (error) {
+    console.error(`✗ Failed to update BMad Core: ${error.message}`);
+  }
+  
+  // Then, bump all expansion packs
+  const expansionPacksDir = path.join(__dirname, '..', 'expansion-packs');
+  
+  try {
+    const entries = fs.readdirSync(expansionPacksDir, { withFileTypes: true });
+    
+    for (const entry of entries) {
+      if (entry.isDirectory() && !entry.name.startsWith('.') && entry.name !== 'README.md') {
+        const packId = entry.name;
+        const configPath = path.join(expansionPacksDir, packId, 'config.yml');
+        
+        if (fs.existsSync(configPath)) {
+          try {
+            const configContent = fs.readFileSync(configPath, 'utf8');
+            const config = yaml.load(configContent);
+            const oldVersion = config.version || '1.0.0';
+            const newVersion = bumpVersion(oldVersion, bumpType);
+            
+            config.version = newVersion;
+            
+            const updatedYaml = yaml.dump(config, { indent: 2 });
+            fs.writeFileSync(configPath, updatedYaml);
+            
+            updatedItems.push({ type: 'expansion', name: packId, oldVersion, newVersion });
+            console.log(`✓ ${packId}: ${oldVersion} → ${newVersion}`);
+            
+          } catch (error) {
+            console.error(`✗ Failed to update ${packId}: ${error.message}`);
+          }
+        }
+      }
+    }
+    
+    if (updatedItems.length > 0) {
+      const coreCount = updatedItems.filter(i => i.type === 'core').length;
+      const expansionCount = updatedItems.filter(i => i.type === 'expansion').length;
+      
+      console.log(`\n✓ Successfully bumped ${updatedItems.length} item(s) with ${bumpType} version bump`);
+      if (coreCount > 0) console.log(`  - ${coreCount} core`);
+      if (expansionCount > 0) console.log(`  - ${expansionCount} expansion pack(s)`);
+      
+      console.log('\nNext steps:');
+      console.log('1. Test the changes');
+      console.log('2. Commit: git add -A && git commit -m "chore: bump all versions (' + bumpType + ')"');
+    } else {
+      console.log('No items found to update');
+    }
+    
+  } catch (error) {
+    console.error('Error reading expansion packs directory:', error.message);
+    process.exit(1);
+  }
+}
+
+bumpAllVersions();

tools/bump-core-version.js

@@ -0,0 +1,57 @@
+#!/usr/bin/env node
+
+const fs = require('fs');
+const path = require('path');
+const yaml = require('js-yaml');
+
+const args = process.argv.slice(2);
+const bumpType = args[0] || 'minor'; // default to minor
+
+if (!['major', 'minor', 'patch'].includes(bumpType)) {
+  console.log('Usage: node bump-core-version.js [major|minor|patch]');
+  console.log('Default: minor');
+  process.exit(1);
+}
+
+function bumpVersion(currentVersion, type) {
+  const [major, minor, patch] = currentVersion.split('.').map(Number);
+  
+  switch (type) {
+    case 'major':
+      return `${major + 1}.0.0`;
+    case 'minor':
+      return `${major}.${minor + 1}.0`;
+    case 'patch':
+      return `${major}.${minor}.${patch + 1}`;
+    default:
+      return currentVersion;
+  }
+}
+
+async function bumpCoreVersion() {
+  try {
+    const coreConfigPath = path.join(__dirname, '..', 'bmad-core', 'core-config.yml');
+    
+    const coreConfigContent = fs.readFileSync(coreConfigPath, 'utf8');
+    const coreConfig = yaml.load(coreConfigContent);
+    const oldVersion = coreConfig.version || '1.0.0';
+    const newVersion = bumpVersion(oldVersion, bumpType);
+    
+    coreConfig.version = newVersion;
+    
+    const updatedYaml = yaml.dump(coreConfig, { indent: 2 });
+    fs.writeFileSync(coreConfigPath, updatedYaml);
+    
+    console.log(`✓ BMad Core: ${oldVersion} → ${newVersion}`);
+    console.log(`\n✓ Successfully bumped BMad Core with ${bumpType} version bump`);
+    console.log('\nNext steps:');
+    console.log('1. Test the changes');
+    console.log('2. Commit: git add -A && git commit -m "chore: bump core version (' + bumpType + ')"');
+    
+  } catch (error) {
+    console.error('Error updating core version:', error.message);
+    process.exit(1);
+  }
+}
+
+bumpCoreVersion();

tools/bump-expansion-version.js

@@ -0,0 +1,78 @@
+#!/usr/bin/env node
+
+const fs = require('fs');
+const path = require('path');
+const yaml = require('js-yaml');
+
+const args = process.argv.slice(2);
+
+if (args.length < 1 || args.length > 2) {
+  console.log('Usage: node bump-expansion-version.js <expansion-pack-id> [major|minor|patch]');
+  console.log('Default: minor');
+  console.log('Example: node bump-expansion-version.js bmad-creator-tools patch');
+  process.exit(1);
+}
+
+const packId = args[0];
+const bumpType = args[1] || 'minor'; // default to minor
+
+if (!['major', 'minor', 'patch'].includes(bumpType)) {
+  console.error('Error: Bump type must be major, minor, or patch');
+  process.exit(1);
+}
+
+function bumpVersion(currentVersion, type) {
+  const [major, minor, patch] = currentVersion.split('.').map(Number);
+  
+  switch (type) {
+    case 'major':
+      return `${major + 1}.0.0`;
+    case 'minor':
+      return `${major}.${minor + 1}.0`;
+    case 'patch':
+      return `${major}.${minor}.${patch + 1}`;
+    default:
+      return currentVersion;
+  }
+}
+
+async function updateVersion() {
+  try {
+    const configPath = path.join(__dirname, '..', 'expansion-packs', packId, 'config.yml');
+    
+    if (!fs.existsSync(configPath)) {
+      console.error(`Error: Expansion pack '${packId}' not found`);
+      console.log('\nAvailable expansion packs:');
+      const expansionPacksDir = path.join(__dirname, '..', 'expansion-packs');
+      const entries = fs.readdirSync(expansionPacksDir, { withFileTypes: true });
+      entries.forEach(entry => {
+        if (entry.isDirectory() && !entry.name.startsWith('.')) {
+          console.log(`  - ${entry.name}`);
+        }
+      });
+      process.exit(1);
+    }
+    
+    const configContent = fs.readFileSync(configPath, 'utf8');
+    const config = yaml.load(configContent);
+    const oldVersion = config.version || '1.0.0';
+    const newVersion = bumpVersion(oldVersion, bumpType);
+    
+    config.version = newVersion;
+    
+    const updatedYaml = yaml.dump(config, { indent: 2 });
+    fs.writeFileSync(configPath, updatedYaml);
+    
+    console.log(`✓ ${packId}: ${oldVersion} → ${newVersion}`);
+    console.log(`\n✓ Successfully bumped ${packId} with ${bumpType} version bump`);
+    console.log('\nNext steps:');
+    console.log('1. Test the changes');
+    console.log('2. Commit: git add -A && git commit -m "chore: bump ' + packId + ' version (' + bumpType + ')"');
+    
+  } catch (error) {
+    console.error('Error updating version:', error.message);
+    process.exit(1);
+  }
+}
+
+updateVersion();

tools/installer/bin/bmad.js

@@ -2,6 +2,8 @@
 
 const { program } = require('commander');
 const path = require('path');
+const fs = require('fs').promises;
+const yaml = require('js-yaml');
 
 // Dynamic imports for ES modules
 let chalk, inquirer;
@@ -40,22 +42,20 @@ try {
 
 program
   .version(version)
-  .description('BMAD Method installer - AI-powered Agile development framework');
+  .description('BMAD Method installer - Universal AI agent framework for any domain');
 
 program
   .command('install')
   .description('Install BMAD Method agents and tools')
-  .option('-f, --full', 'Install complete .bmad-core folder')
-  .option('-a, --agent <agent>', 'Install specific agent with dependencies')
-  .option('-t, --team <team>', 'Install specific team with required agents and dependencies')
+  .option('-f, --full', 'Install complete BMAD Method')
   .option('-x, --expansion-only', 'Install only expansion packs (no bmad-core)')
-  .option('-d, --directory <path>', 'Installation directory (default: .bmad-core)')
-  .option('-i, --ide <ide...>', 'Configure for specific IDE(s) - can specify multiple (cursor, claude-code, windsurf, roo, cline, other)')
+  .option('-d, --directory <path>', 'Installation directory')
+  .option('-i, --ide <ide...>', 'Configure for specific IDE(s) - can specify multiple (cursor, claude-code, windsurf, roo, cline, gemini, vs-code-copilot, other)')
   .option('-e, --expansion-packs <packs...>', 'Install specific expansion packs (can specify multiple)')
   .action(async (options) => {
     try {
       await initializeModules();
-      if (!options.full && !options.agent && !options.team && !options.expansionOnly) {
+      if (!options.full && !options.expansionOnly) {
         // Interactive mode
         const answers = await promptInstallation();
         if (!answers._alreadyInstalled) {
@@ -64,15 +64,11 @@ program
       } else {
         // Direct mode
         let installType = 'full';
-        if (options.agent) installType = 'single-agent';
-        else if (options.team) installType = 'team';
-        else if (options.expansionOnly) installType = 'expansion-only';
+        if (options.expansionOnly) installType = 'expansion-only';
 
         const config = {
           installType,
-          agent: options.agent,
-          team: options.team,
-          directory: options.directory || '.bmad-core',
+          directory: options.directory || '.',
           ides: (options.ide || []).filter(ide => ide !== 'other'),
           expansionPacks: options.expansionPacks || []
         };
@@ -100,19 +96,6 @@ program
     }
   });
 
-program
-  .command('list')
-  .description('List available agents')
-  .action(async () => {
-    try {
-      await installer.listAgents();
-    } catch (error) {
-      if (!chalk) await initializeModules();
-      console.error(chalk.red('Error:'), error.message);
-      process.exit(1);
-    }
-  });
-
 program
   .command('list:expansions')
   .description('List available expansion packs')
@@ -145,7 +128,7 @@ async function promptInstallation() {
 
   const answers = {};
 
-  // Ask for installation directory
+  // Ask for installation directory first
   const { directory } = await inquirer.prompt([
     {
       type: 'input',
@@ -161,147 +144,85 @@ async function promptInstallation() {
   ]);
   answers.directory = directory;
 
-  // Check if this is an existing v4 installation
-  const installDir = path.resolve(answers.directory);
+  // Detect existing installations
+  const installDir = path.resolve(directory);
   const state = await installer.detectInstallationState(installDir);
-
+  
+  // Check for existing expansion packs
+  const existingExpansionPacks = state.expansionPacks || {};
+  
+  // Get available expansion packs
+  const availableExpansionPacks = await installer.getAvailableExpansionPacks();
+  
+  // Build choices list
+  const choices = [];
+  
+  // Load core config to get short-title
+  const coreConfigPath = path.join(__dirname, '..', '..', '..', 'bmad-core', 'core-config.yml');
+  const coreConfig = yaml.load(await fs.readFile(coreConfigPath, 'utf8'));
+  const coreShortTitle = coreConfig['short-title'] || 'BMad Agile Core System';
+  
+  // Add BMAD core option
+  let bmadOptionText;
   if (state.type === 'v4_existing') {
-    console.log(chalk.yellow('\n🔍 Found existing BMAD v4 installation'));
-    console.log(`   Directory: ${installDir}`);
-    console.log(`   Version: ${state.manifest?.version || 'Unknown'}`);
-    console.log(`   Installed: ${state.manifest?.installed_at ? new Date(state.manifest.installed_at).toLocaleDateString() : 'Unknown'}`);
-
-    const { shouldUpdate } = await inquirer.prompt([
-      {
-        type: 'confirm',
-        name: 'shouldUpdate',
-        message: 'Would you like to update your existing BMAD v4 installation?',
-        default: true
-      }
-    ]);
-
-    if (shouldUpdate) {
-      // Skip other prompts and go directly to update
-      answers.installType = 'update';
-      answers._alreadyInstalled = true; // Flag to prevent double installation
-      await installer.install(answers);
-      return answers; // Return the answers object
-    }
-    // If user doesn't want to update, continue with normal flow
+    const currentVersion = state.manifest?.version || 'unknown';
+    const newVersion = coreConfig.version || 'unknown'; // Use version from core-config.yml
+    const versionInfo = currentVersion === newVersion 
+      ? `(v${currentVersion} - reinstall)`
+      : `(v${currentVersion} → v${newVersion})`;
+    bmadOptionText = `Update ${coreShortTitle} ${versionInfo} .bmad-core`;
+  } else {
+    bmadOptionText = `Install ${coreShortTitle} (v${coreConfig.version || version}) .bmad-core`;
   }
-
-  // Ask for installation type
-  const { installType } = await inquirer.prompt([
+  
+  choices.push({
+    name: bmadOptionText,
+    value: 'bmad-core',
+    checked: true
+  });
+  
+  // Add expansion pack options
+  for (const pack of availableExpansionPacks) {
+    const existing = existingExpansionPacks[pack.id];
+    let packOptionText;
+    
+    if (existing) {
+      const currentVersion = existing.manifest?.version || 'unknown';
+      const newVersion = pack.version;
+      const versionInfo = currentVersion === newVersion 
+        ? `(v${currentVersion} - reinstall)`
+        : `(v${currentVersion} → v${newVersion})`;
+      packOptionText = `Update ${pack.description} ${versionInfo} .${pack.id}`;
+    } else {
+      packOptionText = `Install ${pack.description} (v${pack.version}) .${pack.id}`;
+    }
+    
+    choices.push({
+      name: packOptionText,
+      value: pack.id,
+      checked: false
+    });
+  }
+  
+  // Ask what to install
+  const { selectedItems } = await inquirer.prompt([
     {
-      type: 'list',
-      name: 'installType',
-      message: 'How would you like to install BMAD?',
-      choices: [
-        {
-          name: 'Complete installation (recommended) - All agents and tools',
-          value: 'full'
-        },
-        {
-          name: 'Team installation - Install a specific team with required agents',
-          value: 'team'
-        },
-        {
-          name: 'Single agent - Choose one agent to install',
-          value: 'single-agent'
-        },
-        {
-          name: 'Expansion packs only - Install expansion packs without bmad-core',
-          value: 'expansion-only'
+      type: 'checkbox',
+      name: 'selectedItems',
+      message: 'Select what to install/update (use space to select, enter to continue):',
+      choices: choices,
+      validate: (selected) => {
+        if (selected.length === 0) {
+          return 'Please select at least one item to install';
         }
-      ]
+        return true;
+      }
     }
   ]);
-  answers.installType = installType;
-
-  // If single agent, ask which one
-  if (installType === 'single-agent') {
-    const agents = await installer.getAvailableAgents();
-    const { agent } = await inquirer.prompt([
-      {
-        type: 'list',
-        name: 'agent',
-        message: 'Select an agent to install:',
-        choices: agents.map(a => ({
-          name: `${a.id} - ${a.name} (${a.description})`,
-          value: a.id
-        }))
-      }
-    ]);
-    answers.agent = agent;
-  }
-
-  // If team installation, ask which team
-  if (installType === 'team') {
-    const teams = await installer.getAvailableTeams();
-    const { team } = await inquirer.prompt([
-      {
-        type: 'list',
-        name: 'team',
-        message: 'Select a team to install in your IDE project folder:',
-        choices: teams.map(t => ({
-          name: `${t.icon || '📋'} ${t.name}: ${t.description}`,
-          value: t.id
-        }))
-      }
-    ]);
-    answers.team = team;
-  }
-
-  // Ask for expansion pack selection
-  if (installType === 'full' || installType === 'team' || installType === 'expansion-only') {
-    try {
-      const availableExpansionPacks = await installer.getAvailableExpansionPacks();
-
-      if (availableExpansionPacks.length > 0) {
-        let choices;
-        let message;
-
-        if (installType === 'expansion-only') {
-          message = 'Select expansion packs to install (required):'
-          choices = availableExpansionPacks.map(pack => ({
-            name: `${pack.name} - ${pack.description}`,
-            value: pack.id
-          }));
-        } else {
-          message = 'Select expansion packs to install (press Enter to skip, or check any to install):';
-          choices = availableExpansionPacks.map(pack => ({
-            name: `${pack.name} - ${pack.description}`,
-            value: pack.id
-          }));
-        }
-
-        const { expansionPacks } = await inquirer.prompt([
-          {
-            type: 'checkbox',
-            name: 'expansionPacks',
-            message,
-            choices,
-            validate: installType === 'expansion-only' ? (answer) => {
-              if (answer.length < 1) {
-                return 'You must select at least one expansion pack for expansion-only installation.';
-              }
-              return true;
-            } : undefined
-          }
-        ]);
-
-        // Use selected expansion packs directly
-        answers.expansionPacks = expansionPacks;
-      } else {
-        answers.expansionPacks = [];
-      }
-    } catch (error) {
-      console.warn(chalk.yellow('Warning: Could not load expansion packs. Continuing without them.'));
-      answers.expansionPacks = [];
-    }
-  } else {
-    answers.expansionPacks = [];
-  }
+  
+  // Process selections
+  answers.installType = selectedItems.includes('bmad-core') ? 'full' : 'expansion-only';
+  answers.expansionPacks = selectedItems.filter(item => item !== 'bmad-core');
 
   // Ask for IDE configuration
   const { ides } = await inquirer.prompt([
@@ -314,7 +235,9 @@ async function promptInstallation() {
         { name: 'Claude Code', value: 'claude-code' },
         { name: 'Windsurf', value: 'windsurf' },
         { name: 'Roo Code', value: 'roo' },
-        { name: 'Cline', value: 'cline' }
+        { name: 'Cline', value: 'cline' },
+        { name: 'Gemini CLI', value: 'gemini' },
+        { name: 'VS Code Copilot', value: 'vs-code-copilot' }
       ]
     }
   ]);
@@ -328,7 +251,7 @@ async function promptInstallation() {
       type: 'confirm',
       name: 'includeWebBundles',
       message: 'Would you like to include pre-built web bundles? (standalone files for ChatGPT, Claude, Gemini)',
-      default: true
+      default: false
     }
   ]);
 

tools/installer/config/ide-agent-config.yml

@@ -0,0 +1,58 @@
+# IDE-specific agent configurations
+# This file defines agent-specific settings for different IDEs
+
+# Roo Code file permissions
+# Each agent can have restricted file access based on regex patterns
+# If an agent is not listed here, it gets full edit access
+roo-permissions:
+  # Core agents
+  analyst:
+    fileRegex: "\\.(md|txt)$"
+    description: "Documentation and text files"
+  pm:
+    fileRegex: "\\.(md|txt)$"
+    description: "Product documentation"
+  architect:
+    fileRegex: "\\.(md|txt|yml|yaml|json)$"
+    description: "Architecture docs and configs"
+  qa:
+    fileRegex: "\\.(test|spec)\\.(js|ts|jsx|tsx)$|\\.md$"
+    description: "Test files and documentation"
+  ux-expert:
+    fileRegex: "\\.(md|css|scss|html|jsx|tsx)$"
+    description: "Design-related files"
+  po:
+    fileRegex: "\\.(md|txt)$"
+    description: "Story and requirement docs"
+  sm:
+    fileRegex: "\\.(md|txt)$"
+    description: "Process and planning docs"
+  # Expansion pack agents
+  game-designer:
+    fileRegex: "\\.(md|txt|json|yaml|yml)$"
+    description: "Game design documents and configs"
+  game-sm:
+    fileRegex: "\\.(md|txt)$"
+    description: "Game project management docs"
+
+# Cline agent ordering
+# Lower numbers appear first in the list
+# Agents not listed get order 99
+cline-order:
+  # Core agents
+  bmad-master: 1
+  bmad-orchestrator: 2
+  pm: 3
+  analyst: 4
+  architect: 5
+  po: 6
+  sm: 7
+  dev: 8
+  qa: 9
+  ux-expert: 10
+  # Expansion pack agents
+  bmad-the-creator: 11
+  game-designer: 12
+  game-developer: 13
+  game-sm: 14
+  infra-devops-platform: 15