ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: WIP create-docv2

Browse Source
This commit is contained in:
Brian Madison
2025-07-06 00:10:00 -05:00
parent be9453f234
commit c107af0598
16 changed files with 4064 additions and 1916 deletions
Download Patch File Download Diff File Expand all files Collapse all files

731
dist/agents/analyst.txt vendored
View File

File diff suppressed because it is too large Load Diff

1005
dist/agents/bmad-master.txt vendored
View File

File diff suppressed because it is too large Load Diff

250
dist/agents/bmad-orchestrator.txt vendored
View File

@@ -185,91 +185,116 @@ dependencies:
- Provide optional reflective and brainstorming actions to enhance content quality
- Enable deeper exploration of ideas through structured elicitation techniques
- Support iterative refinement through multiple analytical perspectives
- Usable during template-driven document creation or any chat conversation
## Usage Scenarios
### Scenario 1: Template Document Creation
After outputting a section during document creation:
1. **Section Review**: Ask user to review the drafted section
2. **Offer Elicitation**: Present 9 carefully selected elicitation methods
3. **Simple Selection**: User types a number (0-8) to engage method, or 9 to proceed
4. **Execute & Loop**: Apply selected method, then re-offer choices until user proceeds
### Scenario 2: General Chat Elicitation
User can request advanced elicitation on any agent output:
- User says "do advanced elicitation" or similar
- Agent selects 9 relevant methods for the context
- Same simple 0-9 selection process
## Task Instructions
### 1. Section Context and Review
### 1. Intelligent Method Selection
[[LLM: When invoked after outputting a section:
**Context Analysis**: Before presenting options, analyze:
1. First, provide a brief 1-2 sentence summary of what the user should look for in the section just presented (e.g., "Please review the technology choices for completeness and alignment with your project needs. Pay special attention to version numbers and any missing categories.")
- **Content Type**: Technical specs, user stories, architecture, requirements, etc.
- **Complexity Level**: Simple, moderate, or complex content
- **Stakeholder Needs**: Who will use this information
- **Risk Level**: High-impact decisions vs routine items
- **Creative Potential**: Opportunities for innovation or alternatives
2. If the section contains Mermaid diagrams, explain each diagram briefly before offering elicitation options (e.g., "The component diagram shows the main system modules and their interactions. Notice how the API Gateway routes requests to different services.")
**Method Selection Strategy**:
3. If the section contains multiple distinct items (like multiple components, multiple patterns, etc.), inform the user they can apply elicitation actions to:
1. **Always Include Core Methods** (choose 3-4):
- Expand or Contract for Audience
- Critique and Refine
- Identify Potential Risks
- Assess Alignment with Goals
2. **Context-Specific Methods** (choose 4-5):
- **Technical Content**: Tree of Thoughts, ReWOO, Meta-Prompting
- **User-Facing Content**: Agile Team Perspective, Stakeholder Roundtable
- **Creative Content**: Innovation Tournament, Escape Room Challenge
- **Strategic Content**: Red Team vs Blue Team, Hindsight Reflection
3. **Always Include**: "Proceed / No Further Actions" as option 9
### 2. Section Context and Review
When invoked after outputting a section:
1. **Provide Context Summary**: Give a brief 1-2 sentence summary of what the user should look for in the section just presented
2. **Explain Visual Elements**: If the section contains diagrams, explain them briefly before offering elicitation options
3. **Clarify Scope Options**: If the section contains multiple distinct items, inform the user they can apply elicitation actions to:
- The entire section as a whole
- Individual items within the section (specify which item when selecting an action)
4. Then present the action list as specified below.]]
### 3. Present Elicitation Options
### 2. Ask for Review and Present Action List
**Review Request Process:**
[[LLM: Ask the user to review the drafted section. In the SAME message, inform them that they can suggest additions, removals, or modifications, OR they can select an action by number from the 'Advanced Reflective, Elicitation & Brainstorming Actions'. If there are multiple items in the section, mention they can specify which item(s) to apply the action to. Then, present ONLY the numbered list (0-9) of these actions. Conclude by stating that selecting 9 will proceed to the next section. Await user selection. If an elicitation action (0-8) is chosen, execute it and then re-offer this combined review/elicitation choice. If option 9 is chosen, or if the user provides direct feedback, proceed accordingly.]]
- Ask the user to review the drafted section
- In the SAME message, inform them they can suggest direct changes OR select an elicitation method
- Present 9 intelligently selected methods (0-8) plus "Proceed" (9)
- Keep descriptions short - just the method name
- Await simple numeric selection
**Present the numbered list (0-9) with this exact format:**
**Action List Presentation Format:**
```text
**Advanced Reflective, Elicitation & Brainstorming Actions**
Choose an action (0-9 - 9 to bypass - HELP for explanation of these options):
**Advanced Elicitation Options**
Choose a number (0-8) or 9 to proceed:
0. Expand or Contract for Audience
1. Explain Reasoning (CoT Step-by-Step)
2. Critique and Refine
3. Analyze Logical Flow and Dependencies
4. Assess Alignment with Overall Goals
5. Identify Potential Risks and Unforeseen Issues
6. Challenge from Critical Perspective (Self or Other Persona)
7. Explore Diverse Alternatives (ToT-Inspired)
8. Hindsight is 20/20: The 'If Only...' Reflection
0. [Method Name]
1. [Method Name]
2. [Method Name]
3. [Method Name]
4. [Method Name]
5. [Method Name]
6. [Method Name]
7. [Method Name]
8. [Method Name]
9. Proceed / No Further Actions
```
### 2. Processing Guidelines
**Response Handling:**
**Do NOT show:**
- **Numbers 0-8**: Execute the selected method, then re-offer the choice
- **Number 9**: Proceed to next section or continue conversation
- **Direct Feedback**: Apply user's suggested changes and continue
- The full protocol text with `[[LLM: ...]]` instructions
- Detailed explanations of each option unless executing or the user asks, when giving the definition you can modify to tie its relevance
- Any internal template markup
### 4. Method Execution Framework
**After user selection from the list:**
**Execution Process:**
- Execute the chosen action according to the protocol instructions below
- Ask if they want to select another action or proceed with option 9 once complete
- Continue until user selects option 9 or indicates completion
1. **Retrieve Method**: Access the specific elicitation method from the elicitation-methods data file
2. **Apply Context**: Execute the method from your current role's perspective
3. **Provide Results**: Deliver insights, critiques, or alternatives relevant to the content
4. **Re-offer Choice**: Present the same 9 options again until user selects 9 or gives direct feedback
## Action Definitions
**Execution Guidelines:**
0. Expand or Contract for Audience
[[LLM: Ask the user whether they want to 'expand' on the content (add more detail, elaborate) or 'contract' it (simplify, clarify, make more concise). Also, ask if there's a specific target audience they have in mind. Once clarified, perform the expansion or contraction from your current role's perspective, tailored to the specified audience if provided.]]
1. Explain Reasoning (CoT Step-by-Step)
[[LLM: Explain the step-by-step thinking process, characteristic of your role, that you used to arrive at the current proposal for this content.]]
2. Critique and Refine
[[LLM: From your current role's perspective, review your last output or the current section for flaws, inconsistencies, or areas for improvement, and then suggest a refined version reflecting your expertise.]]
3. Analyze Logical Flow and Dependencies
[[LLM: From your role's standpoint, examine the content's structure for logical progression, internal consistency, and any relevant dependencies. Confirm if elements are presented in an effective order.]]
4. Assess Alignment with Overall Goals
[[LLM: Evaluate how well the current content contributes to the stated overall goals of the document, interpreting this from your specific role's perspective and identifying any misalignments you perceive.]]
5. Identify Potential Risks and Unforeseen Issues
[[LLM: Based on your role's expertise, brainstorm potential risks, overlooked edge cases, or unintended consequences related to the current content or proposal.]]
6. Challenge from Critical Perspective (Self or Other Persona)
[[LLM: Adopt a critical perspective on the current content. If the user specifies another role or persona (e.g., 'as a customer', 'as [Another Persona Name]'), critique the content or play devil's advocate from that specified viewpoint. If no other role is specified, play devil's advocate from your own current persona's viewpoint, arguing against the proposal or current content and highlighting weaknesses or counterarguments specific to your concerns. This can also randomly include YAGNI when appropriate, such as when trimming the scope of an MVP, the perspective might challenge the need for something to cut MVP scope.]]
7. Explore Diverse Alternatives (ToT-Inspired)
[[LLM: From your role's perspective, first broadly brainstorm a range of diverse approaches or solutions to the current topic. Then, from this wider exploration, select and present 2 distinct alternatives, detailing the pros, cons, and potential implications you foresee for each.]]
8. Hindsight is 20/20: The 'If Only...' Reflection
[[LLM: In your current persona, imagine it's a retrospective for a project based on the current content. What's the one 'if only we had known/done X...' that your role would humorously or dramatically highlight, along with the imagined consequences?]]
9. Proceed / No Further Actions
[[LLM: Acknowledge the user's choice to finalize the current work, accept the AI's last output as is, or move on to the next step without selecting another action from this list. Prepare to proceed accordingly.]]
- **Be Concise**: Focus on actionable insights, not lengthy explanations
- **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
- **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
- **Maintain Flow**: Keep the process moving efficiently
==================== END: tasks#advanced-elicitation ====================
==================== START: tasks#create-doc ====================
@@ -1018,13 +1043,15 @@ BMad transforms you into a "Vibe CEO" - directing a team of specialized AI agent
### The Two-Phase Approach
**Phase 1: Planning (Web UI - Cost Effective)**
#### Phase 1: Planning (Web UI - Cost Effective)
- Use large context windows (Gemini's 1M tokens)
- Generate comprehensive documents (PRD, Architecture)
- Leverage multiple agents for brainstorming
- Create once, use throughout development
**Phase 2: Development (IDE - Implementation)**
#### Phase 2: Development (IDE - Implementation)
- Shard documents into manageable pieces
- Execute focused SM → Dev cycles
- One story at a time, sequential progress
@@ -1054,6 +1081,7 @@ BMad transforms you into a "Vibe CEO" - directing a team of specialized AI agent
### Quick Start Options
#### Option 1: Web UI
**Best for**: ChatGPT, Claude, Gemini users who want to start immediately
1. Navigate to `dist/teams/`
@@ -1063,6 +1091,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, Trae, Cline, Roo Code, Github Copilot users
```bash
@@ -1071,6 +1100,7 @@ npx bmad-method install
```
**Installation Steps**:
- Choose "Complete installation"
- Select your IDE from supported options:
- **Cursor**: Native AI integration
@@ -1084,6 +1114,7 @@ npx bmad-method install
**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.
**Verify Installation**:
- `.bmad-core/` folder created with all agents
- IDE-specific integration files created
- All agent commands/rules/modes available
@@ -1093,12 +1124,14 @@ npx bmad-method install
### Environment Selection Guide
**Use Web UI for**:
- Initial planning and documentation (PRD, architecture)
- Cost-effective document creation (especially with Gemini)
- Brainstorming and analysis phases
- Multi-agent consultation and planning
**Use IDE for**:
- Active development and coding
- File operations and project integration
- Document sharding and story management
@@ -1111,35 +1144,41 @@ npx bmad-method install
**Can you do everything in IDE?** Yes, but understand the tradeoffs:
**Pros of IDE-Only**:
- Single environment workflow
- Direct file operations from start
- No copy/paste between environments
- Immediate project integration
**Cons of IDE-Only**:
- Higher token costs for large document creation
- Smaller context windows (varies by IDE/model)
- May hit limits during planning phases
- Less cost-effective for brainstorming
**Using Web Agents in IDE**:
- **NOT RECOMMENDED**: Web agents (PM, Architect) have rich dependencies designed for large contexts
- **Why it matters**: Dev agents are kept lean to maximize coding context
- **The principle**: "Dev agents code, planning agents plan" - mixing breaks this optimization
**About bmad-master and bmad-orchestrator**:
- **bmad-master**: CAN do any task without switching agents, BUT...
- **Still use specialized agents for planning**: PM, Architect, and UX Expert have tuned personas that produce better results
- **Why specialization matters**: Each agent's personality and focus creates higher quality outputs
- **If using bmad-master/orchestrator**: Fine for planning phases, but...
**CRITICAL RULE for Development**:
- **ALWAYS use SM agent for story creation** - Never use bmad-master/orchestrator
- **ALWAYS use Dev agent for implementation** - Never use bmad-master/orchestrator
- **Why this matters**: SM and Dev agents are specifically optimized for the development workflow
- **No exceptions**: Even if using bmad-master for everything else, switch to SM → Dev for implementation
**Best Practice for IDE-Only**:
1. Use PM/Architect/UX agents for planning (better than bmad-master)
2. Create documents directly in project
3. Shard immediately after creation
@@ -1163,17 +1202,20 @@ This configuration file acts as a map for BMad agents, telling them exactly wher
### Key Configuration Areas
#### PRD Configuration
- **prdVersion**: Tells agents if PRD follows v3 or v4 conventions
- **prdSharded**: Whether epics are embedded (false) or in separate files (true)
- **prdShardedLocation**: Where to find sharded epic files
- **epicFilePattern**: Pattern for epic filenames (e.g., `epic-{n}*.md`)
#### Architecture Configuration
- **architectureVersion**: v3 (monolithic) or v4 (sharded)
- **architectureSharded**: Whether architecture is split into components
- **architectureShardedLocation**: Where sharded architecture files live
#### Developer Files
- **devLoadAlwaysFiles**: List of files the dev agent loads for every task
- **devDebugLog**: Where dev agent logs repeated failures
- **agentCoreDump**: Export location for chat conversations
@@ -1188,6 +1230,7 @@ This configuration file acts as a map for BMad agents, telling them exactly wher
### Common Configurations
**Legacy V3 Project**:
```yaml
prdVersion: v3
prdSharded: false
@@ -1196,6 +1239,7 @@ architectureSharded: false
```
**V4 Optimized Project**:
```yaml
prdVersion: v4
prdSharded: true
@@ -1261,6 +1305,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
#### IDE-Specific Syntax
**Agent Loading by IDE**:
- **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
- **Cursor**: `@agent-name` (e.g., `@bmad-master`)
- **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
@@ -1269,10 +1314,12 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
- **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 Guidelines**:
- **Claude Code, Cursor, Windsurf, Trae**: Start new chats when switching agents
- **Roo Code**: Switch modes within the same conversation
**Common Task Commands**:
- `*help` - Show available commands
- `*status` - Show current context/progress
- `*exit` - Exit the agent mode
@@ -1281,6 +1328,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
- `*create` - Run create-next-story task (SM agent)
**In Web UI**:
```text
/pm create-doc prd
/architect review system design
@@ -1294,16 +1342,19 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
### Pre-Built Teams
#### Team All
- **Includes**: All 10 agents + orchestrator
- **Use Case**: Complete projects requiring all roles
- **Bundle**: `team-all.txt`
#### Team Fullstack
- **Includes**: PM, Architect, Developer, QA, UX Expert
- **Use Case**: End-to-end web/mobile development
- **Bundle**: `team-fullstack.txt`
#### Team No-UI
- **Includes**: PM, Architect, Developer, QA (no UX Expert)
- **Use Case**: Backend services, APIs, system development
- **Bundle**: `team-no-ui.txt`
@@ -1317,22 +1368,26 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor
### Key Architectural Components
#### 1. Agents (`bmad-core/agents/`)
- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
- **Startup Instructions**: Can load project-specific documentation for immediate context
#### 2. Agent Teams (`bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`)
- **Purpose**: YAML files defining prescribed sequences of steps for specific project types
- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
- **Structure**: Defines agent interactions, artifacts created, and transition conditions
#### 4. Reusable Resources
- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review
@@ -1372,6 +1427,7 @@ BMad employs a sophisticated template system with three key components:
### Technical Preferences Integration
The `technical-preferences.md` file serves as a persistent technical profile that:
- Ensures consistency across all agents and projects
- Eliminates repetitive technology specification
- Provides personalized recommendations aligned with user preferences
@@ -1380,6 +1436,7 @@ The `technical-preferences.md` file serves as a persistent technical profile tha
### Build and Delivery Process
The `web-builder.js` tool creates web-ready bundles by:
1. Reading agent or team definition files
2. Recursively resolving all dependencies
3. Concatenating content into single text files with clear separators
@@ -1394,11 +1451,13 @@ This architecture enables seamless operation across environments while maintaini
**Ideal for cost efficiency with Gemini's massive context:**
**For Brownfield Projects - Start Here!**:
1. **Upload entire project to Gemini Web** (GitHub URL, files, or zip)
2. **Document existing system**: `/analyst` → `*document-project`
3. **Creates comprehensive docs** from entire codebase analysis
**For All Projects**:
1. **Optional Analysis**: `/analyst` - Market research, competitive analysis
2. **Project Brief**: Create foundation document (Analyst or user)
3. **PRD Creation**: `/pm create-doc prd` - Comprehensive product requirements
@@ -1409,12 +1468,14 @@ This architecture enables seamless operation across environments while maintaini
#### Example Planning Prompts
**For PRD Creation**:
```text
"I want to build a [type] application that [core purpose].
Help me brainstorm features and create a comprehensive PRD."
```
**For Architecture Design**:
```text
"Based on this PRD, design a scalable technical architecture
that can handle [specific requirements]."
@@ -1432,7 +1493,7 @@ that can handle [specific requirements]."
**Prerequisites**: Planning documents must exist in `docs/` folder
1. **Document Sharding** (CRITICAL STEP):
1. **Document Sharding** (CRITICAL STEP):
- Documents created by PM/Architect (in Web or IDE) MUST be sharded for development
- Two methods to shard:
a) **Manual**: Drag `shard-doc` task + document file into chat
@@ -1446,32 +1507,33 @@ that can handle [specific requirements]."
- Source tree document and coding standards for dev agent reference
- Sharded docs for SM agent story creation
**Resulting Folder Structure**:
Resulting Folder Structure:
- `docs/prd/` - Broken down PRD sections
- `docs/architecture/` - Broken down architecture sections
- `docs/stories/` - Generated user stories
3. **Development Cycle** (Sequential, one story at a time):
1. **Development Cycle** (Sequential, one story at a time):
**CRITICAL CONTEXT MANAGEMENT**:
- **Context windows matter!** Always use fresh, clean context windows
- **Model selection matters!** Use most powerful thinking model for SM story creation
- **ALWAYS start new chat between SM, Dev, and QA work**
**Step 1 - Story Creation**:
**Step 1 - Story Creation**:
- **NEW CLEAN CHAT** → Select powerful model → `@sm` → `*create`
- SM executes create-next-story task
- Review generated story in `docs/stories/`
- Update status from "Draft" to "Approved"
**Step 2 - Story Implementation**:
**Step 2 - Story Implementation**:
- **NEW CLEAN CHAT** → `@dev`
- Agent asks which story to implement
- Include story file content to save dev agent lookup time
- Dev follows tasks/subtasks, marking completion
- Dev maintains File List of all changes
- Dev marks story as "Review" when complete with all tests passing
**Step 3 - Senior QA Review**:
- **NEW CLEAN CHAT** → `@qa` → execute review-story task
- QA performs senior developer code review
@@ -1479,7 +1541,7 @@ that can handle [specific requirements]."
- QA appends results to story's QA Results section
- If approved: Status → "Done"
- If changes needed: Status stays "Review" with unchecked items for dev
**Step 4 - Repeat**: Continue SM → Dev → QA cycle until all epic stories complete
**Important**: Only 1 story in progress at a time, worked sequentially until all epic stories complete.
@@ -1487,6 +1549,7 @@ that can handle [specific requirements]."
### Status Tracking Workflow
Stories progress through defined statuses:
- **Draft** → **Approved** → **InProgress** → **Done**
Each status change requires user verification and approval before proceeding.
@@ -1494,6 +1557,7 @@ Each status change requires user verification and approval before proceeding.
### Workflow Types
#### Greenfield Development
- Business analysis and market research
- Product requirements and feature definition
- System architecture and design
@@ -1507,6 +1571,7 @@ Each status change requires user verification and approval before proceeding.
**Complete Brownfield Workflow Options**:
**Option 1: PRD-First (Recommended for Large Codebases/Monorepos)**:
1. **Upload project to Gemini Web** (GitHub URL, files, or zip)
2. **Create PRD first**: `@pm` → `*create-doc brownfield-prd`
3. **Focused documentation**: `@analyst` → `*document-project`
@@ -1517,18 +1582,19 @@ Each status change requires user verification and approval before proceeding.
- Avoids bloating docs with unused code
**Option 2: Document-First (Good for Smaller Projects)**:
1. **Upload project to Gemini Web**
2. **Document everything**: `@analyst` → `*document-project`
3. **Then create PRD**: `@pm` → `*create-doc brownfield-prd`
- More thorough but can create excessive documentation
2. **Requirements Gathering**:
4. **Requirements Gathering**:
- **Brownfield PRD**: Use PM agent with `brownfield-prd-tmpl`
- **Analyzes**: Existing system, constraints, integration points
- **Defines**: Enhancement scope, compatibility requirements, risk assessment
- **Creates**: Epic and story structure for changes
3. **Architecture Planning**:
5. **Architecture Planning**:
- **Brownfield Architecture**: Use Architect agent with `brownfield-architecture-tmpl`
- **Integration Strategy**: How new features integrate with existing system
- **Migration Planning**: Gradual rollout and backwards compatibility
@@ -1537,10 +1603,12 @@ Each status change requires user verification and approval before proceeding.
**Brownfield-Specific Resources**:
**Templates**:
- `brownfield-prd-tmpl.md`: Comprehensive enhancement planning with existing system analysis
- `brownfield-architecture-tmpl.md`: Integration-focused architecture for existing systems
**Tasks**:
- `document-project`: Generates comprehensive documentation from existing codebase
- `brownfield-create-epic`: Creates single epic for focused enhancements (when full PRD is overkill)
- `brownfield-create-story`: Creates individual story for small, isolated changes
@@ -1548,18 +1616,21 @@ Each status change requires user verification and approval before proceeding.
**When to Use Each Approach**:
**Full Brownfield Workflow** (Recommended for):
- Major feature additions
- System modernization
- Complex integrations
- Multiple related changes
**Quick Epic/Story Creation** (Use when):
- Single, focused enhancement
- Isolated bug fixes
- Small feature additions
- Well-documented existing system
**Critical Success Factors**:
1. **Documentation First**: Always run `document-project` if docs are outdated/missing
2. **Context Matters**: Provide agents access to relevant code sections
3. **Integration Focus**: Emphasize compatibility and non-breaking changes
@@ -1575,6 +1646,7 @@ Each status change requires user verification and approval before proceeding.
- `docs/architecture.md` - System Architecture Document
**Why These Names Matter**:
- Agents automatically reference these files during development
- Sharding tasks expect these specific filenames
- Workflow automation depends on standard naming
@@ -1593,6 +1665,7 @@ Each status change requires user verification and approval before proceeding.
Templates with Level 2 headings (`##`) can be automatically sharded:
**Original PRD**:
```markdown
## Goals and Background Context
## Requirements
@@ -1601,6 +1674,7 @@ Templates with Level 2 headings (`##`) can be automatically sharded:
```
**After Sharding**:
- `docs/prd/goals-and-background-context.md`
- `docs/prd/requirements.md`
- `docs/prd/user-interface-design-goals.md`
@@ -1613,12 +1687,14 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
### Environment-Specific Usage
**Web UI Best For**:
- Initial planning and documentation phases
- Cost-effective large document creation
- Agent consultation and brainstorming
- Multi-agent workflows with orchestrator
**IDE Best For**:
- Active development and implementation
- File operations and project integration
- Story management and development cycles
@@ -1653,6 +1729,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
For full details, see `CONTRIBUTING.md`. Key points:
**Fork Workflow**:
1. Fork the repository
2. Create feature branches
3. Submit PRs to `next` branch (default) or `main` for critical fixes only
@@ -1660,12 +1737,14 @@ For full details, see `CONTRIBUTING.md`. Key points:
5. One feature/fix per PR
**PR Requirements**:
- Clear descriptions (max 200 words) with What/Why/How/Testing
- Use conventional commits (feat:, fix:, docs:)
- Atomic commits - one logical change per commit
- Must align with guiding principles
**Core Principles** (from GUIDING-PRINCIPLES.md):
- **Dev Agents Must Be Lean**: Minimize dependencies, save context for code
- **Natural Language First**: Everything in markdown, no code in core
- **Core vs Expansion Packs**: Core for universal needs, packs for specialized domains
@@ -1687,12 +1766,14 @@ Expansion packs extend BMad-Method beyond traditional software development into
### Available Expansion Packs
**Technical Packs**:
- **Infrastructure/DevOps**: Cloud architects, SRE experts, security specialists
- **Game Development**: Game designers, level designers, narrative writers
- **Mobile Development**: iOS/Android specialists, mobile UX experts
- **Data Science**: ML engineers, data scientists, visualization experts
**Non-Technical Packs**:
- **Business Strategy**: Consultants, financial analysts, marketing strategists
- **Creative Writing**: Plot architects, character developers, world builders
- **Health & Wellness**: Fitness trainers, nutritionists, habit engineers
@@ -1700,6 +1781,7 @@ Expansion packs extend BMad-Method beyond traditional software development into
- **Legal Support**: Contract analysts, compliance checkers
**Specialty Packs**:
- **Expansion Creator**: Tools to build your own expansion packs
- **RPG Game Master**: Tabletop gaming assistance
- **Life Event Planning**: Wedding planners, event coordinators
@@ -1709,11 +1791,13 @@ Expansion packs extend BMad-Method beyond traditional software development into
1. **Browse Available Packs**: Check `expansion-packs/` directory
2. **Get Inspiration**: See `docs/expansion-packs.md` for detailed examples and ideas
3. **Install via CLI**:
3. **Install via CLI**:
```bash
npx bmad-method install
# Select "Install expansion pack" option
```
4. **Use in Your Workflow**: Installed packs integrate seamlessly with existing agents
### Creating Custom Expansion Packs
@@ -1747,14 +1831,10 @@ Provides utilities for agents and tasks to interact with workflow plans, check p
### 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.yaml for custom plan location
3. Return plan status (exists/not exists)
```
2. Return plan status to user (exists/not exists) - if not exists then HALT.
### 2. Parse Plan Status
@@ -1795,7 +1875,7 @@ Check for workflow plan:
**Warning Templates:**
```
```text
SEQUENCE WARNING:
The workflow plan shows you should complete "{expected_step}" next.
You're attempting to: "{requested_action}"
@@ -1829,7 +1909,7 @@ In flexible mode: Allow with confirmation
**For Agents (startup sequence)**:
```
```text
1. Check if plan exists using this utility
2. If exists:
- Parse current status
@@ -1840,7 +1920,7 @@ In flexible mode: Allow with confirmation
**For Tasks (pre-execution)**:
```
```text
1. Check if plan exists
2. If exists:
- Verify this task aligns with plan
@@ -1856,7 +1936,7 @@ In flexible mode: Allow with confirmation
[[LLM: Standard format for showing plan status]]
```
```text
📋 Workflow Plan Status
━━━━━━━━━━━━━━━━━━━━
Workflow: {workflow_name}
@@ -1909,7 +1989,7 @@ If user wants to abandon plan:
### Example 1: Agent Startup Check
```
```text
BMad Master starting...
[Check for plan]
@@ -1923,7 +2003,7 @@ Use *agent pm to switch, or *plan-status to see full progress.
### Example 2: Task Sequence Warning
```
```text
User: *task create-next-story
[Plan check triggered]
@@ -1939,7 +2019,7 @@ Would you like to:
### Example 3: Automatic Plan Update
```
```text
[After completing create-doc task for PRD]
✅ Plan Updated: Marked "Create PRD" as complete