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

installer updates part 1

Browse Source
This commit is contained in:
Brian Madison
2025-06-27 23:38:34 -05:00
parent 6cdecec61f
commit 1ea367619a
38 changed files with 569 additions and 2332 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
dist/agents/analyst.txt vendored
View File

@@ -681,9 +681,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules

12
dist/agents/architect.txt vendored
View File

@@ -136,9 +136,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules
@@ -808,13 +808,9 @@ Apply the advanced elicitation task after major sections to refine based on user
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Context
The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
## Instructions
@@ -823,7 +819,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from bmad-core/checklists/
- Load the appropriate checklist from {root}/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder

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

@@ -788,83 +788,6 @@ The story creation is successful when:
- Stories should take no more than 4 hours of focused development work
==================== END: tasks#brownfield-create-story ====================
==================== START: tasks#core-dump ====================
# Core Dump Task
## Purpose
To create a concise memory recording file (`.ai/core-dump-n.md`) that captures the essential context of the current agent session, enabling seamless continuation of work in future agent sessions. This task ensures persistent context across agent conversations while maintaining minimal token usage for efficient context loading.
## Inputs for this Task
- Current session conversation history and accomplishments
- Files created, modified, or deleted during the session
- Key decisions made and procedures followed
- Current project state and next logical steps
- User requests and agent responses that shaped the session
## Task Execution Instructions
### 0. Check Existing Core Dump
Before proceeding, check if `.ai/core-dump.md` already exists:
- If file exists, ask user: "Core dump file exists. Should I: 1. Overwrite, 2. Update, 3. Append or 4. Create new?"
- **Overwrite**: Replace entire file with new content
- **Update**: Merge new session info with existing content, updating relevant sections
- **Append**: Add new session as a separate entry while preserving existing content
- **Create New**: Create a new file, appending the next possible -# to the file, such as core-dump-3.md if 1 and 2 already exist.
- If file doesn't exist, proceed with creation of `core-dump-1.md`
### 1. Analyze Session Context
- Review the entire conversation to identify key accomplishments
- Note any specific tasks, procedures, or workflows that were executed
- Identify important decisions made or problems solved
- Capture the user's working style and preferences observed during the session
### 2. Document What Was Accomplished
- **Primary Actions**: List the main tasks completed concisely
- **Story Progress**: For story work, use format "Tasks Complete: 1-6, 8. Next Task Pending: 7, 9"
- **Problem Solving**: Document any challenges encountered and how they were resolved
- **User Communications**: Summarize key user requests, preferences, and discussion points
### 3. Record File System Changes (Concise Format)
- **Files Created**: `filename.ext` (brief purpose/size)
- **Files Modified**: `filename.ext` (what changed)
- **Files Deleted**: `filename.ext` (why removed)
- Focus on essential details, avoid verbose descriptions
### 4. Capture Current Project State
- **Project Progress**: Where the project stands after this session
- **Current Issues**: Any blockers or problems that need resolution
- **Next Logical Steps**: What would be the natural next actions to take
### 5. Create/Update Core Dump File
Based on user's choice from step 0, handle the file accordingly:
### 6. Optimize for Minimal Context
- Keep descriptions concise but informative
- Use abbreviated formats where possible (file sizes, task numbers)
- Focus on actionable information rather than detailed explanations
- Avoid redundant information that can be found in project documentation
- Prioritize information that would be lost without this recording
- Ensure the file can be quickly scanned and understood
### 7. Validate Completeness
- Verify all significant session activities are captured
- Ensure a future agent could understand the current state
- Check that file changes are accurately recorded
- Confirm next steps are clear and actionable
- Verify user communication style and preferences are noted
==================== END: tasks#core-dump ====================
==================== START: tasks#correct-course ====================
# Correct Course Task
@@ -1279,9 +1202,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules
@@ -1902,13 +1825,9 @@ Provide a summary to the user including:
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Context
The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
## Instructions
@@ -1917,7 +1836,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from bmad-core/checklists/
- Load the appropriate checklist from {root}/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder
@@ -9187,225 +9106,71 @@ Templates in the BMAD method use standardized markup for AI processing. These co
==================== START: utils#workflow-management ====================
# Workflow Management
This utility enables the BMAD orchestrator to manage and execute team workflows.
Enables BMAD orchestrator to manage and execute team workflows.
## Important: Dynamic Workflow Loading
## Dynamic Workflow Loading
The BMAD orchestrator MUST read the available workflows from the current team configuration's `workflows` field. Do not use hardcoded workflow lists. Each team bundle defines its own set of supported workflows based on the agents it includes.
Read available workflows from current team configuration's `workflows` field. Each team bundle defines its own supported workflows.
**Critical Distinction**:
**Key Commands**:
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
- Use `/agent-list` to show agents in the current bundle
- Use `/workflows` to show workflows in the current bundle, NOT any creation tasks
### Workflow Descriptions
When displaying workflows, use these descriptions based on the workflow ID:
- **greenfield-fullstack**: Build a new full-stack application from concept to development
- **brownfield-fullstack**: Enhance an existing full-stack application with new features
- **greenfield-service**: Build a new backend service or API from concept to development
- **brownfield-service**: Enhance an existing backend service or API
- **greenfield-ui**: Build a new frontend/UI application from concept to development
- **brownfield-ui**: Enhance an existing frontend/UI application
- `/workflows` - List workflows in current bundle or workflows folder
- `/agent-list` - Show agents in current bundle
## Workflow Commands
### /workflows
Lists all available workflows for the current team. The available workflows are determined by the team configuration and may include workflows such as:
- greenfield-fullstack
- brownfield-fullstack
- greenfield-service
- brownfield-service
- greenfield-ui
- brownfield-ui
The actual list depends on which team bundle is loaded. When responding to this command, display the workflows that are configured in the current team's `workflows` field.
Example response format:
```text
Available workflows for [Team Name]:
1. [workflow-id] - [Brief description based on workflow type]
2. [workflow-id] - [Brief description based on workflow type]
[... etc. ...]
Use /workflow-start {number or id} to begin a workflow.
```
Lists available workflows with titles and descriptions.
### /workflow-start {workflow-id}
Starts a specific workflow and transitions to the first agent.
Example: `/workflow-start greenfield-fullstack`
Starts workflow and transitions to first agent.
### /workflow-status
Shows current workflow progress, completed artifacts, and next steps.
Example response:
```text
Current Workflow: Greenfield Full-Stack Development
Stage: Product Planning (2 of 6)
Completed:
✓ Discovery & Requirements
- project-brief (completed by Mary)
In Progress:
⚡ Product Planning
- Create PRD (John) - awaiting input
Next: Technical Architecture
```
Shows current progress, completed artifacts, and next steps.
### /workflow-resume
Resumes a workflow from where it left off, useful when starting a new chat.
User can provide completed artifacts:
```text
User: /workflow-resume greenfield-fullstack
I have completed: project-brief, PRD
BMad: I see you've completed Discovery and part of Product Planning.
Based on the greenfield-fullstack workflow, the next step is:
- UX Strategy with Sally (ux-expert)
Would you like me to load Sally to continue?
```
Resumes workflow from last position. User can provide completed artifacts.
### /workflow-next
Shows the next recommended agent and action in the current workflow.
Shows next recommended agent and action.
## Workflow Execution Flow
## Execution Flow
### 1. Starting a Workflow
1. **Starting**: Load definition → Identify first stage → Transition to agent → Guide artifact creation
When a workflow is started:
2. **Stage Transitions**: Mark complete → Check conditions → Load next agent → Pass artifacts
1. Load the workflow definition
2. Identify the first stage and step
3. Transition to the required agent
4. Provide context about expected inputs/outputs
5. Guide artifact creation
3. **Artifact Tracking**: Track status, creator, timestamps in workflow_state
### 2. Stage Transitions
4. **Interruption Handling**: Analyze provided artifacts → Determine position → Suggest next step
After each artifact is completed:
## Context Passing
1. Mark the step as complete
2. Check transition conditions
3. If stage is complete, move to next stage
4. Load the appropriate agent
5. Pass relevant artifacts as context
When transitioning, pass:
### 3. Artifact Tracking
Track all created artifacts:
```yaml
workflow_state:
current_workflow: greenfield-fullstack
current_stage: planning
current_step: 2
artifacts:
project-brief:
status: completed
created_by: analyst
timestamp: 2024-01-15T10:30:00.000Z
prd:
status: in-progress
created_by: pm
started: 2024-01-15T11:00:00.000Z
```
### 4. Workflow Interruption Handling
When user returns after interruption:
1. Ask if continuing previous workflow
2. Request any completed artifacts
3. Analyze provided artifacts
4. Determine workflow position
5. Suggest next appropriate step
Example:
```text
User: I'm working on a new app. Here's my PRD and architecture doc.
BMad: I see you have a PRD and architecture document. Based on these artifacts,
it looks like you're following the greenfield-fullstack workflow and have completed
stages 1-3. The next recommended step would be:
Stage 4: Validation & Refinement
- Load Sarah (Product Owner) to validate all artifacts
Would you like to continue with this workflow?
```
## Workflow Context Passing
When transitioning between agents, pass:
1. Previous artifacts created
2. Current workflow stage
3. Expected outputs
4. Any decisions or constraints identified
Example transition:
```text
BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
the next step is UX Strategy with Sally.
/ux-expert
Sally: I see we're in the Product Planning stage of the greenfield-fullstack workflow.
I have access to:
- Project Brief from Mary
- PRD from John
Let's create the UX strategy and UI specifications. First, let me review
the PRD to understand the features we're designing for...
```
- Previous artifacts
- Current workflow stage
- Expected outputs
- Decisions/constraints
## Multi-Path Workflows
Some workflows may have multiple paths:
Handle conditional paths by asking clarifying questions when needed.
```yaml
conditional_paths:
- condition: project_type == 'mobile'
next_stage: mobile-specific-design
- condition: project_type == 'web'
next_stage: web-architecture
- default: fullstack-architecture
```
## Best Practices
Handle these by asking clarifying questions when needed.
1. Show progress
2. Explain transitions
3. Preserve context
4. Allow flexibility
5. Track state
## Workflow Best Practices
## Agent Integration
1. **Always show progress** - Users should know where they are
2. **Explain transitions** - Why moving to next agent
3. **Preserve context** - Pass relevant information forward
4. **Allow flexibility** - Users can skip or modify steps
5. **Track everything** - Maintain complete workflow state
## Integration with Agents
Each agent should be workflow-aware:
- Know which workflow is active
- Understand their role in the workflow
- Access previous artifacts
- Know expected outputs
- Guide toward workflow goals
This creates a seamless experience where the entire team works together toward the workflow's objectives.
Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
==================== END: utils#workflow-management ====================

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

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

8
dist/agents/dev.txt vendored
View File

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

12
dist/agents/pm.txt vendored
View File

@@ -133,9 +133,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules
@@ -874,13 +874,9 @@ The story creation is successful when:
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Context
The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
## Instructions
@@ -889,7 +885,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from bmad-core/checklists/
- Load the appropriate checklist from {root}/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder

8
dist/agents/po.txt vendored
View File

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

8
dist/agents/sm.txt vendored
View File

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

12
dist/agents/ux-expert.txt vendored
View File

@@ -493,9 +493,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules
@@ -541,13 +541,9 @@ If template specifies a checklist:
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Context
The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
## Instructions
@@ -556,7 +552,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from bmad-core/checklists/
- Load the appropriate checklist from {root}/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder

12
dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt vendored
View File

@@ -133,9 +133,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules
@@ -181,13 +181,9 @@ If template specifies a checklist:
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Context
The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
## Instructions
@@ -196,7 +192,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from bmad-core/checklists/
- Load the appropriate checklist from {root}/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder

8
dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt vendored
View File

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

8
dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt vendored
View File

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

228
dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt vendored
View File

@@ -1006,9 +1006,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules
@@ -2638,227 +2638,73 @@ Or ask me about anything else related to BMAD-METHOD!
==================== START: utils#workflow-management ====================
# Workflow Management
This utility enables the BMAD orchestrator to manage and execute team workflows.
Enables BMAD orchestrator to manage and execute team workflows.
## Important: Dynamic Workflow Loading
## Dynamic Workflow Loading
The BMAD orchestrator MUST read the available workflows from the current team configuration's `workflows` field. Do not use hardcoded workflow lists. Each team bundle defines its own set of supported workflows based on the agents it includes.
Read available workflows from current team configuration's `workflows` field. Each team bundle defines its own supported workflows.
**Critical Distinction**:
**Key Commands**:
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
- Use `/agent-list` to show agents in the current bundle
- Use `/workflows` to show workflows in the current bundle, NOT any creation tasks
### Workflow Descriptions
When displaying workflows, use these descriptions based on the workflow ID:
- **greenfield-fullstack**: Build a new full-stack application from concept to development
- **brownfield-fullstack**: Enhance an existing full-stack application with new features
- **greenfield-service**: Build a new backend service or API from concept to development
- **brownfield-service**: Enhance an existing backend service or API
- **greenfield-ui**: Build a new frontend/UI application from concept to development
- **brownfield-ui**: Enhance an existing frontend/UI application
- `/workflows` - List workflows in current bundle or workflows folder
- `/agent-list` - Show agents in current bundle
## Workflow Commands
### /workflows
Lists all available workflows for the current team. The available workflows are determined by the team configuration and may include workflows such as:
- greenfield-fullstack
- brownfield-fullstack
- greenfield-service
- brownfield-service
- greenfield-ui
- brownfield-ui
The actual list depends on which team bundle is loaded. When responding to this command, display the workflows that are configured in the current team's `workflows` field.
Example response format:
```text
Available workflows for [Team Name]:
1. [workflow-id] - [Brief description based on workflow type]
2. [workflow-id] - [Brief description based on workflow type]
[... etc. ...]
Use /workflow-start {number or id} to begin a workflow.
```
Lists available workflows with titles and descriptions.
### /workflow-start {workflow-id}
Starts a specific workflow and transitions to the first agent.
Example: `/workflow-start greenfield-fullstack`
Starts workflow and transitions to first agent.
### /workflow-status
Shows current workflow progress, completed artifacts, and next steps.
Example response:
```text
Current Workflow: Greenfield Full-Stack Development
Stage: Product Planning (2 of 6)
Completed:
✓ Discovery & Requirements
- project-brief (completed by Mary)
In Progress:
⚡ Product Planning
- Create PRD (John) - awaiting input
Next: Technical Architecture
```
Shows current progress, completed artifacts, and next steps.
### /workflow-resume
Resumes a workflow from where it left off, useful when starting a new chat.
User can provide completed artifacts:
```text
User: /workflow-resume greenfield-fullstack
I have completed: project-brief, PRD
BMad: I see you've completed Discovery and part of Product Planning.
Based on the greenfield-fullstack workflow, the next step is:
- UX Strategy with Sally (ux-expert)
Would you like me to load Sally to continue?
```
Resumes workflow from last position. User can provide completed artifacts.
### /workflow-next
Shows the next recommended agent and action in the current workflow.
Shows next recommended agent and action.
## Workflow Execution Flow
## Execution Flow
### 1. Starting a Workflow
1. **Starting**: Load definition → Identify first stage → Transition to agent → Guide artifact creation
When a workflow is started:
2. **Stage Transitions**: Mark complete → Check conditions → Load next agent → Pass artifacts
1. Load the workflow definition
2. Identify the first stage and step
3. Transition to the required agent
4. Provide context about expected inputs/outputs
5. Guide artifact creation
3. **Artifact Tracking**: Track status, creator, timestamps in workflow_state
### 2. Stage Transitions
4. **Interruption Handling**: Analyze provided artifacts → Determine position → Suggest next step
After each artifact is completed:
## Context Passing
1. Mark the step as complete
2. Check transition conditions
3. If stage is complete, move to next stage
4. Load the appropriate agent
5. Pass relevant artifacts as context
When transitioning, pass:
### 3. Artifact Tracking
Track all created artifacts:
```yaml
workflow_state:
current_workflow: greenfield-fullstack
current_stage: planning
current_step: 2
artifacts:
project-brief:
status: completed
created_by: analyst
timestamp: 2024-01-15T10:30:00.000Z
prd:
status: in-progress
created_by: pm
started: 2024-01-15T11:00:00.000Z
```
### 4. Workflow Interruption Handling
When user returns after interruption:
1. Ask if continuing previous workflow
2. Request any completed artifacts
3. Analyze provided artifacts
4. Determine workflow position
5. Suggest next appropriate step
Example:
```text
User: I'm working on a new app. Here's my PRD and architecture doc.
BMad: I see you have a PRD and architecture document. Based on these artifacts,
it looks like you're following the greenfield-fullstack workflow and have completed
stages 1-3. The next recommended step would be:
Stage 4: Validation & Refinement
- Load Sarah (Product Owner) to validate all artifacts
Would you like to continue with this workflow?
```
## Workflow Context Passing
When transitioning between agents, pass:
1. Previous artifacts created
2. Current workflow stage
3. Expected outputs
4. Any decisions or constraints identified
Example transition:
```text
BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
the next step is UX Strategy with Sally.
/ux-expert
Sally: I see we're in the Product Planning stage of the greenfield-fullstack workflow.
I have access to:
- Project Brief from Mary
- PRD from John
Let's create the UX strategy and UI specifications. First, let me review
the PRD to understand the features we're designing for...
```
- Previous artifacts
- Current workflow stage
- Expected outputs
- Decisions/constraints
## Multi-Path Workflows
Some workflows may have multiple paths:
Handle conditional paths by asking clarifying questions when needed.
```yaml
conditional_paths:
- condition: project_type == 'mobile'
next_stage: mobile-specific-design
- condition: project_type == 'web'
next_stage: web-architecture
- default: fullstack-architecture
```
## Best Practices
Handle these by asking clarifying questions when needed.
1. Show progress
2. Explain transitions
3. Preserve context
4. Allow flexibility
5. Track state
## Workflow Best Practices
## Agent Integration
1. **Always show progress** - Users should know where they are
2. **Explain transitions** - Why moving to next agent
3. **Preserve context** - Pass relevant information forward
4. **Allow flexibility** - Users can skip or modify steps
5. **Track everything** - Maintain complete workflow state
## Integration with Agents
Each agent should be workflow-aware:
- Know which workflow is active
- Understand their role in the workflow
- Access previous artifacts
- Know expected outputs
- Guide toward workflow goals
This creates a seamless experience where the entire team works together toward the workflow's objectives.
Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
==================== END: utils#workflow-management ====================
==================== START: tasks#execute-checklist ====================
@@ -2866,13 +2712,9 @@ This creates a seamless experience where the entire team works together toward t
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Context
The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
## Instructions
@@ -2881,7 +2723,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from bmad-core/checklists/
- Load the appropriate checklist from {root}/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder

4
dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt vendored
View File

@@ -134,9 +134,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules

228
dist/teams/team-all.txt vendored
View File

@@ -784,9 +784,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules
@@ -1653,227 +1653,73 @@ Use the **expansion-creator** pack to build your own:
==================== START: utils#workflow-management ====================
# Workflow Management
This utility enables the BMAD orchestrator to manage and execute team workflows.
Enables BMAD orchestrator to manage and execute team workflows.
## Important: Dynamic Workflow Loading
## Dynamic Workflow Loading
The BMAD orchestrator MUST read the available workflows from the current team configuration's `workflows` field. Do not use hardcoded workflow lists. Each team bundle defines its own set of supported workflows based on the agents it includes.
Read available workflows from current team configuration's `workflows` field. Each team bundle defines its own supported workflows.
**Critical Distinction**:
**Key Commands**:
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
- Use `/agent-list` to show agents in the current bundle
- Use `/workflows` to show workflows in the current bundle, NOT any creation tasks
### Workflow Descriptions
When displaying workflows, use these descriptions based on the workflow ID:
- **greenfield-fullstack**: Build a new full-stack application from concept to development
- **brownfield-fullstack**: Enhance an existing full-stack application with new features
- **greenfield-service**: Build a new backend service or API from concept to development
- **brownfield-service**: Enhance an existing backend service or API
- **greenfield-ui**: Build a new frontend/UI application from concept to development
- **brownfield-ui**: Enhance an existing frontend/UI application
- `/workflows` - List workflows in current bundle or workflows folder
- `/agent-list` - Show agents in current bundle
## Workflow Commands
### /workflows
Lists all available workflows for the current team. The available workflows are determined by the team configuration and may include workflows such as:
- greenfield-fullstack
- brownfield-fullstack
- greenfield-service
- brownfield-service
- greenfield-ui
- brownfield-ui
The actual list depends on which team bundle is loaded. When responding to this command, display the workflows that are configured in the current team's `workflows` field.
Example response format:
```text
Available workflows for [Team Name]:
1. [workflow-id] - [Brief description based on workflow type]
2. [workflow-id] - [Brief description based on workflow type]
[... etc. ...]
Use /workflow-start {number or id} to begin a workflow.
```
Lists available workflows with titles and descriptions.
### /workflow-start {workflow-id}
Starts a specific workflow and transitions to the first agent.
Example: `/workflow-start greenfield-fullstack`
Starts workflow and transitions to first agent.
### /workflow-status
Shows current workflow progress, completed artifacts, and next steps.
Example response:
```text
Current Workflow: Greenfield Full-Stack Development
Stage: Product Planning (2 of 6)
Completed:
✓ Discovery & Requirements
- project-brief (completed by Mary)
In Progress:
⚡ Product Planning
- Create PRD (John) - awaiting input
Next: Technical Architecture
```
Shows current progress, completed artifacts, and next steps.
### /workflow-resume
Resumes a workflow from where it left off, useful when starting a new chat.
User can provide completed artifacts:
```text
User: /workflow-resume greenfield-fullstack
I have completed: project-brief, PRD
BMad: I see you've completed Discovery and part of Product Planning.
Based on the greenfield-fullstack workflow, the next step is:
- UX Strategy with Sally (ux-expert)
Would you like me to load Sally to continue?
```
Resumes workflow from last position. User can provide completed artifacts.
### /workflow-next
Shows the next recommended agent and action in the current workflow.
Shows next recommended agent and action.
## Workflow Execution Flow
## Execution Flow
### 1. Starting a Workflow
1. **Starting**: Load definition → Identify first stage → Transition to agent → Guide artifact creation
When a workflow is started:
2. **Stage Transitions**: Mark complete → Check conditions → Load next agent → Pass artifacts
1. Load the workflow definition
2. Identify the first stage and step
3. Transition to the required agent
4. Provide context about expected inputs/outputs
5. Guide artifact creation
3. **Artifact Tracking**: Track status, creator, timestamps in workflow_state
### 2. Stage Transitions
4. **Interruption Handling**: Analyze provided artifacts → Determine position → Suggest next step
After each artifact is completed:
## Context Passing
1. Mark the step as complete
2. Check transition conditions
3. If stage is complete, move to next stage
4. Load the appropriate agent
5. Pass relevant artifacts as context
When transitioning, pass:
### 3. Artifact Tracking
Track all created artifacts:
```yaml
workflow_state:
current_workflow: greenfield-fullstack
current_stage: planning
current_step: 2
artifacts:
project-brief:
status: completed
created_by: analyst
timestamp: 2024-01-15T10:30:00.000Z
prd:
status: in-progress
created_by: pm
started: 2024-01-15T11:00:00.000Z
```
### 4. Workflow Interruption Handling
When user returns after interruption:
1. Ask if continuing previous workflow
2. Request any completed artifacts
3. Analyze provided artifacts
4. Determine workflow position
5. Suggest next appropriate step
Example:
```text
User: I'm working on a new app. Here's my PRD and architecture doc.
BMad: I see you have a PRD and architecture document. Based on these artifacts,
it looks like you're following the greenfield-fullstack workflow and have completed
stages 1-3. The next recommended step would be:
Stage 4: Validation & Refinement
- Load Sarah (Product Owner) to validate all artifacts
Would you like to continue with this workflow?
```
## Workflow Context Passing
When transitioning between agents, pass:
1. Previous artifacts created
2. Current workflow stage
3. Expected outputs
4. Any decisions or constraints identified
Example transition:
```text
BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
the next step is UX Strategy with Sally.
/ux-expert
Sally: I see we're in the Product Planning stage of the greenfield-fullstack workflow.
I have access to:
- Project Brief from Mary
- PRD from John
Let's create the UX strategy and UI specifications. First, let me review
the PRD to understand the features we're designing for...
```
- Previous artifacts
- Current workflow stage
- Expected outputs
- Decisions/constraints
## Multi-Path Workflows
Some workflows may have multiple paths:
Handle conditional paths by asking clarifying questions when needed.
```yaml
conditional_paths:
- condition: project_type == 'mobile'
next_stage: mobile-specific-design
- condition: project_type == 'web'
next_stage: web-architecture
- default: fullstack-architecture
```
## Best Practices
Handle these by asking clarifying questions when needed.
1. Show progress
2. Explain transitions
3. Preserve context
4. Allow flexibility
5. Track state
## Workflow Best Practices
## Agent Integration
1. **Always show progress** - Users should know where they are
2. **Explain transitions** - Why moving to next agent
3. **Preserve context** - Pass relevant information forward
4. **Allow flexibility** - Users can skip or modify steps
5. **Track everything** - Maintain complete workflow state
## Integration with Agents
Each agent should be workflow-aware:
- Know which workflow is active
- Understand their role in the workflow
- Access previous artifacts
- Know expected outputs
- Guide toward workflow goals
This creates a seamless experience where the entire team works together toward the workflow's objectives.
Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
==================== END: utils#workflow-management ====================
==================== START: utils#template-format ====================
@@ -3568,13 +3414,9 @@ These replace the standard elicitation options when working on competitive analy
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Context
The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
## Instructions
@@ -3583,7 +3425,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from bmad-core/checklists/
- Load the appropriate checklist from {root}/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder

228
dist/teams/team-fullstack.txt vendored
View File

@@ -628,9 +628,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules
@@ -1497,227 +1497,73 @@ Use the **expansion-creator** pack to build your own:
==================== START: utils#workflow-management ====================
# Workflow Management
This utility enables the BMAD orchestrator to manage and execute team workflows.
Enables BMAD orchestrator to manage and execute team workflows.
## Important: Dynamic Workflow Loading
## Dynamic Workflow Loading
The BMAD orchestrator MUST read the available workflows from the current team configuration's `workflows` field. Do not use hardcoded workflow lists. Each team bundle defines its own set of supported workflows based on the agents it includes.
Read available workflows from current team configuration's `workflows` field. Each team bundle defines its own supported workflows.
**Critical Distinction**:
**Key Commands**:
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
- Use `/agent-list` to show agents in the current bundle
- Use `/workflows` to show workflows in the current bundle, NOT any creation tasks
### Workflow Descriptions
When displaying workflows, use these descriptions based on the workflow ID:
- **greenfield-fullstack**: Build a new full-stack application from concept to development
- **brownfield-fullstack**: Enhance an existing full-stack application with new features
- **greenfield-service**: Build a new backend service or API from concept to development
- **brownfield-service**: Enhance an existing backend service or API
- **greenfield-ui**: Build a new frontend/UI application from concept to development
- **brownfield-ui**: Enhance an existing frontend/UI application
- `/workflows` - List workflows in current bundle or workflows folder
- `/agent-list` - Show agents in current bundle
## Workflow Commands
### /workflows
Lists all available workflows for the current team. The available workflows are determined by the team configuration and may include workflows such as:
- greenfield-fullstack
- brownfield-fullstack
- greenfield-service
- brownfield-service
- greenfield-ui
- brownfield-ui
The actual list depends on which team bundle is loaded. When responding to this command, display the workflows that are configured in the current team's `workflows` field.
Example response format:
```text
Available workflows for [Team Name]:
1. [workflow-id] - [Brief description based on workflow type]
2. [workflow-id] - [Brief description based on workflow type]
[... etc. ...]
Use /workflow-start {number or id} to begin a workflow.
```
Lists available workflows with titles and descriptions.
### /workflow-start {workflow-id}
Starts a specific workflow and transitions to the first agent.
Example: `/workflow-start greenfield-fullstack`
Starts workflow and transitions to first agent.
### /workflow-status
Shows current workflow progress, completed artifacts, and next steps.
Example response:
```text
Current Workflow: Greenfield Full-Stack Development
Stage: Product Planning (2 of 6)
Completed:
✓ Discovery & Requirements
- project-brief (completed by Mary)
In Progress:
⚡ Product Planning
- Create PRD (John) - awaiting input
Next: Technical Architecture
```
Shows current progress, completed artifacts, and next steps.
### /workflow-resume
Resumes a workflow from where it left off, useful when starting a new chat.
User can provide completed artifacts:
```text
User: /workflow-resume greenfield-fullstack
I have completed: project-brief, PRD
BMad: I see you've completed Discovery and part of Product Planning.
Based on the greenfield-fullstack workflow, the next step is:
- UX Strategy with Sally (ux-expert)
Would you like me to load Sally to continue?
```
Resumes workflow from last position. User can provide completed artifacts.
### /workflow-next
Shows the next recommended agent and action in the current workflow.
Shows next recommended agent and action.
## Workflow Execution Flow
## Execution Flow
### 1. Starting a Workflow
1. **Starting**: Load definition → Identify first stage → Transition to agent → Guide artifact creation
When a workflow is started:
2. **Stage Transitions**: Mark complete → Check conditions → Load next agent → Pass artifacts
1. Load the workflow definition
2. Identify the first stage and step
3. Transition to the required agent
4. Provide context about expected inputs/outputs
5. Guide artifact creation
3. **Artifact Tracking**: Track status, creator, timestamps in workflow_state
### 2. Stage Transitions
4. **Interruption Handling**: Analyze provided artifacts → Determine position → Suggest next step
After each artifact is completed:
## Context Passing
1. Mark the step as complete
2. Check transition conditions
3. If stage is complete, move to next stage
4. Load the appropriate agent
5. Pass relevant artifacts as context
When transitioning, pass:
### 3. Artifact Tracking
Track all created artifacts:
```yaml
workflow_state:
current_workflow: greenfield-fullstack
current_stage: planning
current_step: 2
artifacts:
project-brief:
status: completed
created_by: analyst
timestamp: 2024-01-15T10:30:00.000Z
prd:
status: in-progress
created_by: pm
started: 2024-01-15T11:00:00.000Z
```
### 4. Workflow Interruption Handling
When user returns after interruption:
1. Ask if continuing previous workflow
2. Request any completed artifacts
3. Analyze provided artifacts
4. Determine workflow position
5. Suggest next appropriate step
Example:
```text
User: I'm working on a new app. Here's my PRD and architecture doc.
BMad: I see you have a PRD and architecture document. Based on these artifacts,
it looks like you're following the greenfield-fullstack workflow and have completed
stages 1-3. The next recommended step would be:
Stage 4: Validation & Refinement
- Load Sarah (Product Owner) to validate all artifacts
Would you like to continue with this workflow?
```
## Workflow Context Passing
When transitioning between agents, pass:
1. Previous artifacts created
2. Current workflow stage
3. Expected outputs
4. Any decisions or constraints identified
Example transition:
```text
BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
the next step is UX Strategy with Sally.
/ux-expert
Sally: I see we're in the Product Planning stage of the greenfield-fullstack workflow.
I have access to:
- Project Brief from Mary
- PRD from John
Let's create the UX strategy and UI specifications. First, let me review
the PRD to understand the features we're designing for...
```
- Previous artifacts
- Current workflow stage
- Expected outputs
- Decisions/constraints
## Multi-Path Workflows
Some workflows may have multiple paths:
Handle conditional paths by asking clarifying questions when needed.
```yaml
conditional_paths:
- condition: project_type == 'mobile'
next_stage: mobile-specific-design
- condition: project_type == 'web'
next_stage: web-architecture
- default: fullstack-architecture
```
## Best Practices
Handle these by asking clarifying questions when needed.
1. Show progress
2. Explain transitions
3. Preserve context
4. Allow flexibility
5. Track state
## Workflow Best Practices
## Agent Integration
1. **Always show progress** - Users should know where they are
2. **Explain transitions** - Why moving to next agent
3. **Preserve context** - Pass relevant information forward
4. **Allow flexibility** - Users can skip or modify steps
5. **Track everything** - Maintain complete workflow state
## Integration with Agents
Each agent should be workflow-aware:
- Know which workflow is active
- Understand their role in the workflow
- Access previous artifacts
- Know expected outputs
- Guide toward workflow goals
This creates a seamless experience where the entire team works together toward the workflow's objectives.
Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
==================== END: utils#workflow-management ====================
==================== START: utils#template-format ====================
@@ -3801,13 +3647,9 @@ The story creation is successful when:
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Context
The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
## Instructions
@@ -3816,7 +3658,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from bmad-core/checklists/
- Load the appropriate checklist from {root}/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder

228
dist/teams/team-ide-minimal.txt vendored
View File

@@ -528,9 +528,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules
@@ -1397,227 +1397,73 @@ Use the **expansion-creator** pack to build your own:
==================== START: utils#workflow-management ====================
# Workflow Management
This utility enables the BMAD orchestrator to manage and execute team workflows.
Enables BMAD orchestrator to manage and execute team workflows.
## Important: Dynamic Workflow Loading
## Dynamic Workflow Loading
The BMAD orchestrator MUST read the available workflows from the current team configuration's `workflows` field. Do not use hardcoded workflow lists. Each team bundle defines its own set of supported workflows based on the agents it includes.
Read available workflows from current team configuration's `workflows` field. Each team bundle defines its own supported workflows.
**Critical Distinction**:
**Key Commands**:
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
- Use `/agent-list` to show agents in the current bundle
- Use `/workflows` to show workflows in the current bundle, NOT any creation tasks
### Workflow Descriptions
When displaying workflows, use these descriptions based on the workflow ID:
- **greenfield-fullstack**: Build a new full-stack application from concept to development
- **brownfield-fullstack**: Enhance an existing full-stack application with new features
- **greenfield-service**: Build a new backend service or API from concept to development
- **brownfield-service**: Enhance an existing backend service or API
- **greenfield-ui**: Build a new frontend/UI application from concept to development
- **brownfield-ui**: Enhance an existing frontend/UI application
- `/workflows` - List workflows in current bundle or workflows folder
- `/agent-list` - Show agents in current bundle
## Workflow Commands
### /workflows
Lists all available workflows for the current team. The available workflows are determined by the team configuration and may include workflows such as:
- greenfield-fullstack
- brownfield-fullstack
- greenfield-service
- brownfield-service
- greenfield-ui
- brownfield-ui
The actual list depends on which team bundle is loaded. When responding to this command, display the workflows that are configured in the current team's `workflows` field.
Example response format:
```text
Available workflows for [Team Name]:
1. [workflow-id] - [Brief description based on workflow type]
2. [workflow-id] - [Brief description based on workflow type]
[... etc. ...]
Use /workflow-start {number or id} to begin a workflow.
```
Lists available workflows with titles and descriptions.
### /workflow-start {workflow-id}
Starts a specific workflow and transitions to the first agent.
Example: `/workflow-start greenfield-fullstack`
Starts workflow and transitions to first agent.
### /workflow-status
Shows current workflow progress, completed artifacts, and next steps.
Example response:
```text
Current Workflow: Greenfield Full-Stack Development
Stage: Product Planning (2 of 6)
Completed:
✓ Discovery & Requirements
- project-brief (completed by Mary)
In Progress:
⚡ Product Planning
- Create PRD (John) - awaiting input
Next: Technical Architecture
```
Shows current progress, completed artifacts, and next steps.
### /workflow-resume
Resumes a workflow from where it left off, useful when starting a new chat.
User can provide completed artifacts:
```text
User: /workflow-resume greenfield-fullstack
I have completed: project-brief, PRD
BMad: I see you've completed Discovery and part of Product Planning.
Based on the greenfield-fullstack workflow, the next step is:
- UX Strategy with Sally (ux-expert)
Would you like me to load Sally to continue?
```
Resumes workflow from last position. User can provide completed artifacts.
### /workflow-next
Shows the next recommended agent and action in the current workflow.
Shows next recommended agent and action.
## Workflow Execution Flow
## Execution Flow
### 1. Starting a Workflow
1. **Starting**: Load definition → Identify first stage → Transition to agent → Guide artifact creation
When a workflow is started:
2. **Stage Transitions**: Mark complete → Check conditions → Load next agent → Pass artifacts
1. Load the workflow definition
2. Identify the first stage and step
3. Transition to the required agent
4. Provide context about expected inputs/outputs
5. Guide artifact creation
3. **Artifact Tracking**: Track status, creator, timestamps in workflow_state
### 2. Stage Transitions
4. **Interruption Handling**: Analyze provided artifacts → Determine position → Suggest next step
After each artifact is completed:
## Context Passing
1. Mark the step as complete
2. Check transition conditions
3. If stage is complete, move to next stage
4. Load the appropriate agent
5. Pass relevant artifacts as context
When transitioning, pass:
### 3. Artifact Tracking
Track all created artifacts:
```yaml
workflow_state:
current_workflow: greenfield-fullstack
current_stage: planning
current_step: 2
artifacts:
project-brief:
status: completed
created_by: analyst
timestamp: 2024-01-15T10:30:00.000Z
prd:
status: in-progress
created_by: pm
started: 2024-01-15T11:00:00.000Z
```
### 4. Workflow Interruption Handling
When user returns after interruption:
1. Ask if continuing previous workflow
2. Request any completed artifacts
3. Analyze provided artifacts
4. Determine workflow position
5. Suggest next appropriate step
Example:
```text
User: I'm working on a new app. Here's my PRD and architecture doc.
BMad: I see you have a PRD and architecture document. Based on these artifacts,
it looks like you're following the greenfield-fullstack workflow and have completed
stages 1-3. The next recommended step would be:
Stage 4: Validation & Refinement
- Load Sarah (Product Owner) to validate all artifacts
Would you like to continue with this workflow?
```
## Workflow Context Passing
When transitioning between agents, pass:
1. Previous artifacts created
2. Current workflow stage
3. Expected outputs
4. Any decisions or constraints identified
Example transition:
```text
BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
the next step is UX Strategy with Sally.
/ux-expert
Sally: I see we're in the Product Planning stage of the greenfield-fullstack workflow.
I have access to:
- Project Brief from Mary
- PRD from John
Let's create the UX strategy and UI specifications. First, let me review
the PRD to understand the features we're designing for...
```
- Previous artifacts
- Current workflow stage
- Expected outputs
- Decisions/constraints
## Multi-Path Workflows
Some workflows may have multiple paths:
Handle conditional paths by asking clarifying questions when needed.
```yaml
conditional_paths:
- condition: project_type == 'mobile'
next_stage: mobile-specific-design
- condition: project_type == 'web'
next_stage: web-architecture
- default: fullstack-architecture
```
## Best Practices
Handle these by asking clarifying questions when needed.
1. Show progress
2. Explain transitions
3. Preserve context
4. Allow flexibility
5. Track state
## Workflow Best Practices
## Agent Integration
1. **Always show progress** - Users should know where they are
2. **Explain transitions** - Why moving to next agent
3. **Preserve context** - Pass relevant information forward
4. **Allow flexibility** - Users can skip or modify steps
5. **Track everything** - Maintain complete workflow state
## Integration with Agents
Each agent should be workflow-aware:
- Know which workflow is active
- Understand their role in the workflow
- Access previous artifacts
- Know expected outputs
- Guide toward workflow goals
This creates a seamless experience where the entire team works together toward the workflow's objectives.
Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
==================== END: utils#workflow-management ====================
==================== START: utils#template-format ====================
@@ -1654,13 +1500,9 @@ Templates in the BMAD method use standardized markup for AI processing. These co
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Context
The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
## Instructions
@@ -1669,7 +1511,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from bmad-core/checklists/
- Load the appropriate checklist from {root}/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder

228
dist/teams/team-no-ui.txt vendored
View File

@@ -560,9 +560,9 @@ Confirm with the user their preferred interaction style:
### 3. Execute Template
- Load specified template from `templates#*` or the /templates directory
- Load specified template from `templates#*` or the ../templates directory
- Follow ALL embedded LLM instructions within the template
- Process template markup according to `utils#template-format` conventions
- Process template markup according to `utils#template-format` or `../utils/template-format` conventions
### 4. Template Processing Rules
@@ -1429,227 +1429,73 @@ Use the **expansion-creator** pack to build your own:
==================== START: utils#workflow-management ====================
# Workflow Management
This utility enables the BMAD orchestrator to manage and execute team workflows.
Enables BMAD orchestrator to manage and execute team workflows.
## Important: Dynamic Workflow Loading
## Dynamic Workflow Loading
The BMAD orchestrator MUST read the available workflows from the current team configuration's `workflows` field. Do not use hardcoded workflow lists. Each team bundle defines its own set of supported workflows based on the agents it includes.
Read available workflows from current team configuration's `workflows` field. Each team bundle defines its own supported workflows.
**Critical Distinction**:
**Key Commands**:
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
- Use `/agent-list` to show agents in the current bundle
- Use `/workflows` to show workflows in the current bundle, NOT any creation tasks
### Workflow Descriptions
When displaying workflows, use these descriptions based on the workflow ID:
- **greenfield-fullstack**: Build a new full-stack application from concept to development
- **brownfield-fullstack**: Enhance an existing full-stack application with new features
- **greenfield-service**: Build a new backend service or API from concept to development
- **brownfield-service**: Enhance an existing backend service or API
- **greenfield-ui**: Build a new frontend/UI application from concept to development
- **brownfield-ui**: Enhance an existing frontend/UI application
- `/workflows` - List workflows in current bundle or workflows folder
- `/agent-list` - Show agents in current bundle
## Workflow Commands
### /workflows
Lists all available workflows for the current team. The available workflows are determined by the team configuration and may include workflows such as:
- greenfield-fullstack
- brownfield-fullstack
- greenfield-service
- brownfield-service
- greenfield-ui
- brownfield-ui
The actual list depends on which team bundle is loaded. When responding to this command, display the workflows that are configured in the current team's `workflows` field.
Example response format:
```text
Available workflows for [Team Name]:
1. [workflow-id] - [Brief description based on workflow type]
2. [workflow-id] - [Brief description based on workflow type]
[... etc. ...]
Use /workflow-start {number or id} to begin a workflow.
```
Lists available workflows with titles and descriptions.
### /workflow-start {workflow-id}
Starts a specific workflow and transitions to the first agent.
Example: `/workflow-start greenfield-fullstack`
Starts workflow and transitions to first agent.
### /workflow-status
Shows current workflow progress, completed artifacts, and next steps.
Example response:
```text
Current Workflow: Greenfield Full-Stack Development
Stage: Product Planning (2 of 6)
Completed:
✓ Discovery & Requirements
- project-brief (completed by Mary)
In Progress:
⚡ Product Planning
- Create PRD (John) - awaiting input
Next: Technical Architecture
```
Shows current progress, completed artifacts, and next steps.
### /workflow-resume
Resumes a workflow from where it left off, useful when starting a new chat.
User can provide completed artifacts:
```text
User: /workflow-resume greenfield-fullstack
I have completed: project-brief, PRD
BMad: I see you've completed Discovery and part of Product Planning.
Based on the greenfield-fullstack workflow, the next step is:
- UX Strategy with Sally (ux-expert)
Would you like me to load Sally to continue?
```
Resumes workflow from last position. User can provide completed artifacts.
### /workflow-next
Shows the next recommended agent and action in the current workflow.
Shows next recommended agent and action.
## Workflow Execution Flow
## Execution Flow
### 1. Starting a Workflow
1. **Starting**: Load definition → Identify first stage → Transition to agent → Guide artifact creation
When a workflow is started:
2. **Stage Transitions**: Mark complete → Check conditions → Load next agent → Pass artifacts
1. Load the workflow definition
2. Identify the first stage and step
3. Transition to the required agent
4. Provide context about expected inputs/outputs
5. Guide artifact creation
3. **Artifact Tracking**: Track status, creator, timestamps in workflow_state
### 2. Stage Transitions
4. **Interruption Handling**: Analyze provided artifacts → Determine position → Suggest next step
After each artifact is completed:
## Context Passing
1. Mark the step as complete
2. Check transition conditions
3. If stage is complete, move to next stage
4. Load the appropriate agent
5. Pass relevant artifacts as context
When transitioning, pass:
### 3. Artifact Tracking
Track all created artifacts:
```yaml
workflow_state:
current_workflow: greenfield-fullstack
current_stage: planning
current_step: 2
artifacts:
project-brief:
status: completed
created_by: analyst
timestamp: 2024-01-15T10:30:00.000Z
prd:
status: in-progress
created_by: pm
started: 2024-01-15T11:00:00.000Z
```
### 4. Workflow Interruption Handling
When user returns after interruption:
1. Ask if continuing previous workflow
2. Request any completed artifacts
3. Analyze provided artifacts
4. Determine workflow position
5. Suggest next appropriate step
Example:
```text
User: I'm working on a new app. Here's my PRD and architecture doc.
BMad: I see you have a PRD and architecture document. Based on these artifacts,
it looks like you're following the greenfield-fullstack workflow and have completed
stages 1-3. The next recommended step would be:
Stage 4: Validation & Refinement
- Load Sarah (Product Owner) to validate all artifacts
Would you like to continue with this workflow?
```
## Workflow Context Passing
When transitioning between agents, pass:
1. Previous artifacts created
2. Current workflow stage
3. Expected outputs
4. Any decisions or constraints identified
Example transition:
```text
BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
the next step is UX Strategy with Sally.
/ux-expert
Sally: I see we're in the Product Planning stage of the greenfield-fullstack workflow.
I have access to:
- Project Brief from Mary
- PRD from John
Let's create the UX strategy and UI specifications. First, let me review
the PRD to understand the features we're designing for...
```
- Previous artifacts
- Current workflow stage
- Expected outputs
- Decisions/constraints
## Multi-Path Workflows
Some workflows may have multiple paths:
Handle conditional paths by asking clarifying questions when needed.
```yaml
conditional_paths:
- condition: project_type == 'mobile'
next_stage: mobile-specific-design
- condition: project_type == 'web'
next_stage: web-architecture
- default: fullstack-architecture
```
## Best Practices
Handle these by asking clarifying questions when needed.
1. Show progress
2. Explain transitions
3. Preserve context
4. Allow flexibility
5. Track state
## Workflow Best Practices
## Agent Integration
1. **Always show progress** - Users should know where they are
2. **Explain transitions** - Why moving to next agent
3. **Preserve context** - Pass relevant information forward
4. **Allow flexibility** - Users can skip or modify steps
5. **Track everything** - Maintain complete workflow state
## Integration with Agents
Each agent should be workflow-aware:
- Know which workflow is active
- Understand their role in the workflow
- Access previous artifacts
- Know expected outputs
- Guide toward workflow goals
This creates a seamless experience where the entire team works together toward the workflow's objectives.
Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
==================== END: utils#workflow-management ====================
==================== START: utils#template-format ====================
@@ -3733,13 +3579,9 @@ The story creation is successful when:
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Context
The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
## Instructions
@@ -3748,7 +3590,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from bmad-core/checklists/
- Load the appropriate checklist from {root}/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder