rebuild corrected a few bmad agent errors in orchestration where it thought tasks were actual configurations
This commit is contained in:
Brian Madison
@@ -1,7 +1,15 @@
|
||||
bundle:
|
||||
name: Every Agent Team Bundle
|
||||
name: Team All
|
||||
description: This is a full organization of agents and includes every possible agent. This will produce the larges bundle but give the most options for discussion in a single session
|
||||
|
||||
agents:
|
||||
- bmad
|
||||
- "*"
|
||||
|
||||
workflows:
|
||||
- brownfield-fullstack
|
||||
- brownfield-service
|
||||
- brownfield-ui
|
||||
- greenfield-fullstack
|
||||
- greenfield-service
|
||||
- greenfield-ui
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
bundle:
|
||||
name: Full-Stack Development Team
|
||||
name: Team Fullstack
|
||||
description: >-
|
||||
Comprehensive full-stack development team capable of handling both greenfield
|
||||
application development and brownfield enhancement projects. This team combines
|
||||
@@ -10,6 +10,14 @@ bundle:
|
||||
|
||||
agents:
|
||||
- bmad
|
||||
- analyst
|
||||
- pm
|
||||
- ux-expert
|
||||
- fullstack-architect
|
||||
- po
|
||||
|
||||
workflows:
|
||||
- greenfield-fullstack
|
||||
- brownfield-fullstack
|
||||
- greenfield-ui
|
||||
- brownfield-ui
|
||||
|
||||
@@ -8,3 +8,7 @@ agents:
|
||||
- pm
|
||||
- architect
|
||||
- po
|
||||
|
||||
workflows:
|
||||
- greenfield-service
|
||||
- brownfield-service
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
bundle:
|
||||
name: Development Team Bundle
|
||||
name: Team Scrum
|
||||
description: This is a core development Agile implementation scrum team.
|
||||
|
||||
agents:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
bundle:
|
||||
name: Technical Planning and Assessment Team Bundle
|
||||
description: This is good for deep technical discussions and assessments.
|
||||
name: team-technical
|
||||
description: The Technical Planning and Assessment Team Bundle is good for deep technical discussions and assessments.
|
||||
|
||||
agents:
|
||||
- bmad
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
agent:
|
||||
id: pm
|
||||
name: John
|
||||
id: pm
|
||||
title: Product Manager
|
||||
description: >-
|
||||
Main goal is to help produce or maintain the best possible PRD and represent the end user the
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# Create Team Utility
|
||||
|
||||
This utility helps you create a new BMAD team bundle by combining existing agents.
|
||||
This utility helps you create a NEW BMAD team bundle by combining existing agents from the BMAD-METHOD repository.
|
||||
|
||||
**Important**: This utility is for CREATING new teams, not for listing what agents are available in the current bundle. To see agents in the current bundle, use `/agent-list`.
|
||||
|
||||
## Process
|
||||
|
||||
@@ -13,12 +15,12 @@ Ask the user for:
|
||||
- **Team Description**: What this team is designed to accomplish
|
||||
- **Target Environment**: Usually "web" for team bundles
|
||||
|
||||
### 2. List Available Agents
|
||||
### 2. List Available Agents for Team Creation
|
||||
|
||||
Show all available agents from `/agents/`:
|
||||
When creating a new team, you can choose from these agents in the BMAD-METHOD repository:
|
||||
|
||||
```
|
||||
Available agents:
|
||||
Agents available for team creation:
|
||||
- analyst (Mary) - Project Analyst and Brainstorming Coach
|
||||
- architect (Fred) - System Architecture Expert
|
||||
- bmad (BMad) - BMAD Method Orchestrator
|
||||
@@ -33,6 +35,8 @@ Available agents:
|
||||
- ux-expert (Sally) - UX Design Expert
|
||||
```
|
||||
|
||||
**Note**: This list is for selecting agents when creating a NEW team configuration file. It does not reflect what agents are in your current bundle.
|
||||
|
||||
### 3. Select Team Members
|
||||
|
||||
For each agent the user wants to include:
|
||||
|
||||
@@ -2,19 +2,46 @@
|
||||
|
||||
This utility enables the BMAD orchestrator to manage and execute team workflows.
|
||||
|
||||
## Important: 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.
|
||||
|
||||
**Critical Distinction**:
|
||||
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
|
||||
- The create-* utilities (create-agent, create-team, etc.) are for CREATING new configurations, not for listing what's available in the current session
|
||||
- Use `/agent-list` to show agents in the current bundle, NOT the create-agent utility
|
||||
- Use `/workflows` to show workflows in the current bundle, NOT any creation utilities
|
||||
|
||||
### 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
|
||||
|
||||
## Workflow Commands
|
||||
|
||||
### /workflows
|
||||
Lists all available workflows for the current team.
|
||||
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
|
||||
|
||||
Example response:
|
||||
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:
|
||||
```
|
||||
Available workflows:
|
||||
1. greenfield-mvp - Complete workflow for building a new MVP from scratch
|
||||
2. fullstack-app - Comprehensive workflow for production-ready applications
|
||||
3. api-only - API-first development workflow
|
||||
4. brownfield-enhancement - Enhance existing applications
|
||||
5. frontend-only - Frontend application development
|
||||
Available workflows for [Team Name]:
|
||||
1. [workflow-id] - [Brief description based on workflow type]
|
||||
2. [workflow-id] - [Brief description based on workflow type]
|
||||
...
|
||||
|
||||
Use /workflow-start {number or id} to begin a workflow.
|
||||
```
|
||||
@@ -22,14 +49,14 @@ Use /workflow-start {number or id} to begin a workflow.
|
||||
### /workflow-start {workflow-id}
|
||||
Starts a specific workflow and transitions to the first agent.
|
||||
|
||||
Example: `/workflow-start greenfield-mvp`
|
||||
Example: `/workflow-start greenfield-fullstack`
|
||||
|
||||
### /workflow-status
|
||||
Shows current workflow progress, completed artifacts, and next steps.
|
||||
|
||||
Example response:
|
||||
```
|
||||
Current Workflow: Greenfield MVP Development
|
||||
Current Workflow: Greenfield Full-Stack Development
|
||||
Stage: Product Planning (2 of 6)
|
||||
Completed:
|
||||
✓ Discovery & Requirements
|
||||
@@ -47,10 +74,10 @@ Resumes a workflow from where it left off, useful when starting a new chat.
|
||||
|
||||
User can provide completed artifacts:
|
||||
```
|
||||
User: /workflow-resume greenfield-mvp
|
||||
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-mvp workflow, the next step is:
|
||||
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?
|
||||
@@ -84,7 +111,7 @@ After each artifact is completed:
|
||||
Track all created artifacts:
|
||||
```yaml
|
||||
workflow_state:
|
||||
current_workflow: greenfield-mvp
|
||||
current_workflow: greenfield-fullstack
|
||||
current_stage: planning
|
||||
current_step: 2
|
||||
artifacts:
|
||||
@@ -111,7 +138,7 @@ Example:
|
||||
```
|
||||
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-mvp workflow and have completed
|
||||
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
|
||||
@@ -130,12 +157,12 @@ When transitioning between agents, pass:
|
||||
|
||||
Example transition:
|
||||
```
|
||||
BMad: Great! John has completed the PRD. According to the greenfield-mvp workflow,
|
||||
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-mvp workflow.
|
||||
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
|
||||
|
||||
@@ -239,18 +239,25 @@ class WebBuilder {
|
||||
|
||||
const optimizedBundle = this.optimizer.createStandaloneAgent(agentId, 'web');
|
||||
|
||||
// Get agent config to extract name
|
||||
const agentConfig = this.resolver.loadAgentConfig(agentId);
|
||||
const agentName = agentConfig.name || agentId;
|
||||
|
||||
// Create lowercase-dashcase filename with format: {id}-{name}.txt
|
||||
const filename = `${agentId}-${agentName.toLowerCase().replace(/\s+/g, '-')}.txt`;
|
||||
|
||||
// Write standalone agent file
|
||||
const outputDir = path.join(this.outputPath, 'agents');
|
||||
this.ensureDirectory(outputDir);
|
||||
|
||||
const agentFile = path.join(outputDir, `${agentId}.txt`);
|
||||
const agentFile = path.join(outputDir, filename);
|
||||
fs.writeFileSync(agentFile, optimizedBundle.standaloneContent);
|
||||
|
||||
// Also write to web-bundles if sample update is enabled
|
||||
if (this.sampleUpdateEnabled) {
|
||||
const sampleOutputDir = path.join(this.sampleUpdatePath, 'agents');
|
||||
this.ensureDirectory(sampleOutputDir);
|
||||
const sampleAgentFile = path.join(sampleOutputDir, `${agentId}.txt`);
|
||||
const sampleAgentFile = path.join(sampleOutputDir, filename);
|
||||
fs.writeFileSync(sampleAgentFile, optimizedBundle.standaloneContent);
|
||||
}
|
||||
|
||||
|
||||
@@ -920,19 +920,46 @@ The BMAD orchestrator determines available agents from the bundle configuration
|
||||
|
||||
This utility enables the BMAD orchestrator to manage and execute team workflows.
|
||||
|
||||
## Important: 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.
|
||||
|
||||
**Critical Distinction**:
|
||||
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
|
||||
- The create-* utilities (create-agent, create-team, etc.) are for CREATING new configurations, not for listing what's available in the current session
|
||||
- Use `/agent-list` to show agents in the current bundle, NOT the create-agent utility
|
||||
- Use `/workflows` to show workflows in the current bundle, NOT any creation utilities
|
||||
|
||||
### 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
|
||||
|
||||
## Workflow Commands
|
||||
|
||||
### /workflows
|
||||
Lists all available workflows for the current team.
|
||||
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
|
||||
|
||||
Example response:
|
||||
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:
|
||||
```
|
||||
Available workflows:
|
||||
1. greenfield-mvp - Complete workflow for building a new MVP from scratch
|
||||
2. fullstack-app - Comprehensive workflow for production-ready applications
|
||||
3. api-only - API-first development workflow
|
||||
4. brownfield-enhancement - Enhance existing applications
|
||||
5. frontend-only - Frontend application development
|
||||
Available workflows for [Team Name]:
|
||||
1. [workflow-id] - [Brief description based on workflow type]
|
||||
2. [workflow-id] - [Brief description based on workflow type]
|
||||
...
|
||||
|
||||
Use /workflow-start {number or id} to begin a workflow.
|
||||
```
|
||||
@@ -940,14 +967,14 @@ Use /workflow-start {number or id} to begin a workflow.
|
||||
### /workflow-start {workflow-id}
|
||||
Starts a specific workflow and transitions to the first agent.
|
||||
|
||||
Example: `/workflow-start greenfield-mvp`
|
||||
Example: `/workflow-start greenfield-fullstack`
|
||||
|
||||
### /workflow-status
|
||||
Shows current workflow progress, completed artifacts, and next steps.
|
||||
|
||||
Example response:
|
||||
```
|
||||
Current Workflow: Greenfield MVP Development
|
||||
Current Workflow: Greenfield Full-Stack Development
|
||||
Stage: Product Planning (2 of 6)
|
||||
Completed:
|
||||
✓ Discovery & Requirements
|
||||
@@ -965,10 +992,10 @@ Resumes a workflow from where it left off, useful when starting a new chat.
|
||||
|
||||
User can provide completed artifacts:
|
||||
```
|
||||
User: /workflow-resume greenfield-mvp
|
||||
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-mvp workflow, the next step is:
|
||||
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?
|
||||
@@ -1002,7 +1029,7 @@ After each artifact is completed:
|
||||
Track all created artifacts:
|
||||
```yaml
|
||||
workflow_state:
|
||||
current_workflow: greenfield-mvp
|
||||
current_workflow: greenfield-fullstack
|
||||
current_stage: planning
|
||||
current_step: 2
|
||||
artifacts:
|
||||
@@ -1029,7 +1056,7 @@ Example:
|
||||
```
|
||||
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-mvp workflow and have completed
|
||||
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
|
||||
@@ -1048,12 +1075,12 @@ When transitioning between agents, pass:
|
||||
|
||||
Example transition:
|
||||
```
|
||||
BMad: Great! John has completed the PRD. According to the greenfield-mvp workflow,
|
||||
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-mvp workflow.
|
||||
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
|
||||
@@ -1378,7 +1405,9 @@ Style: Direct solutions with example code.
|
||||
==================== START: utils#create-team ====================
|
||||
# Create Team Utility
|
||||
|
||||
This utility helps you create a new BMAD team bundle by combining existing agents.
|
||||
This utility helps you create a NEW BMAD team bundle by combining existing agents from the BMAD-METHOD repository.
|
||||
|
||||
**Important**: This utility is for CREATING new teams, not for listing what agents are available in the current bundle. To see agents in the current bundle, use `/agent-list`.
|
||||
|
||||
## Process
|
||||
|
||||
@@ -1391,12 +1420,12 @@ Ask the user for:
|
||||
- **Team Description**: What this team is designed to accomplish
|
||||
- **Target Environment**: Usually "web" for team bundles
|
||||
|
||||
### 2. List Available Agents
|
||||
### 2. List Available Agents for Team Creation
|
||||
|
||||
Show all available agents from `/agents/`:
|
||||
When creating a new team, you can choose from these agents in the BMAD-METHOD repository:
|
||||
|
||||
```
|
||||
Available agents:
|
||||
Agents available for team creation:
|
||||
- analyst (Mary) - Project Analyst and Brainstorming Coach
|
||||
- architect (Fred) - System Architecture Expert
|
||||
- bmad (BMad) - BMAD Method Orchestrator
|
||||
@@ -1411,6 +1440,8 @@ Available agents:
|
||||
- ux-expert (Sally) - UX Design Expert
|
||||
```
|
||||
|
||||
**Note**: This list is for selecting agents when creating a NEW team configuration file. It does not reflect what agents are in your current bundle.
|
||||
|
||||
### 3. Select Team Members
|
||||
|
||||
For each agent the user wants to include:
|
||||
@@ -34,7 +34,7 @@
|
||||
5. **Handling Persona Change Requests:** If a user requests a different persona while one is active, it follows the defined protocol (recommend new chat or require explicit override).
|
||||
|
||||
|
||||
## Available Agents in Every Agent Team Bundle
|
||||
## Available Agents in Team All
|
||||
|
||||
### BMad (/bmad)
|
||||
- **Role:** BMad Primary Orchestrator and Coach
|
||||
@@ -86,12 +86,12 @@
|
||||
|
||||
|
||||
|
||||
<!-- Bundle: Every Agent Team Bundle -->
|
||||
<!-- Generated: 2025-06-09T01:54:51.028Z -->
|
||||
<!-- Bundle: Team All -->
|
||||
<!-- Generated: 2025-06-09T03:23:56.264Z -->
|
||||
<!-- Environment: web -->
|
||||
|
||||
==================== START: agent-config ====================
|
||||
name: Every Agent Team Bundle
|
||||
name: Team All
|
||||
version: 1.0.0
|
||||
agents:
|
||||
bmad:
|
||||
@@ -9509,19 +9509,46 @@ The BMAD orchestrator determines available agents from the bundle configuration
|
||||
|
||||
This utility enables the BMAD orchestrator to manage and execute team workflows.
|
||||
|
||||
## Important: 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.
|
||||
|
||||
**Critical Distinction**:
|
||||
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
|
||||
- The create-* utilities (create-agent, create-team, etc.) are for CREATING new configurations, not for listing what's available in the current session
|
||||
- Use `/agent-list` to show agents in the current bundle, NOT the create-agent utility
|
||||
- Use `/workflows` to show workflows in the current bundle, NOT any creation utilities
|
||||
|
||||
### 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
|
||||
|
||||
## Workflow Commands
|
||||
|
||||
### /workflows
|
||||
Lists all available workflows for the current team.
|
||||
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
|
||||
|
||||
Example response:
|
||||
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:
|
||||
```
|
||||
Available workflows:
|
||||
1. greenfield-mvp - Complete workflow for building a new MVP from scratch
|
||||
2. fullstack-app - Comprehensive workflow for production-ready applications
|
||||
3. api-only - API-first development workflow
|
||||
4. brownfield-enhancement - Enhance existing applications
|
||||
5. frontend-only - Frontend application development
|
||||
Available workflows for [Team Name]:
|
||||
1. [workflow-id] - [Brief description based on workflow type]
|
||||
2. [workflow-id] - [Brief description based on workflow type]
|
||||
...
|
||||
|
||||
Use /workflow-start {number or id} to begin a workflow.
|
||||
```
|
||||
@@ -9529,14 +9556,14 @@ Use /workflow-start {number or id} to begin a workflow.
|
||||
### /workflow-start {workflow-id}
|
||||
Starts a specific workflow and transitions to the first agent.
|
||||
|
||||
Example: `/workflow-start greenfield-mvp`
|
||||
Example: `/workflow-start greenfield-fullstack`
|
||||
|
||||
### /workflow-status
|
||||
Shows current workflow progress, completed artifacts, and next steps.
|
||||
|
||||
Example response:
|
||||
```
|
||||
Current Workflow: Greenfield MVP Development
|
||||
Current Workflow: Greenfield Full-Stack Development
|
||||
Stage: Product Planning (2 of 6)
|
||||
Completed:
|
||||
✓ Discovery & Requirements
|
||||
@@ -9554,10 +9581,10 @@ Resumes a workflow from where it left off, useful when starting a new chat.
|
||||
|
||||
User can provide completed artifacts:
|
||||
```
|
||||
User: /workflow-resume greenfield-mvp
|
||||
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-mvp workflow, the next step is:
|
||||
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?
|
||||
@@ -9591,7 +9618,7 @@ After each artifact is completed:
|
||||
Track all created artifacts:
|
||||
```yaml
|
||||
workflow_state:
|
||||
current_workflow: greenfield-mvp
|
||||
current_workflow: greenfield-fullstack
|
||||
current_stage: planning
|
||||
current_step: 2
|
||||
artifacts:
|
||||
@@ -9618,7 +9645,7 @@ Example:
|
||||
```
|
||||
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-mvp workflow and have completed
|
||||
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
|
||||
@@ -9637,12 +9664,12 @@ When transitioning between agents, pass:
|
||||
|
||||
Example transition:
|
||||
```
|
||||
BMad: Great! John has completed the PRD. According to the greenfield-mvp workflow,
|
||||
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-mvp workflow.
|
||||
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
|
||||
@@ -9967,7 +9994,9 @@ Style: Direct solutions with example code.
|
||||
==================== START: utils#create-team ====================
|
||||
# Create Team Utility
|
||||
|
||||
This utility helps you create a new BMAD team bundle by combining existing agents.
|
||||
This utility helps you create a NEW BMAD team bundle by combining existing agents from the BMAD-METHOD repository.
|
||||
|
||||
**Important**: This utility is for CREATING new teams, not for listing what agents are available in the current bundle. To see agents in the current bundle, use `/agent-list`.
|
||||
|
||||
## Process
|
||||
|
||||
@@ -9980,12 +10009,12 @@ Ask the user for:
|
||||
- **Team Description**: What this team is designed to accomplish
|
||||
- **Target Environment**: Usually "web" for team bundles
|
||||
|
||||
### 2. List Available Agents
|
||||
### 2. List Available Agents for Team Creation
|
||||
|
||||
Show all available agents from `/agents/`:
|
||||
When creating a new team, you can choose from these agents in the BMAD-METHOD repository:
|
||||
|
||||
```
|
||||
Available agents:
|
||||
Agents available for team creation:
|
||||
- analyst (Mary) - Project Analyst and Brainstorming Coach
|
||||
- architect (Fred) - System Architecture Expert
|
||||
- bmad (BMad) - BMAD Method Orchestrator
|
||||
@@ -10000,6 +10029,8 @@ Available agents:
|
||||
- ux-expert (Sally) - UX Design Expert
|
||||
```
|
||||
|
||||
**Note**: This list is for selecting agents when creating a NEW team configuration file. It does not reflect what agents are in your current bundle.
|
||||
|
||||
### 3. Select Team Members
|
||||
|
||||
For each agent the user wants to include:
|
||||
File diff suppressed because it is too large
Load Diff
@@ -61,7 +61,7 @@
|
||||
|
||||
|
||||
<!-- Bundle: Team No UI -->
|
||||
<!-- Generated: 2025-06-09T01:54:51.035Z -->
|
||||
<!-- Generated: 2025-06-09T03:23:56.271Z -->
|
||||
<!-- Environment: web -->
|
||||
|
||||
==================== START: agent-config ====================
|
||||
@@ -5993,19 +5993,46 @@ The BMAD orchestrator determines available agents from the bundle configuration
|
||||
|
||||
This utility enables the BMAD orchestrator to manage and execute team workflows.
|
||||
|
||||
## Important: 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.
|
||||
|
||||
**Critical Distinction**:
|
||||
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
|
||||
- The create-* utilities (create-agent, create-team, etc.) are for CREATING new configurations, not for listing what's available in the current session
|
||||
- Use `/agent-list` to show agents in the current bundle, NOT the create-agent utility
|
||||
- Use `/workflows` to show workflows in the current bundle, NOT any creation utilities
|
||||
|
||||
### 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
|
||||
|
||||
## Workflow Commands
|
||||
|
||||
### /workflows
|
||||
Lists all available workflows for the current team.
|
||||
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
|
||||
|
||||
Example response:
|
||||
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:
|
||||
```
|
||||
Available workflows:
|
||||
1. greenfield-mvp - Complete workflow for building a new MVP from scratch
|
||||
2. fullstack-app - Comprehensive workflow for production-ready applications
|
||||
3. api-only - API-first development workflow
|
||||
4. brownfield-enhancement - Enhance existing applications
|
||||
5. frontend-only - Frontend application development
|
||||
Available workflows for [Team Name]:
|
||||
1. [workflow-id] - [Brief description based on workflow type]
|
||||
2. [workflow-id] - [Brief description based on workflow type]
|
||||
...
|
||||
|
||||
Use /workflow-start {number or id} to begin a workflow.
|
||||
```
|
||||
@@ -6013,14 +6040,14 @@ Use /workflow-start {number or id} to begin a workflow.
|
||||
### /workflow-start {workflow-id}
|
||||
Starts a specific workflow and transitions to the first agent.
|
||||
|
||||
Example: `/workflow-start greenfield-mvp`
|
||||
Example: `/workflow-start greenfield-fullstack`
|
||||
|
||||
### /workflow-status
|
||||
Shows current workflow progress, completed artifacts, and next steps.
|
||||
|
||||
Example response:
|
||||
```
|
||||
Current Workflow: Greenfield MVP Development
|
||||
Current Workflow: Greenfield Full-Stack Development
|
||||
Stage: Product Planning (2 of 6)
|
||||
Completed:
|
||||
✓ Discovery & Requirements
|
||||
@@ -6038,10 +6065,10 @@ Resumes a workflow from where it left off, useful when starting a new chat.
|
||||
|
||||
User can provide completed artifacts:
|
||||
```
|
||||
User: /workflow-resume greenfield-mvp
|
||||
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-mvp workflow, the next step is:
|
||||
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?
|
||||
@@ -6075,7 +6102,7 @@ After each artifact is completed:
|
||||
Track all created artifacts:
|
||||
```yaml
|
||||
workflow_state:
|
||||
current_workflow: greenfield-mvp
|
||||
current_workflow: greenfield-fullstack
|
||||
current_stage: planning
|
||||
current_step: 2
|
||||
artifacts:
|
||||
@@ -6102,7 +6129,7 @@ Example:
|
||||
```
|
||||
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-mvp workflow and have completed
|
||||
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
|
||||
@@ -6121,12 +6148,12 @@ When transitioning between agents, pass:
|
||||
|
||||
Example transition:
|
||||
```
|
||||
BMad: Great! John has completed the PRD. According to the greenfield-mvp workflow,
|
||||
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-mvp workflow.
|
||||
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
|
||||
@@ -6451,7 +6478,9 @@ Style: Direct solutions with example code.
|
||||
==================== START: utils#create-team ====================
|
||||
# Create Team Utility
|
||||
|
||||
This utility helps you create a new BMAD team bundle by combining existing agents.
|
||||
This utility helps you create a NEW BMAD team bundle by combining existing agents from the BMAD-METHOD repository.
|
||||
|
||||
**Important**: This utility is for CREATING new teams, not for listing what agents are available in the current bundle. To see agents in the current bundle, use `/agent-list`.
|
||||
|
||||
## Process
|
||||
|
||||
@@ -6464,12 +6493,12 @@ Ask the user for:
|
||||
- **Team Description**: What this team is designed to accomplish
|
||||
- **Target Environment**: Usually "web" for team bundles
|
||||
|
||||
### 2. List Available Agents
|
||||
### 2. List Available Agents for Team Creation
|
||||
|
||||
Show all available agents from `/agents/`:
|
||||
When creating a new team, you can choose from these agents in the BMAD-METHOD repository:
|
||||
|
||||
```
|
||||
Available agents:
|
||||
Agents available for team creation:
|
||||
- analyst (Mary) - Project Analyst and Brainstorming Coach
|
||||
- architect (Fred) - System Architecture Expert
|
||||
- bmad (BMad) - BMAD Method Orchestrator
|
||||
@@ -6484,6 +6513,8 @@ Available agents:
|
||||
- ux-expert (Sally) - UX Design Expert
|
||||
```
|
||||
|
||||
**Note**: This list is for selecting agents when creating a NEW team configuration file. It does not reflect what agents are in your current bundle.
|
||||
|
||||
### 3. Select Team Members
|
||||
|
||||
For each agent the user wants to include:
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
5. **Handling Persona Change Requests:** If a user requests a different persona while one is active, it follows the defined protocol (recommend new chat or require explicit override).
|
||||
|
||||
|
||||
## Available Agents in Development Team Bundle
|
||||
## Available Agents in Team Scrum
|
||||
|
||||
### BMad (/bmad)
|
||||
- **Role:** BMad Primary Orchestrator and Coach
|
||||
@@ -59,12 +59,12 @@
|
||||
|
||||
|
||||
|
||||
<!-- Bundle: Development Team Bundle -->
|
||||
<!-- Generated: 2025-06-09T01:54:51.037Z -->
|
||||
<!-- Bundle: Team Scrum -->
|
||||
<!-- Generated: 2025-06-09T03:23:56.272Z -->
|
||||
<!-- Environment: web -->
|
||||
|
||||
==================== START: agent-config ====================
|
||||
name: Development Team Bundle
|
||||
name: Team Scrum
|
||||
version: 1.0.0
|
||||
agents:
|
||||
bmad:
|
||||
@@ -3587,19 +3587,46 @@ The BMAD orchestrator determines available agents from the bundle configuration
|
||||
|
||||
This utility enables the BMAD orchestrator to manage and execute team workflows.
|
||||
|
||||
## Important: 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.
|
||||
|
||||
**Critical Distinction**:
|
||||
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
|
||||
- The create-* utilities (create-agent, create-team, etc.) are for CREATING new configurations, not for listing what's available in the current session
|
||||
- Use `/agent-list` to show agents in the current bundle, NOT the create-agent utility
|
||||
- Use `/workflows` to show workflows in the current bundle, NOT any creation utilities
|
||||
|
||||
### 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
|
||||
|
||||
## Workflow Commands
|
||||
|
||||
### /workflows
|
||||
Lists all available workflows for the current team.
|
||||
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
|
||||
|
||||
Example response:
|
||||
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:
|
||||
```
|
||||
Available workflows:
|
||||
1. greenfield-mvp - Complete workflow for building a new MVP from scratch
|
||||
2. fullstack-app - Comprehensive workflow for production-ready applications
|
||||
3. api-only - API-first development workflow
|
||||
4. brownfield-enhancement - Enhance existing applications
|
||||
5. frontend-only - Frontend application development
|
||||
Available workflows for [Team Name]:
|
||||
1. [workflow-id] - [Brief description based on workflow type]
|
||||
2. [workflow-id] - [Brief description based on workflow type]
|
||||
...
|
||||
|
||||
Use /workflow-start {number or id} to begin a workflow.
|
||||
```
|
||||
@@ -3607,14 +3634,14 @@ Use /workflow-start {number or id} to begin a workflow.
|
||||
### /workflow-start {workflow-id}
|
||||
Starts a specific workflow and transitions to the first agent.
|
||||
|
||||
Example: `/workflow-start greenfield-mvp`
|
||||
Example: `/workflow-start greenfield-fullstack`
|
||||
|
||||
### /workflow-status
|
||||
Shows current workflow progress, completed artifacts, and next steps.
|
||||
|
||||
Example response:
|
||||
```
|
||||
Current Workflow: Greenfield MVP Development
|
||||
Current Workflow: Greenfield Full-Stack Development
|
||||
Stage: Product Planning (2 of 6)
|
||||
Completed:
|
||||
✓ Discovery & Requirements
|
||||
@@ -3632,10 +3659,10 @@ Resumes a workflow from where it left off, useful when starting a new chat.
|
||||
|
||||
User can provide completed artifacts:
|
||||
```
|
||||
User: /workflow-resume greenfield-mvp
|
||||
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-mvp workflow, the next step is:
|
||||
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?
|
||||
@@ -3669,7 +3696,7 @@ After each artifact is completed:
|
||||
Track all created artifacts:
|
||||
```yaml
|
||||
workflow_state:
|
||||
current_workflow: greenfield-mvp
|
||||
current_workflow: greenfield-fullstack
|
||||
current_stage: planning
|
||||
current_step: 2
|
||||
artifacts:
|
||||
@@ -3696,7 +3723,7 @@ Example:
|
||||
```
|
||||
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-mvp workflow and have completed
|
||||
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
|
||||
@@ -3715,12 +3742,12 @@ When transitioning between agents, pass:
|
||||
|
||||
Example transition:
|
||||
```
|
||||
BMad: Great! John has completed the PRD. According to the greenfield-mvp workflow,
|
||||
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-mvp workflow.
|
||||
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
|
||||
@@ -4045,7 +4072,9 @@ Style: Direct solutions with example code.
|
||||
==================== START: utils#create-team ====================
|
||||
# Create Team Utility
|
||||
|
||||
This utility helps you create a new BMAD team bundle by combining existing agents.
|
||||
This utility helps you create a NEW BMAD team bundle by combining existing agents from the BMAD-METHOD repository.
|
||||
|
||||
**Important**: This utility is for CREATING new teams, not for listing what agents are available in the current bundle. To see agents in the current bundle, use `/agent-list`.
|
||||
|
||||
## Process
|
||||
|
||||
@@ -4058,12 +4087,12 @@ Ask the user for:
|
||||
- **Team Description**: What this team is designed to accomplish
|
||||
- **Target Environment**: Usually "web" for team bundles
|
||||
|
||||
### 2. List Available Agents
|
||||
### 2. List Available Agents for Team Creation
|
||||
|
||||
Show all available agents from `/agents/`:
|
||||
When creating a new team, you can choose from these agents in the BMAD-METHOD repository:
|
||||
|
||||
```
|
||||
Available agents:
|
||||
Agents available for team creation:
|
||||
- analyst (Mary) - Project Analyst and Brainstorming Coach
|
||||
- architect (Fred) - System Architecture Expert
|
||||
- bmad (BMad) - BMAD Method Orchestrator
|
||||
@@ -4078,6 +4107,8 @@ Available agents:
|
||||
- ux-expert (Sally) - UX Design Expert
|
||||
```
|
||||
|
||||
**Note**: This list is for selecting agents when creating a NEW team configuration file. It does not reflect what agents are in your current bundle.
|
||||
|
||||
### 3. Select Team Members
|
||||
|
||||
For each agent the user wants to include:
|
||||
@@ -34,7 +34,7 @@
|
||||
5. **Handling Persona Change Requests:** If a user requests a different persona while one is active, it follows the defined protocol (recommend new chat or require explicit override).
|
||||
|
||||
|
||||
## Available Agents in Technical Planning and Assessment Team Bundle
|
||||
## Available Agents in team-technical
|
||||
|
||||
### BMad (/bmad)
|
||||
- **Role:** BMad Primary Orchestrator and Coach
|
||||
@@ -57,12 +57,12 @@
|
||||
|
||||
|
||||
|
||||
<!-- Bundle: Technical Planning and Assessment Team Bundle -->
|
||||
<!-- Generated: 2025-06-09T01:54:51.038Z -->
|
||||
<!-- Bundle: team-technical -->
|
||||
<!-- Generated: 2025-06-09T03:23:56.273Z -->
|
||||
<!-- Environment: web -->
|
||||
|
||||
==================== START: agent-config ====================
|
||||
name: Technical Planning and Assessment Team Bundle
|
||||
name: team-technical
|
||||
version: 1.0.0
|
||||
agents:
|
||||
bmad:
|
||||
@@ -5841,19 +5841,46 @@ The BMAD orchestrator determines available agents from the bundle configuration
|
||||
|
||||
This utility enables the BMAD orchestrator to manage and execute team workflows.
|
||||
|
||||
## Important: 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.
|
||||
|
||||
**Critical Distinction**:
|
||||
- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
|
||||
- The create-* utilities (create-agent, create-team, etc.) are for CREATING new configurations, not for listing what's available in the current session
|
||||
- Use `/agent-list` to show agents in the current bundle, NOT the create-agent utility
|
||||
- Use `/workflows` to show workflows in the current bundle, NOT any creation utilities
|
||||
|
||||
### 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
|
||||
|
||||
## Workflow Commands
|
||||
|
||||
### /workflows
|
||||
Lists all available workflows for the current team.
|
||||
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
|
||||
|
||||
Example response:
|
||||
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:
|
||||
```
|
||||
Available workflows:
|
||||
1. greenfield-mvp - Complete workflow for building a new MVP from scratch
|
||||
2. fullstack-app - Comprehensive workflow for production-ready applications
|
||||
3. api-only - API-first development workflow
|
||||
4. brownfield-enhancement - Enhance existing applications
|
||||
5. frontend-only - Frontend application development
|
||||
Available workflows for [Team Name]:
|
||||
1. [workflow-id] - [Brief description based on workflow type]
|
||||
2. [workflow-id] - [Brief description based on workflow type]
|
||||
...
|
||||
|
||||
Use /workflow-start {number or id} to begin a workflow.
|
||||
```
|
||||
@@ -5861,14 +5888,14 @@ Use /workflow-start {number or id} to begin a workflow.
|
||||
### /workflow-start {workflow-id}
|
||||
Starts a specific workflow and transitions to the first agent.
|
||||
|
||||
Example: `/workflow-start greenfield-mvp`
|
||||
Example: `/workflow-start greenfield-fullstack`
|
||||
|
||||
### /workflow-status
|
||||
Shows current workflow progress, completed artifacts, and next steps.
|
||||
|
||||
Example response:
|
||||
```
|
||||
Current Workflow: Greenfield MVP Development
|
||||
Current Workflow: Greenfield Full-Stack Development
|
||||
Stage: Product Planning (2 of 6)
|
||||
Completed:
|
||||
✓ Discovery & Requirements
|
||||
@@ -5886,10 +5913,10 @@ Resumes a workflow from where it left off, useful when starting a new chat.
|
||||
|
||||
User can provide completed artifacts:
|
||||
```
|
||||
User: /workflow-resume greenfield-mvp
|
||||
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-mvp workflow, the next step is:
|
||||
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?
|
||||
@@ -5923,7 +5950,7 @@ After each artifact is completed:
|
||||
Track all created artifacts:
|
||||
```yaml
|
||||
workflow_state:
|
||||
current_workflow: greenfield-mvp
|
||||
current_workflow: greenfield-fullstack
|
||||
current_stage: planning
|
||||
current_step: 2
|
||||
artifacts:
|
||||
@@ -5950,7 +5977,7 @@ Example:
|
||||
```
|
||||
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-mvp workflow and have completed
|
||||
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
|
||||
@@ -5969,12 +5996,12 @@ When transitioning between agents, pass:
|
||||
|
||||
Example transition:
|
||||
```
|
||||
BMad: Great! John has completed the PRD. According to the greenfield-mvp workflow,
|
||||
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-mvp workflow.
|
||||
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
|
||||
@@ -6299,7 +6326,9 @@ Style: Direct solutions with example code.
|
||||
==================== START: utils#create-team ====================
|
||||
# Create Team Utility
|
||||
|
||||
This utility helps you create a new BMAD team bundle by combining existing agents.
|
||||
This utility helps you create a NEW BMAD team bundle by combining existing agents from the BMAD-METHOD repository.
|
||||
|
||||
**Important**: This utility is for CREATING new teams, not for listing what agents are available in the current bundle. To see agents in the current bundle, use `/agent-list`.
|
||||
|
||||
## Process
|
||||
|
||||
@@ -6312,12 +6341,12 @@ Ask the user for:
|
||||
- **Team Description**: What this team is designed to accomplish
|
||||
- **Target Environment**: Usually "web" for team bundles
|
||||
|
||||
### 2. List Available Agents
|
||||
### 2. List Available Agents for Team Creation
|
||||
|
||||
Show all available agents from `/agents/`:
|
||||
When creating a new team, you can choose from these agents in the BMAD-METHOD repository:
|
||||
|
||||
```
|
||||
Available agents:
|
||||
Agents available for team creation:
|
||||
- analyst (Mary) - Project Analyst and Brainstorming Coach
|
||||
- architect (Fred) - System Architecture Expert
|
||||
- bmad (BMad) - BMAD Method Orchestrator
|
||||
@@ -6332,6 +6361,8 @@ Available agents:
|
||||
- ux-expert (Sally) - UX Design Expert
|
||||
```
|
||||
|
||||
**Note**: This list is for selecting agents when creating a NEW team configuration file. It does not reflect what agents are in your current bundle.
|
||||
|
||||
### 3. Select Team Members
|
||||
|
||||
For each agent the user wants to include:
|
||||
Reference in New Issue
Block a user