bmad-stella 1.0.0

package/CONTRIBUTING.md

@@ -0,0 +1,243 @@
+# Contributing to this project
+
+Thank you for contributing to this project! This document outlines the process for contributing and some guidelines to follow.
+
+🆕 **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](docs/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/gk8jAdXWmj) for real-time discussions or search past discussions or ideas.
+
+## Code of Conduct
+
+By participating in this project, you agree to abide by our Code of Conduct. Please read it before participating.
+
+## Before Submitting a PR
+
+**IMPORTANT**: All PRs must pass validation checks before they can be merged.
+
+### Required Checks
+
+Before submitting your PR, run these commands locally:
+
+```bash
+# Run all validation checks
+npm run pre-release
+
+# Or run them individually:
+npm run validate     # Validate agent/team configs
+npm run format:check # Check code formatting
+npm run lint        # Check for linting issues
+```
+
+### Fixing Issues
+
+If any checks fail, use these commands to fix them:
+
+```bash
+# Fix all issues automatically
+npm run fix
+
+# Or fix individually:
+npm run format      # Fix formatting issues
+npm run lint:fix    # Fix linting issues
+```
+
+### Setup Git Hooks (Optional but Recommended)
+
+To catch issues before committing:
+
+```bash
+# Run this once after cloning
+chmod +x tools/setup-hooks.sh
+./tools/setup-hooks.sh
+```
+
+## How to Contribute
+
+### Reporting Bugs
+
+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
+
+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](docs/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
+4. Run any tests or linting to ensure quality
+5. Commit your changes with clear, descriptive messages following our commit message convention
+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:
+
+### 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]
+Fixes #[issue number] (if applicable)
+
+## 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
+
+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
+
+- Follow the existing code style and conventions
+- Write clear comments for complex logic
+
+## License
+
+By contributing to this project, you agree that your contributions will be licensed under the MIT License.

package/LICENSE

@@ -0,0 +1,26 @@
+MIT License
+
+Copyright (c) 2025 BMad Code, LLC
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+TRADEMARK NOTICE:
+BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. The use of these 
+trademarks in this software does not grant any rights to use the trademarks 
+for any other purpose.

package/PR-opencode-agents-generator.md

@@ -0,0 +1,40 @@
+# feat(opencode): compact AGENTS.md generator and JSON-only integration
+
+## What
+
+Add JSON-only OpenCode integration and a compact AGENTS.md generator (no large embeds; clickable file links) with idempotent merges for BMAD instructions, agents, and commands.
+
+## Why
+
+Keep OpenCode config schema‑compliant and small, avoid key collisions, and provide a readable agents/tasks index without inflating AGENTS.md.
+
+## How
+
+- Ensure `.bmad-core/core-config.yaml` in `instructions`
+- Merge only selected packages’ agents/commands into opencode.json file
+- Orchestrators `mode: primary`; all agents enable `write`, `edit`, `bash`
+- Descriptions from `whenToUse`/task `Purpose` with sanitization + fallbacks
+- Explicit warnings for non‑BMAD collisions; AGENTS.md uses a strict 3‑column table with links
+
+## Testing
+
+- Run: `npx bmad-method install -f -i opencode`
+- Verify: `opencode.json[c]` updated/created as expected, `AGENTS.md` OpenCode section is compact with links
+- Pre‑push checks:
+
+```bash
+npm run pre-release
+# or individually
+npm run validate
+npm run format:check
+npm run lint
+# if anything fails
+npm run fix
+# or
+npm run format
+npm run lint:fix
+```
+
+Fixes #<issue-number>
+
+Targets: `next` branch

package/README.md

@@ -0,0 +1,159 @@
+# BMad-Stella: Streamlined AI-Powered Development Workflow
+
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+[![Node.js Version](https://img.shields.io/badge/node-%3E%3D16.0.0-brightgreen)](https://nodejs.org)
+[![Built on BMad-Method](https://img.shields.io/badge/Built%20on-BMad%20Method-blue)](https://github.com/bmadcode/bmad-method)
+
+A customized implementation of BMAD-METHOD™ optimized for **Claude Code CLI**, providing a streamlined development workflow with specialized AI agents for planning, development, testing, and code review.
+
+## Overview
+
+**BMad-Stella** is a focused, implementation-oriented workflow built on BMAD-METHOD™ foundations. It provides four specialized agents that work together seamlessly in Claude Code CLI to deliver high-quality software:
+
+**Core Workflow:**
+
+```
+Planner → Dev → QA → Reviewer
+         ↑______(if fixes needed)
+```
+
+**Key Features:**
+
+- ✨ **Planner Agent (Alex)** - Transforms JIRA tickets into detailed implementation plans
+- 💻 **Dev Agent (Bob)** - Executes tasks sequentially with comprehensive testing
+- 🧪 **QA Agent (Quinn)** - Designs test strategies and ensures requirements traceability
+- 🔍 **Reviewer Agent (Morgan)** - Reviews code and applies practical optimizations
+
+**Built for:** Teams using JIRA, Confluence, and Claude Code CLI for agile development.
+
+**📖 [Complete Stella User Guide](docs/stella-user-guide.md)** - Installation, workflow, and command reference
+
+## Quick Start
+
+### Prerequisites
+
+- [Node.js](https://nodejs.org) v20+ installed
+- [Claude Code CLI](https://docs.anthropic.com/claude/docs/claude-code) installed and configured
+- JIRA account with access to your organization's instance
+- Confluence page URL for architecture documentation (recommended)
+
+### Installation (5 minutes)
+
+**Run the interactive installer:**
+
+```bash
+npx bmad-stella install
+```
+
+**Follow the prompts:**
+
+1. Provide your project directory path
+2. Select **BMad Agile Core System**
+3. Enter Confluence URL for architecture docs
+4. Select **Claude Code** as IDE
+5. Skip web bundles installation (enter `n`)
+6. Configure Atlassian MCP Server (enter `y`)
+7. Provide JIRA instance URL (e.g., `https://stellaint.atlassian.net`)
+
+**📖 [Detailed Installation Guide](docs/stella-user-guide.md#bmad-stella-installation-process)**
+
+## Documentation & Resources
+
+### Essential Guides
+
+- 📖 **[Stella User Guide](docs/stella-user-guide.md)** - Complete installation, workflow, and command reference
+- 🚀 **[Quick Start Guide](docs/stella-user-guide.md#quick-start)** - Get started in minutes
+- 🔧 **[Command Reference](docs/stella-user-guide.md#command-reference)** - All agent commands with detailed usage
+- 💡 **[Best Practices](docs/stella-user-guide.md#best-practices)** - Tips for success with each agent
+- 🐛 **[Troubleshooting](docs/stella-user-guide.md#troubleshooting)** - Common issues and solutions
+
+### Understanding BMad-Stella
+
+**Core Workflow Diagram:**
+
+See the [complete Stella Development Workflow](docs/stella-user-guide.md#the-stella-development-workflow) with visual mermaid diagram showing the complete agent interaction flow.
+
+**📖 [Full Command Reference](docs/stella-user-guide.md#command-reference)**
+
+## Project Structure
+
+### Core Directories
+
+```
+bmad-core/                      # Core agent system and workflows
+├── agents/                     # Agent definitions (planner, dev, qa, reviewer)
+├── tasks/                      # Reusable task definitions
+├── templates/                  # Document templates
+├── checklists/                 # Quality assurance checklists
+└── data/                       # Knowledge base and preferences
+
+tools/                          # Installation and build tools
+├── installer/
+│   ├── bin/
+│   │   └── bmad.js             # Main installer CLI
+│   ├── bmad-npx-wrapper    # NPX entry point
+│   ├── ...
+│   └── lib/                    # Installer modules
+│       ├── dependency-manager.js
+│       ├── config-generator.js
+│       └── ...                 # Other installer utilities
+```
+
+### Extending BMad-Stella
+
+**Adding New Agents or Skills:**
+
+- Add agent definitions to `bmad-core/agents/`
+- Create supporting tasks in `bmad-core/tasks/`
+- Add templates to `bmad-core/templates/`
+- Update `bmad-core/checklists/` for validation
+
+**Customizing Installation:**
+
+- Modify `tools/installer/bin/bmad.js` for CLI behavior
+- Update `tools/installer/lib/` modules for installation logic
+- Edit `tools/installer/lib/dependency-manager.js` for dependency handling
+- Adjust `tools/installer/lib/config-generator.js` for configuration creation
+
+**Key Files:**
+
+- `tools/installer/bin/bmad-npx-wrapper` - NPX entry point for installation
+- `tools/installer/bin/bmad.js` - Main installer command-line interface
+- `tools/installer/lib/*.js` - Core installation functionality
+
+## Support
+
+- 📖 [Stella User Guide](docs/stella-user-guide.md) - Complete documentation
+- 🐛 [Issue Tracker](https://github.com/Asrarul-BS23/BMad-Stella/issues) - Report bugs
+- 💬 [BMad Community Discord](https://discord.gg/gk8jAdXWmj) - Get help and share ideas
+
+## Contributing
+
+Contributions are welcome! Whether it's bug fixes, new features, or documentation improvements.
+
+**Contribution Guidelines:**
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/amazing-feature`)
+3. Make your changes and test thoroughly
+4. Commit with clear messages (`git commit -m 'feat: add amazing feature'`)
+5. Push to your fork (`git push origin feature/amazing-feature`)
+6. Open a Pull Request
+
+**Please ensure:**
+
+- Code follows existing patterns and conventions
+- Documentation is updated for new features
+- Changes are tested in Claude Code CLI
+
+## License
+
+MIT License - see [LICENSE](LICENSE) for details.
+
+## Acknowledgments
+
+Built on the foundations of [BMAD-METHOD™](https://github.com/bmadcode/bmad-method) by BMad Code, LLC.
+
+Special thanks to the BMad community for their continuous support and contributions.
+
+---

package/REVIEWER-AGENT-SIMPLE.md

@@ -0,0 +1,66 @@
+# 🔍 Code Reviewer & Optimizer Agent - ULTRA SIMPLE
+
+**Agent:** Morgan (reviewer)
+**Status:** ✅ Ready to Use
+**Philosophy:** Direct action, no reports, just improvements!
+
+---
+
+## Files
+
+1. **`bmad-core/agents/reviewer.md`** - Agent definition
+2. **`bmad-core/tasks/review-and-improve.md`** - Review and apply improvements
+
+**That's it! Only 2 files.**
+
+---
+
+## Commands
+
+```bash
+*help       # Show commands
+*review     # Review and improve code
+*exit       # Exit agent
+```
+
+---
+
+## Usage
+
+```bash
+@reviewer
+*review bmad-docs/impl-plan/PROJ-123-feature.md
+```
+
+---
+
+## What It Does
+
+**Simple workflow:**
+
+1. Load files
+2. Find improvements (time complexity, code quality)
+3. Show improvement with before/after code
+4. Ask user: "Apply this? (yes/no)"
+5. Apply if yes, skip if no
+6. Done!
+
+**Focuses on:**
+
+- ✅ Reducing time complexity (O(n²) → O(n))
+- ✅ Using better data structures (Map/Set)
+- ✅ Removing duplicate code
+- ✅ Batching database queries
+- ✅ Fixing variable names
+- ✅ Adding error handling
+
+**Avoids:**
+
+- ❌ Caching layers
+- ❌ Vector embeddings
+- ❌ Infrastructure changes
+- ❌ Complex reports
+
+---
+
+**Direct. Practical. Gets shit done!** 🚀

package/bmad-core/agent-teams/team-all.yaml

@@ -0,0 +1,15 @@
+# <!-- Powered by BMAD™ Core -->
+bundle:
+  name: Team All
+  icon: 👥
+  description: Includes every core system agent.
+agents:
+  - bmad-orchestrator
+  - "*"
+workflows:
+  - brownfield-fullstack.yaml
+  - brownfield-service.yaml
+  - brownfield-ui.yaml
+  - greenfield-fullstack.yaml
+  - greenfield-service.yaml
+  - greenfield-ui.yaml

package/bmad-core/agent-teams/team-fullstack.yaml

@@ -0,0 +1,19 @@
+# <!-- Powered by BMAD™ Core -->
+bundle:
+  name: Team Fullstack
+  icon: 🚀
+  description: Team capable of full stack, front end only, or service development.
+agents:
+  - bmad-orchestrator
+  - analyst
+  - pm
+  - ux-expert
+  - architect
+  - po
+workflows:
+  - brownfield-fullstack.yaml
+  - brownfield-service.yaml
+  - brownfield-ui.yaml
+  - greenfield-fullstack.yaml
+  - greenfield-service.yaml
+  - greenfield-ui.yaml

package/bmad-core/agent-teams/team-ide-minimal.yaml

@@ -0,0 +1,11 @@
+# <!-- Powered by BMAD™ Core -->
+bundle:
+  name: Team IDE Minimal
+  icon: ⚡
+  description: Only the bare minimum for the IDE PO SM dev qa cycle.
+agents:
+  - po
+  - sm
+  - dev
+  - qa
+workflows: null

package/bmad-core/agent-teams/team-no-ui.yaml

@@ -0,0 +1,14 @@
+# <!-- Powered by BMAD™ Core -->
+bundle:
+  name: Team No UI
+  icon: 🔧
+  description: Team with no UX or UI Planning.
+agents:
+  - bmad-orchestrator
+  - analyst
+  - pm
+  - architect
+  - po
+workflows:
+  - greenfield-service.yaml
+  - brownfield-service.yaml

package/bmad-core/agents/analyst.md

@@ -0,0 +1,84 @@
+<!-- Powered by BMAD™ Core -->
+
+# analyst
+
+ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
+
+CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+
+## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
+
+```yaml
+IDE-FILE-RESOLUTION:
+  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
+  - Dependencies map to {root}/{type}/{name}
+  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
+  - Example: create-doc.md → {root}/tasks/create-doc.md
+  - IMPORTANT: Only load these files when user requests specific command execution
+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), ALWAYS ask for clarification if no clear match.
+activation-instructions:
+  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - DO NOT: Load any other agent files during activation
+  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
+  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
+  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
+  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
+  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - STAY IN CHARACTER!
+  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+agent:
+  name: Mary
+  id: analyst
+  title: Business Analyst
+  icon: 📊
+  whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, initial project discovery, and documenting existing projects (brownfield)
+  customization: null
+persona:
+  role: Insightful Analyst & Strategic Ideation Partner
+  style: Analytical, inquisitive, creative, facilitative, objective, data-informed
+  identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
+  focus: Research planning, ideation facilitation, strategic analysis, actionable insights
+  core_principles:
+    - Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
+    - Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
+    - Strategic Contextualization - Frame all work within broader strategic context
+    - Facilitate Clarity & Shared Understanding - Help articulate needs with precision
+    - Creative Exploration & Divergent Thinking - Encourage wide range of ideas before narrowing
+    - Structured & Methodical Approach - Apply systematic methods for thoroughness
+    - Action-Oriented Outputs - Produce clear, actionable deliverables
+    - Collaborative Partnership - Engage as a thinking partner with iterative refinement
+    - Maintaining a Broad Perspective - Stay aware of market trends and dynamics
+    - Integrity of Information - Ensure accurate sourcing and representation
+    - Numbered Options Protocol - Always use numbered lists for selections
+# All commands require * prefix when used (e.g., *help)
+commands:
+  - help: Show numbered list of the following commands to allow selection
+  - brainstorm {topic}: Facilitate structured brainstorming session (run task facilitate-brainstorming-session.md with template brainstorming-output-tmpl.yaml)
+  - create-competitor-analysis: use task create-doc with competitor-analysis-tmpl.yaml
+  - create-project-brief: use task create-doc with project-brief-tmpl.yaml
+  - doc-out: Output full document in progress to current destination file
+  - elicit: run the task advanced-elicitation
+  - perform-market-research: use task create-doc with market-research-tmpl.yaml
+  - research-prompt {topic}: execute task create-deep-research-prompt.md
+  - yolo: Toggle Yolo Mode
+  - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
+dependencies:
+  data:
+    - bmad-kb.md
+    - brainstorming-techniques.md
+  tasks:
+    - advanced-elicitation.md
+    - create-deep-research-prompt.md
+    - create-doc.md
+    - document-project.md
+    - facilitate-brainstorming-session.md
+  templates:
+    - brainstorming-output-tmpl.yaml
+    - competitor-analysis-tmpl.yaml
+    - market-research-tmpl.yaml
+    - project-brief-tmpl.yaml
+```