bmad-method 4.30.4 → 4.32.0

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

@@ -1,31 +0,0 @@
-# BMad Method Guide for Gemini CLI
-
-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/bmad-method/` directory with all agent context in GEMINI.md file
-
-## 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.
-
-## Gemini CLI-Specific Features
-
-- **Context files**: All agents loaded as context in `.gemini/bmad-method/GEMINI.md`
-- **Automatic loading**: GEMINI.md 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

package/docs/agentic-tools/github-copilot-guide.md

@@ -1,42 +0,0 @@
-# BMad Method Guide for GitHub Copilot
-
-For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.md).
-
-## Installation
-
-When running `npx bmad-method install`, select **GitHub Copilot** as your IDE. This command will perform the following actions:
-
-- Create the `.bmad-core/` directory with all the agent rule files.
-- Create the `.vscode/` directory and add a `settings.json` file if it does not already exist, and add the basic configuration to enable GitHub Copilot's agent mode.
-- Create a chatmodes file under your .github folder for each specific agent being added
-
-## Using BMAD Agents in GitHub Copilot
-
-1.  **Open GitHub Copilot chat** in VS Code (`⌃⌘I` on Mac, `Ctrl+Alt+I` on Windows/Linux).
-2.  Select the agent you want to use from the chat input's participant selector (e.g., `@workspace` > `dev`).
-3.  The agent adopts that persona for the conversation.
-4.  Use `*help` to see the commands available for the selected agent.
-
-## Available Agents
-
-You can switch between agents using the chat participant selector. The following agents are available for GitHub Copilot:
-
-- `bmad-master` - Master Task Executor
-- `dev` - Development expert
-- `qa` - Quality Assurance specialist
-- `ux-expert` - UX specialist
-
-## GitHub Copilot-Specific Features
-
-- **Settings**: Use the `.vscode/settings.json` file to configure Copilot behavior. The installer can configure these for you.
-  - `chat.agent.maxRequests`: Maximum requests per agent session (recommended: 15).
-  - `github.copilot.chat.agent.runTasks`: Allow agents to run workspace tasks (e.g., from `package.json` scripts).
-  - `github.copilot.chat.agent.autoFix`: Enable automatic error detection and fixing in generated code.
-  - `chat.tools.autoApprove`: Auto-approve ALL tools without confirmation (use with caution).
-- **VS Code integration**: Works within VS Code's GitHub Copilot chat panel.
-- **Tool Confirmation**: Copilot will ask for confirmation before running tools that can modify files. You can approve a tool once, for the session, or always.
-
-## Tips for GitHub Copilot Users
-
-- You can use a `.github/copilot-instructions.md` file to provide additional context or instructions for your projects that are not covered by the BMAD framework.
-- BMAD agents can come with a pre-configured set of tools. You can see which tools an agent uses by looking at the `tools` section in its `.github/chatmodes/[agent].chatmode.md` file.

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

@@ -1,15 +0,0 @@
-# BMad Method Guide for Roo Code
-
-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
-
-## Roo Code-Specific Features
-
-- **Mode file**: `.roomodes` in project root
-- **Mode switching**: Use mode selecto

package/docs/agentic-tools/trae-guide.md

@@ -1,14 +0,0 @@
-# BMad Method Guide for Trae
-
-For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.md).
-
-## Installation
-
-When running `npx bmad-method install`, select **Trae** as your IDE. This creates:
-
-- `.bmad-core/` folder with all agents
-- `.trae/rules/` folder with agent rule files (`.md`)
-
-## Using BMad Agents in Trae
-
-Type `@agent-name` in chat to activate an agent.

package/docs/agentic-tools/windsurf-guide.md

@@ -1,14 +0,0 @@
-# BMad Method Guide for Windsurf
-
-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.

package/docs/bmad-workflow-guide.md

@@ -1,166 +0,0 @@
-# BMad Method Universal Workflow Guide
-
-This guide outlines the core BMad workflow that applies regardless of which AI-powered IDE you're using.
-
-## Overview
-
-The BMad Method follows a structured approach to AI-assisted software development:
-
-1. **Install BMad** in your project
-2. **Plan with Gemini** using team-fullstack
-3. **Organize with bmad-master** (document sharding)
-4. **Develop iteratively** with SM → Dev cycles
-
-## The Complete Workflow
-
-### Phase 1: Project Setup
-
-1. **Install BMad in your project**:
-
-   ```bash
-   npx bmad-method install
-   ```
-
-   - Choose "Complete installation"
-   - Select your IDE (Cursor, Claude Code, Windsurf, Trae, Roo Code, or GitHub Copilot)
-
-2. **Verify installation**:
-   - `.bmad-core/` folder created with all agents
-   - IDE-specific integration files created
-   - All agent commands/rules/modes available
-
-### Phase 2: Ideation & Planning (Gemini)
-
-Use Google's Gemini for collaborative planning with the full team:
-
-1. **Open [Google Gems](https://gemini.google.com/gems/view)**
-2. **Create a new Gem**:
-   - Give it a title and description (e.g., "BMad Team Fullstack")
-3. **Load team-fullstack**:
-   - Copy contents of: `web-bundles/teams/team-fullstack.txt` from your project
-   - Paste this content into the Gem setup to configure the team
-4. **Collaborate with the team**:
-   - Business Analyst: Requirements gathering
-   - Product Manager: Feature prioritization
-   - Solution Architect: Technical design
-   - UX Expert: User experience design
-
-### Example Gemini Sessions:
-
-```text
-"I want to build a [type] application that [core purpose].
-Help me brainstorm features and create a comprehensive PRD."
-
-"Based on this PRD, design a scalable technical architecture
-that can handle [specific requirements]."
-```
-
-5. **Export planning documents**:
-   - Copy the PRD output and save as `docs/prd.md` in your project
-   - Copy the architecture output and save as `docs/architecture.md` in your project
-
-### Phase 3: Document Organization (IDE)
-
-Switch back to your IDE for document management:
-
-1. **Load bmad-master agent** (syntax varies by IDE)
-2. **Shard the PRD**:
-   ```
-   *shard-doc docs/prd.md prd
-   ```
-3. **Shard the architecture**:
-   ```
-   *shard-doc docs/architecture.md architecture
-   ```
-
-**Result**: Organized folder structure:
-
-- `docs/prd/` - Broken down PRD sections
-- `docs/architecture/` - Broken down architecture sections
-
-### Phase 4: Iterative Development
-
-Follow the SM → Dev cycle for systematic story development:
-
-#### Story Creation (Scrum Master)
-
-1. **Start new chat/conversation**
-2. **Load SM agent**
-3. **Execute**: `*create` (runs create-next-story task)
-4. **Review generated story** in `docs/stories/`
-5. **Update status**: Change from "Draft" to "Approved"
-
-#### Story Implementation (Developer)
-
-1. **Start new chat/conversation**
-2. **Load Dev agent**
-3. **Agent asks**: Which story to implement
-4. **Follow development tasks**
-5. **Complete implementation**
-6. **Update status**: Change to "Done"
-
-#### Repeat Until Complete
-
-- **SM**: Create next story → Review → Approve
-- **Dev**: Implement story → Complete → Mark done
-- **Continue**: Until all features implemented
-
-## IDE-Specific Syntax
-
-### Agent Loading Syntax by IDE:
-
-- **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
-- **Cursor**: `@agent-name` (e.g., `@bmad-master`)
-- **Gemini CLI**: `*agent-name` (e.g., `*bmad-master`)
-- **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
-- **Trae**: `@agent-name` (e.g., `@bmad-master`)
-- **Roo Code**: Select mode from mode selector (e.g., `bmad-master`)
-- **GitHub Copilot**: Open the Chat view (`⌃⌘I` on Mac, `Ctrl+Alt+I` on Windows/Linux) and select **Agent** from the chat mode selector.
-
-### Chat Management:
-
-- **Claude Code, Cursor, Windsurf, Trae**: Start new chats when switching agents
-- **Roo Code**: Switch modes within the same conversation
-
-## Available Agents
-
-### Core Development Agents:
-
-- **bmad-master**: Universal task executor, document management
-- **sm**: Scrum Master for story creation and agile process
-- **dev**: Full-stack developer for implementation
-- **architect**: Solution architect for technical design
-
-### Specialized Agents:
-
-- **pm**: Product manager for planning and prioritization
-- **analyst**: Business analyst for requirements
-- **qa**: QA specialist for testing strategies
-- **po**: Product owner for backlog management
-- **ux-expert**: UX specialist for design
-
-## Key Principles
-
-1. **Agent Specialization**: Each agent has specific expertise and responsibilities
-2. **Clean Handoffs**: Always start fresh when switching between agents
-3. **Status Tracking**: Maintain story statuses (Draft → Approved → InProgress → Done)
-4. **Iterative Development**: Complete one story before starting the next
-5. **Documentation First**: Always start with solid PRD and architecture
-
-## Common Commands
-
-Every agent supports these core commands:
-
-- `*help` - Show available commands
-- `*status` - Show current context/progress
-- `*exit` - Exit the agent mode
-
-## Success Tips
-
-- **Use Gemini for big picture planning** - The team-fullstack bundle provides collaborative expertise
-- **Use bmad-master for document organization** - Sharding creates manageable chunks
-- **Follow the SM → Dev cycle religiously** - This ensures systematic progress
-- **Keep conversations focused** - One agent, one task per conversation
-- **Review everything** - Always review and approve before marking complete
-
-This workflow ensures systematic, AI-assisted development following agile principles with clear separation of concerns and consistent progress tracking.