chore(release): 4.13.0 [skip ci]

# [4.13.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.12.0...v4.13.0) (2025-06-24)

### Features

* **ide-setup:** add support for Cline IDE and configuration rules ([#262](https://github.com/bmadcode/BMAD-METHOD/issues/262)) ([913dbec](913dbeced6))

CHANGELOG.md

@@ -1,3 +1,17 @@
+# [4.13.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.12.0...v4.13.0) (2025-06-24)
+
+
+### Features
+
+* **ide-setup:** add support for Cline IDE and configuration rules ([#262](https://github.com/bmadcode/BMAD-METHOD/issues/262)) ([913dbec](https://github.com/bmadcode/BMAD-METHOD/commit/913dbeced60ad65086df6233086d83a51ead81a9))
+
+# [4.12.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.11.0...v4.12.0) (2025-06-23)
+
+
+### Features
+
+* **dev-agent:** add quality gates to prevent task completion with failing validations ([#261](https://github.com/bmadcode/BMAD-METHOD/issues/261)) ([45110ff](https://github.com/bmadcode/BMAD-METHOD/commit/45110ffffe6d29cc08e227e22a901892185dfbd2))
+
 # [4.11.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.10.3...v4.11.0) (2025-06-21)
 
 

CONTRIBUTING.md

@@ -4,6 +4,8 @@ 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.
+
 Also note, we use the discussions feature in GitHub to have a community to discuss potential ideas, uses, additions and enhancements.
 
 ## Code of Conduct
@@ -26,6 +28,65 @@ By participating in this project, you agree to abide by our Code of Conduct. Ple
 
 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:
+
+- Keep dev agents lean - they need context for coding, not documentation
+- Web/planning agents can be larger with more complex tasks
+- Everything is natural language (markdown) - no code in core framework
+- Use expansion packs for domain-specific features
+
+#### Which Branch for Your PR?
+
+**Submit to `next` branch** (most contributions):
+
+- ✨ New features or agents
+- 🎨 Enhancements to existing features
+- 📚 Documentation updates
+- ♻️ Code refactoring
+- ⚡ Performance improvements
+- 🧪 New tests
+- 🎁 New expansion packs
+
+**Submit to `main` branch** (critical only):
+
+- 🚨 Critical bug fixes that break basic functionality
+- 🔒 Security patches
+- 📚 Fixing dangerously incorrect documentation
+- 🐛 Bugs preventing installation or basic usage
+
+**When in doubt, submit to `next`**. We'd rather test changes thoroughly before they hit stable.
+
+#### PR Size Guidelines
+
+- **Ideal PR size**: 200-400 lines of code changes
+- **Maximum PR size**: 800 lines (excluding generated files)
+- **One feature/fix per PR**: Each PR should address a single issue or add one feature
+- **If your change is larger**: Break it into multiple smaller PRs that can be reviewed independently
+- **Related changes**: Even related changes should be separate PRs if they deliver independent value
+
+#### Breaking Down Large PRs
+
+If your change exceeds 800 lines, use this checklist to split it:
+
+- [ ] Can I separate the refactoring from the feature implementation?
+- [ ] Can I introduce the new API/interface in one PR and implementation in another?
+- [ ] Can I split by file or module?
+- [ ] Can I create a base PR with shared utilities first?
+- [ ] Can I separate test additions from implementation?
+- [ ] Even if changes are related, can they deliver value independently?
+- [ ] Can these changes be merged in any order without breaking things?
+
+Example breakdown:
+
+1. PR #1: Add utility functions and types (100 lines)
+2. PR #2: Refactor existing code to use utilities (200 lines)
+3. PR #3: Implement new feature using refactored code (300 lines)
+4. PR #4: Add comprehensive tests (200 lines)
+
+**Note**: PRs #1 and #4 could be submitted simultaneously since they deliver independent value and don't depend on each other's merge order.
+
+#### Pull Request Steps
+
 1. Fork the repository
 2. Create a new branch (`git checkout -b feature/your-feature-name`)
 3. Make your changes
@@ -34,9 +95,75 @@ Please only propose small granular commits! If its large or significant, please
 6. Push to your branch (`git push origin feature/your-feature-name`)
 7. Open a Pull Request against the main branch
 
+## Pull Request Description Guidelines
+
+Keep PR descriptions short and to the point following this template:
+
+### PR Description Template
+
+Keep your PR description concise and focused. Use this template:
+
+```markdown
+## What
+
+[1-2 sentences describing WHAT changed]
+
+## Why
+
+[1-2 sentences explaining WHY this change is needed]
+
+## How
+
+[2-3 bullets listing HOW you implemented it]
+
+-
+-
+-
+
+## Testing
+
+[1-2 sentences on how you tested this]
+```
+
+**Maximum PR description length: 200 words** (excluding code examples if needed)
+
+### Good vs Bad PR Descriptions
+
+❌ **Bad Example:**
+
+> This revolutionary PR introduces a paradigm-shifting enhancement to the system's architecture by implementing a state-of-the-art solution that leverages cutting-edge methodologies to optimize performance metrics and deliver unprecedented value to stakeholders through innovative approaches...
+
+✅ **Good Example:**
+
+> **What:** Added validation for agent dependency resolution
+> **Why:** Build was failing silently when agents had circular dependencies
+> **How:**
+>
+> - Added cycle detection in dependency-resolver.js
+> - Throws clear error with dependency chain
+>   **Testing:** Tested with circular deps between 3 agents
+
 ## Commit Message Convention
 
-PRs with a wall of AI Generated marketing hype that is unclear in what is being proposed will be closed and rejected. Your best change to contribute is with a small clear PR description explaining, what is the issue being solved or gap in the system being filled. Also explain how it leads to the core guiding principles of the project.
+Use conventional commits format:
+
+- `feat:` New feature
+- `fix:` Bug fix
+- `docs:` Documentation only
+- `refactor:` Code change that neither fixes a bug nor adds a feature
+- `test:` Adding missing tests
+- `chore:` Changes to build process or auxiliary tools
+
+Keep commit messages under 72 characters.
+
+### Atomic Commits
+
+Each commit should represent one logical change:
+
+- **Do:** One bug fix per commit
+- **Do:** One feature addition per commit
+- **Don't:** Mix refactoring with bug fixes
+- **Don't:** Combine unrelated changes
 
 ## Code Style
 

GUIDING-PRINCIPLES.md

@@ -0,0 +1,118 @@
+# 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.
+
+## Core Principles
+
+### 1. Dev Agents Must Be Lean
+
+- **Minimize dev agent dependencies**: Development agents that work in IDEs must have minimal context overhead
+- **Save context for code**: Every line counts - dev agents should focus on coding, not documentation
+- **Web agents can be larger**: Planning agents (PRD Writer, Architect) used in web UI can have more complex tasks and dependencies
+- **Small files, loaded on demand**: Multiple small, focused files are better than large files with many branches
+
+### 2. Natural Language First
+
+- **Everything is markdown**: Agents, tasks, templates - all written in plain English
+- **No code in core**: The framework itself contains no programming code, only natural language instructions
+- **Self-contained templates**: Templates include their own generation instructions using `[[LLM: ...]]` markup
+
+### 3. Agent and Task Design
+
+- **Agents define roles**: Each agent is a persona with specific expertise (e.g., Frontend Developer, API Developer)
+- **Tasks are procedures**: Step-by-step instructions an agent follows to complete work
+- **Templates are outputs**: Structured documents with embedded instructions for generation
+- **Dependencies matter**: Explicitly declare only what's needed
+
+## Practical Guidelines
+
+### When to Add to Core
+
+- Universal software development needs only
+- Doesn't bloat dev agent contexts
+- Follows existing agent/task/template patterns
+
+### When to Create Expansion Packs
+
+- Domain-specific needs beyond software development
+- Non-technical domains (business, wellness, education, creative)
+- Specialized technical domains (games, infrastructure, mobile)
+- Heavy documentation or knowledge bases
+- Anything that would bloat core agents
+
+See [Expansion Packs Guide](../docs/expansion-packs.md) for detailed examples and ideas.
+
+### Agent Design Rules
+
+1. **Web/Planning Agents**: Can have richer context, multiple tasks, extensive templates
+2. **Dev Agents**: Minimal dependencies, focused on code generation, lean task sets
+3. **All Agents**: Clear persona, specific expertise, well-defined capabilities
+
+### Task Writing Rules
+
+1. Write clear step-by-step procedures
+2. Use markdown formatting for readability
+3. Keep dev agent tasks focused and concise
+4. Planning tasks can be more elaborate
+5. **Prefer multiple small tasks over one large branching task**
+   - Instead of one task with many conditional paths
+   - Create multiple focused tasks the agent can choose from
+   - This keeps context overhead minimal
+6. **Reuse common tasks** - Don't create new document creation tasks
+   - Use the existing `create-doc` task
+   - Pass the appropriate template with embedded LLM instructions
+   - This maintains consistency and reduces duplication
+
+### Template Rules
+
+1. Include generation instructions with `[[LLM: ...]]` markup
+2. Provide clear structure for output
+3. Make templates reusable across agents
+4. Use standardized markup elements:
+   - `{{placeholders}}` for variables to be replaced
+   - `[[LLM: instructions]]` for AI-only processing (never shown to users)
+   - `REPEAT` sections for repeatable content blocks
+   - `^^CONDITION^^` blocks for conditional content
+   - `@{examples}` for guidance examples (never output to users)
+5. NEVER display template markup or LLM instructions to users
+6. Focus on clean output - all processing instructions stay internal
+
+## Examples
+
+### Good Dev Agent
+
+```yaml
+name: API Developer
+role: Creates REST APIs
+dependencies:
+  templates:
+    - api-endpoint-tmpl
+  tasks:
+    - implement-endpoint
+```
+
+### Good Planning Agent (Web)
+
+```yaml
+name: PRD Writer
+role: Creates comprehensive PRDs
+dependencies:
+  templates:
+    - prd-tmpl
+    - epic-tmpl
+    - story-tmpl
+  tasks:
+    - elicit-requirements
+    - analyze-market
+    - define-features
+  data:
+    - prd-best-practices
+    - market-analysis-guide
+```
+
+## Remember
+
+- The power is in natural language orchestration, not code
+- Dev agents code, planning agents plan
+- Keep dev agents lean for maximum coding efficiency
+- Expansion packs handle specialized domains

README.md

@@ -241,7 +241,7 @@ tools/
 ├── installer/       # NPX installer
 └── lib/             # Build utilities
 
-expansion-packs/     # Optional add-ons (DevOps, Mobile, etc.)
+expansion-packs/     # Domain-specific add-ons (Technical & Non-Technical)
 
 dist/                # 📦 PRE-BUILT BUNDLES (Ready to use!)
 ├── agents/          # Individual agent bundles (.txt files)
@@ -289,12 +289,60 @@ Rich templates for all document types:
 
 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 welcome contributions!
+**We're excited about contributions and welcome your ideas, improvements, and expansion packs!** 🎉
 
-- 🆕 **New to GitHub?** Start with our [Pull Request Guide](docs/how-to-contribute-with-pull-requests.md)
-- See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed guidelines
+### 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
 
@@ -310,6 +358,7 @@ npm install
 
 - 🏗️ [Core Architecture](docs/core-architecture.md) - Complete technical architecture and system design
 - 📖 [User Guide](docs/user-guide.md) - Comprehensive guide to using BMAD-METHOD effectively
+- 🚀 [Expansion Packs Guide](docs/expansion-packs.md) - Extend BMAD to any domain beyond software development
 
 ### Workflow Guides
 

bmad-core/agents/dev.md

@@ -32,6 +32,7 @@ core_principles:
   - CRITICAL: Dev Record Only - ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
   - Strive for Sequential Task Execution - Complete tasks 1-by-1 and mark [x] as completed
   - Test-Driven Quality - Write tests alongside code. Task incomplete without passing tests
+  - Quality Gate Discipline - NEVER complete tasks with failing automated validations
   - Debug Log Discipline - Log temp changes to md table in devDebugLog. Revert after fix.
   - Block Only When Critical - HALT for: missing approval/ambiguous reqs/3 failures/missing config
   - Code Excellence - Clean, secure, maintainable code per loaded standards
@@ -45,15 +46,15 @@ commands:  # All commands require * prefix when used (e.g., *help)
   - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
 
 task-execution:
-  flow: "Read task→Implement→Write tests→Pass tests→Update [x]→Next task"
+  flow: "Read task→Implement→Write tests→Execute validations→Only if ALL pass→Update [x]→Next task"
   updates-ONLY:
     - "Checkboxes: [ ] not started | [-] in progress | [x] complete"
     - "Debug Log: | Task | File | Change | Reverted? |"
     - "Completion Notes: Deviations only, <50 words"
     - "Change Log: Requirement changes only"
-  blocking: "Unapproved deps | Ambiguous after story check | 3 failures | Missing config"
-  done: "Code matches reqs + Tests pass + Follows standards + No lint errors"
-  completion: "All [x]→Lint→Tests(100%)→Integration(if noted)→Coverage(80%+)→E2E(if noted)→DoD→Summary→HALT"
+  blocking: "Unapproved deps | Ambiguous after story check | 3 failures | Missing config | Failing validations"
+  done: "Code matches reqs + All validations pass + Follows standards"
+  completion: "All [x]→Validations pass→Integration(if noted)→E2E(if noted)→DoD→Summary→HALT"
 
 dependencies:
   tasks:

docs/expansion-pack-ideas.md

@@ -0,0 +1,121 @@
+# 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

@@ -0,0 +1,265 @@
+# The Power of BMAD Expansion Packs
+
+## Overview
+
+BMAD Method's expansion packs unlock the framework's true potential by extending its natural language AI orchestration to ANY domain. While the core framework focuses on software development, expansion packs transform BMAD into a universal AI agent system.
+
+## Why Expansion Packs?
+
+### Keep Core Lean
+
+The core BMAD framework maintains its focus on software development, ensuring dev agents have maximum context for coding. Expansion packs handle everything else.
+
+### Domain Expertise
+
+Each expansion pack provides deep, specialized knowledge without bloating the core system. Install only what you need.
+
+### Community Innovation
+
+Anyone can create and share expansion packs, fostering a ecosystem of AI-powered solutions across all industries and interests.
+
+## Technical Expansion Packs
+
+### Game Development Pack
+
+Transform your AI into a complete game development studio:
+
+- **Game Designer**: Mechanics, balance, progression systems
+- **Level Designer**: Map layouts, puzzle design, difficulty curves
+- **Narrative Designer**: Story arcs, dialog trees, lore creation
+- **Art Director**: Visual style guides, asset specifications
+- **Sound Designer**: Audio direction, music themes, SFX planning
+
+### Mobile Development Pack
+
+Specialized agents for mobile app creation:
+
+- **iOS Specialist**: Swift/SwiftUI patterns, Apple guidelines
+- **Android Expert**: Kotlin best practices, Material Design
+- **Mobile UX Designer**: Touch interfaces, gesture patterns
+- **App Store Optimizer**: ASO strategies, listing optimization
+- **Performance Tuner**: Battery optimization, network efficiency
+
+### DevOps/Infrastructure Pack
+
+Complete infrastructure automation team:
+
+- **Cloud Architect**: AWS/Azure/GCP design patterns
+- **Security Specialist**: Zero-trust implementation, compliance
+- **SRE Expert**: Monitoring, alerting, incident response
+- **Container Orchestrator**: Kubernetes, Docker optimization
+- **Cost Optimizer**: Cloud spend analysis, resource right-sizing
+
+### Data Science Pack
+
+AI-powered data analysis team:
+
+- **Data Scientist**: Statistical analysis, ML model selection
+- **Data Engineer**: Pipeline design, ETL processes
+- **ML Engineer**: Model deployment, A/B testing
+- **Visualization Expert**: Dashboard design, insight communication
+- **Ethics Advisor**: Bias detection, fairness assessment
+
+## Non-Technical Expansion Packs
+
+### Business Strategy Pack
+
+Complete business advisory team:
+
+- **Strategy Consultant**: Market positioning, competitive analysis
+- **Financial Analyst**: Projections, unit economics, funding strategies
+- **Operations Manager**: Process optimization, efficiency improvements
+- **Marketing Strategist**: Go-to-market plans, growth hacking
+- **HR Advisor**: Talent strategies, culture building
+
+### Creative Writing Pack
+
+Your personal writing team:
+
+- **Plot Architect**: Three-act structure, story beats, pacing
+- **Character Psychologist**: Deep motivations, authentic dialog
+- **World Builder**: Consistent universes, cultural systems
+- **Editor**: Style consistency, grammar, flow
+- **Beta Reader**: Feedback simulation, plot hole detection
+
+### Health & Wellness Pack
+
+Personal wellness coaching system:
+
+- **Fitness Trainer**: Progressive overload, form correction
+- **Nutritionist**: Macro planning, supplement guidance
+- **Sleep Coach**: Circadian optimization, sleep hygiene
+- **Stress Manager**: Coping strategies, work-life balance
+- **Habit Engineer**: Behavior change, accountability systems
+
+### Education Pack
+
+Complete learning design system:
+
+- **Curriculum Architect**: Learning objectives, scope & sequence
+- **Instructional Designer**: Engagement strategies, multimedia learning
+- **Assessment Specialist**: Rubrics, formative/summative evaluation
+- **Differentiation Expert**: Adaptive learning, special needs
+- **EdTech Integrator**: Tool selection, digital pedagogy
+
+### Mental Health Support Pack
+
+Therapeutic support system:
+
+- **CBT Guide**: Cognitive restructuring, thought challenging
+- **Mindfulness Teacher**: Meditation scripts, awareness exercises
+- **Journal Therapist**: Reflective prompts, emotional processing
+- **Crisis Support**: Coping strategies, safety planning
+- **Habit Tracker**: Mood monitoring, trigger identification
+
+### Legal Assistant Pack
+
+Legal document and research support:
+
+- **Contract Analyst**: Term review, risk assessment
+- **Legal Researcher**: Case law, precedent analysis
+- **Document Drafter**: Template customization, clause libraries
+- **Compliance Checker**: Regulatory alignment, audit prep
+- **IP Advisor**: Patent strategies, trademark guidance
+
+### Real Estate Pack
+
+Property investment and management:
+
+- **Market Analyst**: Comparable analysis, trend prediction
+- **Investment Calculator**: ROI modeling, cash flow analysis
+- **Property Manager**: Tenant screening, maintenance scheduling
+- **Flip Strategist**: Renovation ROI, project planning
+- **Agent Assistant**: Listing optimization, showing prep
+
+## Unique & Innovative Packs
+
+### Role-Playing Game Master Pack
+
+AI-powered tabletop RPG assistance:
+
+- **World Master**: Dynamic world generation, NPC creation
+- **Combat Referee**: Initiative tracking, rule clarification
+- **Story Weaver**: Plot hooks, side quests, consequences
+- **Character Builder**: Backstory generation, stat optimization
+- **Loot Master**: Treasure generation, magic item creation
+
+### Life Event Planning Pack
+
+Major life event coordination:
+
+- **Wedding Planner**: Vendor coordination, timeline creation
+- **Event Designer**: Theme development, decoration plans
+- **Budget Manager**: Cost tracking, vendor negotiation
+- **Guest Coordinator**: RSVP tracking, seating arrangements
+- **Timeline Keeper**: Day-of scheduling, contingency planning
+
+### Hobby Mastery Pack
+
+Deep dive into specific hobbies:
+
+- **Garden Designer**: Plant selection, seasonal planning
+- **Brew Master**: Recipe formulation, process optimization
+- **Maker Assistant**: 3D printing, woodworking, crafts
+- **Collection Curator**: Organization, valuation, trading
+- **Photography Coach**: Composition, lighting, post-processing
+
+### Scientific Research Pack
+
+Research acceleration tools:
+
+- **Literature Reviewer**: Paper summarization, gap analysis
+- **Hypothesis Generator**: Research question formulation
+- **Methodology Designer**: Experiment planning, control design
+- **Statistical Advisor**: Test selection, power analysis
+- **Grant Writer**: Proposal structure, impact statements
+
+## Creating Your Own Expansion Pack
+
+### Step 1: Define Your Domain
+
+What expertise are you capturing? What problems will it solve?
+
+### Step 2: Design Your Agents
+
+Each agent should have:
+
+- Clear expertise area
+- Specific personality traits
+- Defined capabilities
+- Knowledge boundaries
+
+### Step 3: Create Tasks
+
+Tasks should be:
+
+- Step-by-step procedures
+- Reusable across scenarios
+- Clear and actionable
+- Domain-specific
+
+### Step 4: Build Templates
+
+Templates need:
+
+- Structured output format
+- Embedded LLM instructions
+- Placeholders for customization
+- Professional formatting
+
+### Step 5: Test & Iterate
+
+- Use with real scenarios
+- Gather user feedback
+- Refine agent responses
+- Improve task clarity
+
+### Step 6: Package & Share
+
+- Create clear documentation
+- Include usage examples
+- Add to expansion-packs directory
+- Share with community
+
+## The Future of Expansion Packs
+
+### Marketplace Potential
+
+Imagine a future where:
+
+- Professional expansion packs are sold
+- Certified packs for regulated industries
+- Community ratings and reviews
+- Automatic updates and improvements
+
+### AI Agent Ecosystems
+
+Expansion packs could enable:
+
+- Cross-pack agent collaboration
+- Industry-standard agent protocols
+- Interoperable AI workflows
+- Universal agent languages
+
+### Democratizing Expertise
+
+Every expansion pack:
+
+- Makes expert knowledge accessible
+- Reduces barriers to entry
+- Enables solo entrepreneurs
+- Empowers small teams
+
+## Getting Started
+
+1. **Browse existing packs**: Check `expansion-packs/` directory
+2. **Install what you need**: Use the installer's expansion pack option
+3. **Create your own**: Use the expansion-creator pack
+4. **Share with others**: Submit PRs with new packs
+5. **Build the future**: Help shape AI-assisted work
+
+## Remember
+
+The BMAD Method is more than a development framework - it's a platform for structuring human expertise into AI-accessible formats. Every expansion pack you create makes specialized knowledge more accessible to everyone.
+
+**What expertise will you share with the world?**

expansion-packs/expansion-creator/tasks/create-agent.md

@@ -4,7 +4,7 @@ This task guides you through creating a new BMAD agent following the standard te
 
 ## Prerequisites
 
-- Agent template: `.bmad-core/templates/agent-tmpl.md`
+- Agent template: `../templates/agent-tmpl.md`
 - Target directory: `.bmad-core/agents/`
 
 ## Steps

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

@@ -18,7 +18,7 @@ Every expansion pack MUST include a custom BMAD orchestrator agent with sophisti
 
 1. **Create Planning Document First**: Before any implementation, create a comprehensive plan for user approval
 2. **Agent Architecture Standards**: Use YAML-in-Markdown structure with activation instructions, personas, and command systems
-3. **Character Consistency**: Every agent must have a persistent persona with name, communication style, and numbered options protocol
+3. **Character Consistency**: Every agent must have a persistent persona with name, communication style, and numbered options protocol similar to `expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.md`
 4. **Custom Themed Orchestrator**: The orchestrator should embody the domain theme (e.g., Office Manager for medical, Project Lead for tech) for better user experience
 5. **Core Utilities Required**: ALWAYS include these core files in every expansion pack:
    - `tasks/create-doc.md` - Document creation from templates
@@ -26,8 +26,8 @@ Every expansion pack MUST include a custom BMAD orchestrator agent with sophisti
    - `utils/template-format.md` - Template markup conventions
    - `utils/workflow-management.md` - Workflow orchestration
 6. **Team and Workflow Requirements**: If pack has >1 agent, MUST include:
-   - At least one team configuration in `agent-teams/`
-   - At least one workflow in `workflows/`
+   - At least one team configuration in `expansion-packs/{new-expansion}/agent-teams/`
+   - At least one workflow in `expansion-packs/{new-expansion}workflows/`
 7. **Template Sophistication**: Implement LLM instruction embedding with `[[LLM: guidance]]`, conditional content, and variable systems
 8. **Workflow Orchestration**: Include decision trees, handoff protocols, and validation loops
 9. **Quality Assurance Integration**: Multi-level checklists with star ratings and ready/not-ready frameworks
@@ -1018,11 +1018,3 @@ Embedded knowledge (automatic):
 - [ ] Template conditional content tested with different scenarios
 - [ ] Workflow decision trees validated with sample use cases
 - [ ] Character interactions tested for consistency and professional authenticity
-
-```
-
-```
-
-```
-
-```

package-lock.json

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

package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.11.0",
+  "version": "4.13.0",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "main": "tools/cli.js",
   "bin": {

tools/installer/bin/bmad.js

@@ -50,7 +50,7 @@ program
   .option('-t, --team <team>', 'Install specific team with required agents and dependencies')
   .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, other)')
+  .option('-i, --ide <ide...>', 'Configure for specific IDE(s) - can specify multiple (cursor, claude-code, windsurf, roo, cline, other)')
   .option('-e, --expansion-packs <packs...>', 'Install specific expansion packs (can specify multiple)')
   .action(async (options) => {
     try {
@@ -67,7 +67,7 @@ program
         if (options.agent) installType = 'single-agent';
         else if (options.team) installType = 'team';
         else if (options.expansionOnly) installType = 'expansion-only';
-        
+
         const config = {
           installType,
           agent: options.agent,
@@ -164,13 +164,13 @@ async function promptInstallation() {
   // Check if this is an existing v4 installation
   const installDir = path.resolve(answers.directory);
   const state = await installer.detectInstallationState(installDir);
-  
+
   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',
@@ -179,7 +179,7 @@ async function promptInstallation() {
         default: true
       }
     ]);
-    
+
     if (shouldUpdate) {
       // Skip other prompts and go directly to update
       answers.installType = 'update';
@@ -256,11 +256,11 @@ async function promptInstallation() {
   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 => ({
@@ -274,7 +274,7 @@ async function promptInstallation() {
             value: pack.id
           }));
         }
-        
+
         const { expansionPacks } = await inquirer.prompt([
           {
             type: 'checkbox',
@@ -289,7 +289,7 @@ async function promptInstallation() {
             } : undefined
           }
         ]);
-        
+
         // Use selected expansion packs directly
         answers.expansionPacks = expansionPacks;
       } else {
@@ -313,11 +313,12 @@ async function promptInstallation() {
         { name: 'Cursor', value: 'cursor' },
         { name: 'Claude Code', value: 'claude-code' },
         { name: 'Windsurf', value: 'windsurf' },
-        { name: 'Roo Code', value: 'roo' }
+        { name: 'Roo Code', value: 'roo' },
+        { name: 'Cline', value: 'cline' }
       ]
     }
   ]);
-  
+
   // Use selected IDEs directly
   answers.ides = ides;
 

tools/installer/config/install.config.yml

@@ -92,10 +92,15 @@ ide-configurations:
       # 3. The AI will adopt that agent's full personality and capabilities
   cline:
     name: Cline
-    format: unknown
+    rule-dir: .clinerules/
+    format: multi-file
+    command-suffix: .md
     instructions: |
-      # Cline configuration coming soon
-      # Manual setup: Copy IDE agent files to your Cline configuration
+      # To use BMAD agents in Cline:
+      # 1. Open the Cline chat panel in VS Code
+      # 2. Type @agent-name (e.g., "@dev", "@pm", "@architect")
+      # 3. The agent will adopt that persona for the conversation
+      # 4. Rules are stored in .clinerules/ directory in your project
 available-agents:
   - id: analyst
     name: Business Analyst

tools/installer/lib/ide-setup.js

@@ -31,6 +31,8 @@ class IdeSetup {
         return this.setupWindsurf(installDir, selectedAgent);
       case "roo":
         return this.setupRoo(installDir, selectedAgent);
+      case "cline":
+        return this.setupCline(installDir, selectedAgent);
       default:
         console.log(chalk.yellow(`\nIDE ${ide} not yet supported`));
         return false;
@@ -340,6 +342,75 @@ class IdeSetup {
 
     return true;
   }
+
+  async setupCline(installDir, selectedAgent) {
+    const clineRulesDir = path.join(installDir, ".clinerules");
+    const agents = selectedAgent ? [selectedAgent] : await this.getAllAgentIds(installDir);
+
+    await fileManager.ensureDirectory(clineRulesDir);
+
+    // Define agent order for numeric prefixes
+    const agentOrder = {
+      'bmad-master': 1,
+      'bmad-orchestrator': 2,
+      'pm': 3,
+      'analyst': 4,
+      'architect': 5,
+      'po': 6,
+      'sm': 7,
+      'dev': 8,
+      'qa': 9,
+      'ux-expert': 10
+    };
+
+    for (const agentId of agents) {
+      // Check if .bmad-core is a subdirectory (full install) or if agents are in root (single agent install)
+      let agentPath = path.join(installDir, ".bmad-core", "agents", `${agentId}.md`);
+      if (!(await fileManager.pathExists(agentPath))) {
+        agentPath = path.join(installDir, "agents", `${agentId}.md`);
+      }
+
+      if (await fileManager.pathExists(agentPath)) {
+        const agentContent = await fileManager.readFile(agentPath);
+
+        // Get numeric prefix for ordering
+        const order = agentOrder[agentId] || 99;
+        const prefix = order.toString().padStart(2, '0');
+        const mdPath = path.join(clineRulesDir, `${prefix}-${agentId}.md`);
+
+        // Create MD content for Cline (focused on project standards and role)
+        let mdContent = `# ${this.getAgentTitle(agentId)} Agent\n\n`;
+        mdContent += `This rule defines the ${this.getAgentTitle(agentId)} persona and project standards.\n\n`;
+        mdContent += "## Role Definition\n\n";
+        mdContent +=
+          "When the user types `@" + agentId + "`, adopt this persona and follow these guidelines:\n\n";
+        mdContent += "```yml\n";
+        // Extract just the YAML content from the agent file
+        const yamlMatch = agentContent.match(/```ya?ml\n([\s\S]*?)```/);
+        if (yamlMatch) {
+          mdContent += yamlMatch[1].trim();
+        } else {
+          // If no YAML found, include the whole content minus the header
+          mdContent += agentContent.replace(/^#.*$/m, "").trim();
+        }
+        mdContent += "\n```\n\n";
+        mdContent += "## Project Standards\n\n";
+        mdContent += `- Always maintain consistency with project documentation in .bmad-core/\n`;
+        mdContent += `- Follow the agent's specific guidelines and constraints\n`;
+        mdContent += `- Update relevant project files when making changes\n`;
+        mdContent += `- Reference the complete agent definition in [.bmad-core/agents/${agentId}.md](.bmad-core/agents/${agentId}.md)\n\n`;
+        mdContent += "## Usage\n\n";
+        mdContent += `Type \`@${agentId}\` to activate this ${this.getAgentTitle(agentId)} persona.\n`;
+
+        await fileManager.writeFile(mdPath, mdContent);
+        console.log(chalk.green(`✓ Created rule: ${prefix}-${agentId}.md`));
+      }
+    }
+
+    console.log(chalk.green(`\n✓ Created Cline rules in ${clineRulesDir}`));
+
+    return true;
+  }
 }
 
 module.exports = new IdeSetup();

tools/installer/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.11.0",
+  "version": "4.13.0",
   "description": "BMAD Method installer - AI-powered Agile development framework",
   "main": "lib/installer.js",
   "bin": {

tools/upgraders/v3-to-v4-upgrader.js

@@ -561,6 +561,7 @@ class V3ToV4Upgrader {
         "claude-code": "Commands created in .claude/commands/",
         windsurf: "Rules created in .windsurf/rules/",
         roo: "Custom modes created in .roomodes",
+        cline: "Rules created in .clinerules/",
       };
 
       // Setup each selected IDE