Compare commits
2 Commits
021936eaa9
...
12dd97fe9b
| Author | SHA1 | Date |
|---|---|---|
Brian Madison
|
12dd97fe9b | |
|
Brian Madison
|
00ad756acf |
|
|
@ -153,7 +153,7 @@ Each agent brings deep expertise and can be customized to match your team's styl
|
||||||
- **Creative Intelligence Suite (CIS)** - Innovation & problem-solving
|
- **Creative Intelligence Suite (CIS)** - Innovation & problem-solving
|
||||||
- Brainstorming, design thinking, storytelling
|
- Brainstorming, design thinking, storytelling
|
||||||
- 5 creative facilitation workflows
|
- 5 creative facilitation workflows
|
||||||
- [→ Creative Workflows](./src/modules/cis/README.md)
|
- [→ Creative Workflows](src/modules/cis/docs/README.md)
|
||||||
|
|
||||||
### Key Features
|
### Key Features
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -60,7 +60,7 @@ Build your own agents, workflows, and modules.
|
||||||
|
|
||||||
AI-powered creative thinking and brainstorming.
|
AI-powered creative thinking and brainstorming.
|
||||||
|
|
||||||
- **[CIS Module README](../src/modules/cis/README.md)** - Module overview and workflows
|
- **[CIS Module README](../src/modules/cis/docs/README.md)** - Module overview and workflows
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,186 +0,0 @@
|
||||||
# IDE Content Injection Standard
|
|
||||||
|
|
||||||
## Overview
|
|
||||||
|
|
||||||
This document defines the standard for IDE-specific content injection in BMAD modules. Each IDE can inject its own specific content into BMAD templates during installation without polluting the source files with IDE-specific code. The installation process is interactive, allowing users to choose what IDE-specific features they want to install.
|
|
||||||
|
|
||||||
## Architecture
|
|
||||||
|
|
||||||
### 1. Injection Points
|
|
||||||
|
|
||||||
Files that support IDE-specific content define injection points using HTML comments:
|
|
||||||
|
|
||||||
```xml
|
|
||||||
<!-- IDE-INJECT-POINT: unique-point-name -->
|
|
||||||
```
|
|
||||||
|
|
||||||
### 2. Module Structure
|
|
||||||
|
|
||||||
Each module that needs IDE-specific content creates a sub-module folder:
|
|
||||||
|
|
||||||
```
|
|
||||||
src/modules/{module-name}/sub-modules/{ide-name}/
|
|
||||||
├── injections.yaml # Injection configuration
|
|
||||||
├── sub-agents/ # IDE-specific subagents (if applicable)
|
|
||||||
└── config.yaml # Other IDE-specific config
|
|
||||||
```
|
|
||||||
|
|
||||||
### 3. Injection Configuration Format
|
|
||||||
|
|
||||||
The `injections.yaml` file defines what content to inject where:
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
# injections.yaml structure
|
|
||||||
injections:
|
|
||||||
- file: 'relative/path/to/file.md' # Path relative to installation root
|
|
||||||
point: 'injection-point-name' # Must match IDE-INJECT-POINT name
|
|
||||||
requires: 'subagent-name' # Which subagent must be selected (or "any")
|
|
||||||
content: | # Content to inject (preserves formatting)
|
|
||||||
<llm>
|
|
||||||
<i>Instructions specific to this IDE</i>
|
|
||||||
</llm>
|
|
||||||
|
|
||||||
# Subagents available for installation
|
|
||||||
subagents:
|
|
||||||
source: 'sub-agents' # Source folder relative to this config
|
|
||||||
target: '.claude/agents' # Claude's expected location (don't change)
|
|
||||||
files:
|
|
||||||
- 'agent1.md'
|
|
||||||
- 'agent2.md'
|
|
||||||
```
|
|
||||||
|
|
||||||
### 4. Interactive Installation Process
|
|
||||||
|
|
||||||
For Claude Code specifically, the installer will:
|
|
||||||
|
|
||||||
1. **Detect available subagents** from the module's `injections.yaml`
|
|
||||||
2. **Ask the user** about subagent installation:
|
|
||||||
- Install all subagents (default)
|
|
||||||
- Select specific subagents
|
|
||||||
- Skip subagent installation
|
|
||||||
3. **Ask installation location** (if subagents selected):
|
|
||||||
- Project level: `.claude/agents/`
|
|
||||||
- User level: `~/.claude/agents/`
|
|
||||||
4. **Copy selected subagents** to the chosen location
|
|
||||||
5. **Inject only relevant content** based on selected subagents
|
|
||||||
|
|
||||||
Other IDEs can implement their own installation logic appropriate to their architecture.
|
|
||||||
|
|
||||||
## Implementation
|
|
||||||
|
|
||||||
### IDE Installer Responsibilities
|
|
||||||
|
|
||||||
Each IDE installer (e.g., `claude-code.js`) must:
|
|
||||||
|
|
||||||
1. **Check for sub-modules**: Look for `sub-modules/{ide-name}/` in each installed module
|
|
||||||
2. **Load injection config**: Parse `injections.yaml` if present
|
|
||||||
3. **Process injections**: Replace injection points with configured content
|
|
||||||
4. **Copy additional files**: Handle subagents or other IDE-specific files
|
|
||||||
|
|
||||||
### Example Implementation (Claude Code)
|
|
||||||
|
|
||||||
```javascript
|
|
||||||
async processModuleInjections(projectDir, bmadDir, options) {
|
|
||||||
for (const moduleName of options.selectedModules) {
|
|
||||||
const configPath = path.join(
|
|
||||||
bmadDir, 'src/modules', moduleName,
|
|
||||||
'sub-modules/claude-code/injections.yaml'
|
|
||||||
);
|
|
||||||
|
|
||||||
if (exists(configPath)) {
|
|
||||||
const config = yaml.load(configPath);
|
|
||||||
|
|
||||||
// Interactive: Ask user about subagent installation
|
|
||||||
const choices = await this.promptSubagentInstallation(config.subagents);
|
|
||||||
|
|
||||||
if (choices.install !== 'none') {
|
|
||||||
// Ask where to install
|
|
||||||
const location = await this.promptInstallLocation();
|
|
||||||
|
|
||||||
// Process injections based on selections
|
|
||||||
for (const injection of config.injections) {
|
|
||||||
if (this.shouldInject(injection, choices)) {
|
|
||||||
await this.injectContent(projectDir, injection, choices);
|
|
||||||
}
|
|
||||||
}
|
|
||||||
|
|
||||||
// Copy selected subagents
|
|
||||||
await this.copySelectedSubagents(projectDir, config.subagents, choices, location);
|
|
||||||
}
|
|
||||||
}
|
|
||||||
}
|
|
||||||
}
|
|
||||||
```
|
|
||||||
|
|
||||||
## Benefits
|
|
||||||
|
|
||||||
1. **Clean Source Files**: No IDE-specific conditionals in source
|
|
||||||
2. **Modular**: Each IDE manages its own injections
|
|
||||||
3. **Scalable**: Easy to add support for new IDEs
|
|
||||||
4. **Maintainable**: IDE-specific content lives with IDE config
|
|
||||||
5. **Flexible**: Different modules can inject different content
|
|
||||||
|
|
||||||
## Adding Support for a New IDE
|
|
||||||
|
|
||||||
1. Create sub-module folder: `src/modules/{module}/sub-modules/{new-ide}/`
|
|
||||||
2. Add `injections.yaml` with IDE-specific content
|
|
||||||
3. Update IDE installer to process injections using this standard
|
|
||||||
4. Test installation with and without the IDE selected
|
|
||||||
|
|
||||||
## Example: BMM Module with Claude Code
|
|
||||||
|
|
||||||
### File Structure
|
|
||||||
|
|
||||||
```
|
|
||||||
src/modules/bmm/
|
|
||||||
├── agents/pm.md # Has injection point
|
|
||||||
├── templates/prd.md # Has multiple injection points
|
|
||||||
└── sub-modules/
|
|
||||||
└── claude-code/
|
|
||||||
├── injections.yaml # Defines what to inject
|
|
||||||
└── sub-agents/ # Claude Code specific subagents
|
|
||||||
├── market-researcher.md
|
|
||||||
├── requirements-analyst.md
|
|
||||||
└── ...
|
|
||||||
```
|
|
||||||
|
|
||||||
### Injection Point in pm.md
|
|
||||||
|
|
||||||
```xml
|
|
||||||
<agent>
|
|
||||||
<persona>...</persona>
|
|
||||||
<!-- IDE-INJECT-POINT: pm-agent-instructions -->
|
|
||||||
<cmds>...</cmds>
|
|
||||||
</agent>
|
|
||||||
```
|
|
||||||
|
|
||||||
### Injection Configuration
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
injections:
|
|
||||||
- file: '_bmad/bmm/agents/pm.md'
|
|
||||||
point: 'pm-agent-instructions'
|
|
||||||
requires: 'any' # Injected if ANY subagent is selected
|
|
||||||
content: |
|
|
||||||
<llm critical="true">
|
|
||||||
<i>Use 'market-researcher' subagent for analysis</i>
|
|
||||||
</llm>
|
|
||||||
|
|
||||||
- file: '_bmad/bmm/templates/prd.md'
|
|
||||||
point: 'prd-goals-context-delegation'
|
|
||||||
requires: 'market-researcher' # Only if this specific subagent selected
|
|
||||||
content: |
|
|
||||||
<i>DELEGATE: Use 'market-researcher' subagent...</i>
|
|
||||||
```
|
|
||||||
|
|
||||||
### Result After Installation
|
|
||||||
|
|
||||||
```xml
|
|
||||||
<agent>
|
|
||||||
<persona>...</persona>
|
|
||||||
<llm critical="true">
|
|
||||||
<i>Use 'market-researcher' subagent for analysis</i>
|
|
||||||
</llm>
|
|
||||||
<cmds>...</cmds>
|
|
||||||
</agent>
|
|
||||||
```
|
|
||||||
|
|
@ -1,389 +0,0 @@
|
||||||
# BMAD Installation & Module System Reference
|
|
||||||
|
|
||||||
## Table of Contents
|
|
||||||
|
|
||||||
1. [Overview](#overview)
|
|
||||||
2. [Quick Start](#quick-start)
|
|
||||||
3. [Architecture](#architecture)
|
|
||||||
4. [Modules](#modules)
|
|
||||||
5. [Configuration System](#configuration-system)
|
|
||||||
6. [Platform Integration](#platform-integration)
|
|
||||||
7. [Development Guide](#development-guide)
|
|
||||||
8. [Troubleshooting](#troubleshooting)
|
|
||||||
|
|
||||||
## Overview
|
|
||||||
|
|
||||||
BMad Core is a modular AI agent framework with intelligent installation, platform-agnostic support, and configuration inheritance.
|
|
||||||
|
|
||||||
### Key Features
|
|
||||||
|
|
||||||
- **Modular Design**: Core + optional modules (BMB, BMM, CIS)
|
|
||||||
- **Smart Installation**: Interactive configuration with dependency resolution
|
|
||||||
- **Clean Architecture**: Centralized `_bmad` directory add to project, no source pollution with multiple folders added
|
|
||||||
|
|
||||||
## Architecture
|
|
||||||
|
|
||||||
### Directory Structure upon installation
|
|
||||||
|
|
||||||
```
|
|
||||||
project-root/
|
|
||||||
├── _bmad/ # Centralized installation
|
|
||||||
│ ├── _config/ # Configuration
|
|
||||||
│ │ ├── agents/ # Agent configs
|
|
||||||
│ │ └── agent-manifest.csv # Agent manifest
|
|
||||||
│ ├── core/ # Core module
|
|
||||||
│ │ ├── agents/
|
|
||||||
│ │ ├── tasks/
|
|
||||||
│ │ └── config.yaml
|
|
||||||
│ ├── bmm/ # BMad Method module
|
|
||||||
│ │ ├── agents/
|
|
||||||
│ │ ├── tasks/
|
|
||||||
│ │ ├── workflows/
|
|
||||||
│ │ └── config.yaml
|
|
||||||
│ └── cis/ # Creative Innovation Studio
|
|
||||||
│ └── ...
|
|
||||||
└── .claude/ # Platform-specific (example)
|
|
||||||
└── agents/
|
|
||||||
```
|
|
||||||
|
|
||||||
### Installation Flow
|
|
||||||
|
|
||||||
1. **Detection**: Check existing installation
|
|
||||||
2. **Selection**: Choose modules interactively or via CLI
|
|
||||||
3. **Configuration**: Collect module-specific settings
|
|
||||||
4. **Installation**: Compile Process and copy files
|
|
||||||
5. **Generation**: Create config files with inheritance
|
|
||||||
6. **Post-Install**: Run module installers
|
|
||||||
7. **Manifest**: Track installed components
|
|
||||||
|
|
||||||
### Key Exclusions
|
|
||||||
|
|
||||||
- `_module-installer/` directories are never copied to destination
|
|
||||||
- module.yaml
|
|
||||||
- `localskip="true"` agents are filtered out
|
|
||||||
- Source `config.yaml` templates are replaced with generated configs
|
|
||||||
|
|
||||||
## Modules
|
|
||||||
|
|
||||||
### Core Module (Required)
|
|
||||||
|
|
||||||
Foundation framework with C.O.R.E. (Collaboration Optimized Reflection Engine)
|
|
||||||
|
|
||||||
- **Components**: Base agents, activation system, advanced elicitation
|
|
||||||
- **Config**: `user_name`, `communication_language`
|
|
||||||
|
|
||||||
### BMM Module
|
|
||||||
|
|
||||||
BMad Method for software development workflows
|
|
||||||
|
|
||||||
- **Components**: PM agent, dev tasks, PRD templates, story generation
|
|
||||||
- **Config**: `project_name`, `tech_docs`, `output_folder`, `story_location`
|
|
||||||
- **Dependencies**: Core
|
|
||||||
|
|
||||||
### CIS Module
|
|
||||||
|
|
||||||
Creative Innovation Studio for design workflows
|
|
||||||
|
|
||||||
- **Components**: Design agents, creative tasks
|
|
||||||
- **Config**: `output_folder`, design preferences
|
|
||||||
- **Dependencies**: Core
|
|
||||||
|
|
||||||
### Module Structure
|
|
||||||
|
|
||||||
```
|
|
||||||
src/modules/{module}/
|
|
||||||
├── _module-installer/ # Not copied to destination
|
|
||||||
│ ├── installer.js # Post-install logic
|
|
||||||
├── module.yaml
|
|
||||||
├── agents/
|
|
||||||
├── tasks/
|
|
||||||
├── templates/
|
|
||||||
└── sub-modules/ # Platform-specific content
|
|
||||||
└── {platform}/
|
|
||||||
├── injections.yaml
|
|
||||||
└── sub-agents/
|
|
||||||
```
|
|
||||||
|
|
||||||
## Configuration System
|
|
||||||
|
|
||||||
### Collection Process
|
|
||||||
|
|
||||||
Modules define prompts in `module.yaml`:
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
project_name:
|
|
||||||
prompt: 'Project title?'
|
|
||||||
default: 'My Project'
|
|
||||||
result: '{value}'
|
|
||||||
|
|
||||||
output_folder:
|
|
||||||
prompt: 'Output location?'
|
|
||||||
default: 'docs'
|
|
||||||
result: '{project-root}/{value}'
|
|
||||||
|
|
||||||
tools:
|
|
||||||
prompt: 'Select tools:'
|
|
||||||
multi-select:
|
|
||||||
- 'Tool A'
|
|
||||||
- 'Tool B'
|
|
||||||
```
|
|
||||||
|
|
||||||
### Configuration Inheritance
|
|
||||||
|
|
||||||
Core values cascade to ALL modules automatically:
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
# core/config.yaml
|
|
||||||
user_name: "Jane"
|
|
||||||
communication_language: "English"
|
|
||||||
|
|
||||||
# bmm/config.yaml (generated)
|
|
||||||
project_name: "My App"
|
|
||||||
tech_docs: "/path/to/docs"
|
|
||||||
# Core Configuration Values (inherited)
|
|
||||||
user_name: "Jane"
|
|
||||||
communication_language: "English"
|
|
||||||
```
|
|
||||||
|
|
||||||
**Reserved Keys**: Core configuration keys cannot be redefined by other modules.
|
|
||||||
|
|
||||||
### Path Placeholders
|
|
||||||
|
|
||||||
- `{project-root}`: Project directory path
|
|
||||||
- `{value}`: User input
|
|
||||||
- `{module}`: Module name
|
|
||||||
- `{core:field}`: Reference core config value
|
|
||||||
|
|
||||||
### Config Generation Rules
|
|
||||||
|
|
||||||
1. ALL installed modules get a `config.yaml` (even without prompts)
|
|
||||||
2. Core values are ALWAYS included in module configs
|
|
||||||
3. Module-specific values come first, core values appended
|
|
||||||
4. Source templates are never copied, only generated configs
|
|
||||||
|
|
||||||
## Platform Integration
|
|
||||||
|
|
||||||
### Supported Platforms
|
|
||||||
|
|
||||||
**Preferred** (Full Integration):
|
|
||||||
|
|
||||||
- Claude Code
|
|
||||||
- Cursor
|
|
||||||
- Windsurf
|
|
||||||
|
|
||||||
**Additional**:
|
|
||||||
Cline, Roo, Rovo Dev,Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Crush, iFlow
|
|
||||||
|
|
||||||
### Platform Features
|
|
||||||
|
|
||||||
1. **Setup Handler** (`tools/cli/installers/lib/ide/{platform}.js`)
|
|
||||||
- Directory creation
|
|
||||||
- Configuration generation
|
|
||||||
- Agent processing
|
|
||||||
|
|
||||||
2. **Content Injection** (`sub-modules/{platform}/injections.yaml`)
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
injections:
|
|
||||||
- file: '_bmad/bmm/agents/pm.md'
|
|
||||||
point: 'pm-agent-instructions'
|
|
||||||
content: |
|
|
||||||
<i>Platform-specific instruction</i>
|
|
||||||
|
|
||||||
subagents:
|
|
||||||
source: 'sub-agents'
|
|
||||||
target: '.claude/agents'
|
|
||||||
files: ['agent.md']
|
|
||||||
```
|
|
||||||
|
|
||||||
3. **Interactive Config**
|
|
||||||
- Subagent selection
|
|
||||||
- Installation scope (project/user)
|
|
||||||
- Feature toggles
|
|
||||||
|
|
||||||
### Injection System
|
|
||||||
|
|
||||||
Platform-specific content without source modification:
|
|
||||||
|
|
||||||
- Inject points marked in source: `<!-- IDE-INJECT-POINT:name -->`
|
|
||||||
- Content added during installation only
|
|
||||||
- Source files remain clean
|
|
||||||
|
|
||||||
## Development Guide
|
|
||||||
|
|
||||||
### Creating a Module
|
|
||||||
|
|
||||||
1. **Structure**
|
|
||||||
|
|
||||||
```
|
|
||||||
src/modules/mymod/
|
|
||||||
├── _module-installer/
|
|
||||||
│ ├── installer.js
|
|
||||||
├── module.yaml
|
|
||||||
├── agents/
|
|
||||||
└── tasks/
|
|
||||||
```
|
|
||||||
|
|
||||||
2. **Configuration** (`module.yaml`)
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
code: mymod
|
|
||||||
name: 'My Module'
|
|
||||||
prompt: 'Welcome message'
|
|
||||||
|
|
||||||
setting_name:
|
|
||||||
prompt: 'Configure X?'
|
|
||||||
default: 'value'
|
|
||||||
```
|
|
||||||
|
|
||||||
3. **Installer** (`installer.js`)
|
|
||||||
```javascript
|
|
||||||
async function install(options) {
|
|
||||||
const { projectRoot, config, installedIDEs, logger } = options;
|
|
||||||
// Custom logic
|
|
||||||
return true;
|
|
||||||
}
|
|
||||||
module.exports = { install };
|
|
||||||
```
|
|
||||||
|
|
||||||
### Adding Platform Support
|
|
||||||
|
|
||||||
1. Create handler: `tools/cli/installers/lib/ide/myplatform.js`
|
|
||||||
2. Extend `BaseIdeSetup` class
|
|
||||||
3. Add sub-module: `src/modules/{mod}/sub-modules/myplatform/`
|
|
||||||
4. Define injections and platform agents
|
|
||||||
|
|
||||||
### Agent Configuration
|
|
||||||
|
|
||||||
Extractable config nodes:
|
|
||||||
|
|
||||||
```xml
|
|
||||||
<agent>
|
|
||||||
<setting agentConfig="true">
|
|
||||||
Default value
|
|
||||||
</setting>
|
|
||||||
</agent>
|
|
||||||
```
|
|
||||||
|
|
||||||
Generated in: `bmad/_config/agents/{module}-{agent}.md`
|
|
||||||
|
|
||||||
## Troubleshooting
|
|
||||||
|
|
||||||
### Common Issues
|
|
||||||
|
|
||||||
| Issue | Solution |
|
|
||||||
| ----------------------- | ------------------------------------ |
|
|
||||||
| Existing installation | Use `bmad update` or remove `_bmad/` |
|
|
||||||
| Module not found | Check `src/modules/` exists |
|
|
||||||
| Config not applied | Verify `_bmad/{module}/config.yaml` |
|
|
||||||
| Missing config.yaml | Fixed: All modules now get configs |
|
|
||||||
| Agent unavailable | Check for `localskip="true"` |
|
|
||||||
| module-installer copied | Fixed: Now excluded from copy |
|
|
||||||
|
|
||||||
### Debug Commands
|
|
||||||
|
|
||||||
```bash
|
|
||||||
bmad install -v # Verbose installation
|
|
||||||
bmad status -v # Detailed status
|
|
||||||
```
|
|
||||||
|
|
||||||
### Best Practices
|
|
||||||
|
|
||||||
1. Run from project root
|
|
||||||
2. Backup `_bmad/_config/` before updates
|
|
||||||
3. Use interactive mode for guidance
|
|
||||||
4. Review generated configs post-install
|
|
||||||
|
|
||||||
## Migration from v4
|
|
||||||
|
|
||||||
| v4 | v6 |
|
|
||||||
| ------------------- | -------------------- |
|
|
||||||
| Scattered files | Centralized `_bmad/` |
|
|
||||||
| Monolithic | Modular |
|
|
||||||
| Manual config | Interactive setup |
|
|
||||||
| Limited IDE support | 15+ platforms |
|
|
||||||
| Source modification | Clean injection |
|
|
||||||
|
|
||||||
## Technical Notes
|
|
||||||
|
|
||||||
### Dependency Resolution
|
|
||||||
|
|
||||||
- Direct dependencies (module → module)
|
|
||||||
- Agent references (cross-module)
|
|
||||||
- Template dependencies
|
|
||||||
- Partial module installation (only required files)
|
|
||||||
- Workflow vendoring for standalone module operation
|
|
||||||
|
|
||||||
## Workflow Vendoring
|
|
||||||
|
|
||||||
**Problem**: Modules that reference workflows from other modules create dependencies, forcing users to install multiple modules even when they only need one.
|
|
||||||
|
|
||||||
**Solution**: Workflow vendoring allows modules to copy workflows from other modules during installation, making them fully standalone.
|
|
||||||
|
|
||||||
### How It Works
|
|
||||||
|
|
||||||
Agents can specify both `workflow` (source location) and `workflow-install` (destination location) in their menu items:
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
menu:
|
|
||||||
- trigger: create-story
|
|
||||||
workflow: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml'
|
|
||||||
workflow-install: '{project-root}/_bmad/bmgd/workflows/4-production/create-story/workflow.yaml'
|
|
||||||
description: 'Create a game feature story'
|
|
||||||
```
|
|
||||||
|
|
||||||
**During Installation:**
|
|
||||||
|
|
||||||
1. **Vendoring Phase**: Before copying module files, the installer:
|
|
||||||
- Scans source agent YAML files for `workflow-install` attributes
|
|
||||||
- Copies entire workflow folders from `workflow` path to `workflow-install` path
|
|
||||||
- Updates vendored `workflow.yaml` files to reference target module's config
|
|
||||||
|
|
||||||
2. **Compilation Phase**: When compiling agents:
|
|
||||||
- If `workflow-install` exists, uses its value for the `workflow` attribute
|
|
||||||
- `workflow-install` is build-time metadata only, never appears in final XML
|
|
||||||
- Compiled agent references vendored workflow location
|
|
||||||
|
|
||||||
3. **Config Update**: Vendored workflows get their `config_source` updated:
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
# Source workflow (in bmm):
|
|
||||||
config_source: "{project-root}/_bmad/bmm/config.yaml"
|
|
||||||
|
|
||||||
# Vendored workflow (in bmgd):
|
|
||||||
config_source: "{project-root}/_bmad/bmgd/config.yaml"
|
|
||||||
```
|
|
||||||
|
|
||||||
**Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case.
|
|
||||||
|
|
||||||
### Example Use Case: BMGD Module
|
|
||||||
|
|
||||||
The BMad Game Development module vendors implementation workflows from BMM:
|
|
||||||
|
|
||||||
- Game Dev Scrum Master agent references BMM workflows
|
|
||||||
- During installation, workflows are copied to `bmgd/workflows/4-production/`
|
|
||||||
- Vendored workflows use BMGD's config (with game-specific settings)
|
|
||||||
- BMGD can be installed without BMM dependency
|
|
||||||
|
|
||||||
### Benefits
|
|
||||||
|
|
||||||
✅ **Module Independence** - No forced dependencies
|
|
||||||
✅ **Clean Namespace** - Workflows live in their module
|
|
||||||
✅ **Config Isolation** - Each module uses its own configuration
|
|
||||||
✅ **Customization Ready** - Vendored workflows can be modified independently
|
|
||||||
✅ **No User Confusion** - Avoid partial module installations
|
|
||||||
|
|
||||||
### File Processing
|
|
||||||
|
|
||||||
- Filters `localskip="true"` agents
|
|
||||||
- Excludes `_module-installer/` directories
|
|
||||||
- Replaces path placeholders at runtime
|
|
||||||
- Injects activation blocks
|
|
||||||
- Vendors cross-module workflows (see Workflow Vendoring below)
|
|
||||||
|
|
||||||
### Web Bundling
|
|
||||||
|
|
||||||
```bash
|
|
||||||
bmad bundle --web # Filter for web deployment
|
|
||||||
npm run validate:bundles # Validate bundles
|
|
||||||
```
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'agent-builder'
|
|
||||||
description: 'agent-builder agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmb/agents/agent-builder.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'module-builder'
|
|
||||||
description: 'module-builder agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmb/agents/module-builder.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'workflow-builder'
|
|
||||||
description: 'workflow-builder agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmb/agents/workflow-builder.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'game-architect'
|
|
||||||
description: 'game-architect agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-architect.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'game-designer'
|
|
||||||
description: 'game-designer agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-designer.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'game-dev'
|
|
||||||
description: 'game-dev agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-dev.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'game-qa'
|
|
||||||
description: 'game-qa agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-qa.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'game-scrum-master'
|
|
||||||
description: 'game-scrum-master agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-scrum-master.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'game-solo-dev'
|
|
||||||
description: 'game-solo-dev agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-solo-dev.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'analyst'
|
|
||||||
description: 'analyst agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmm/agents/analyst.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'architect'
|
|
||||||
description: 'architect agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmm/agents/architect.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'dev'
|
|
||||||
description: 'dev agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmm/agents/dev.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'pm'
|
|
||||||
description: 'pm agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmm/agents/pm.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'quick-flow-solo-dev'
|
|
||||||
description: 'quick-flow-solo-dev agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmm/agents/quick-flow-solo-dev.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'sm'
|
|
||||||
description: 'sm agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmm/agents/sm.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'tea'
|
|
||||||
description: 'tea agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmm/agents/tea.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'tech-writer'
|
|
||||||
description: 'tech-writer agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmm/agents/tech-writer.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'ux-designer'
|
|
||||||
description: 'ux-designer agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/bmm/agents/ux-designer.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'brainstorming-coach'
|
|
||||||
description: 'brainstorming-coach agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/cis/agents/brainstorming-coach.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'creative-problem-solver'
|
|
||||||
description: 'creative-problem-solver agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/cis/agents/creative-problem-solver.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'design-thinking-coach'
|
|
||||||
description: 'design-thinking-coach agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/cis/agents/design-thinking-coach.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'innovation-strategist'
|
|
||||||
description: 'innovation-strategist agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/cis/agents/innovation-strategist.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'presentation-master'
|
|
||||||
description: 'presentation-master agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/cis/agents/presentation-master.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'storyteller'
|
|
||||||
description: 'storyteller agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/cis/agents/storyteller/storyteller.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,14 +0,0 @@
|
||||||
---
|
|
||||||
name: 'bmad-master'
|
|
||||||
description: 'bmad-master agent'
|
|
||||||
---
|
|
||||||
|
|
||||||
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
||||||
|
|
||||||
<agent-activation CRITICAL="TRUE">
|
|
||||||
1. LOAD the FULL agent file from @_bmad/core/agents/bmad-master.md
|
|
||||||
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
||||||
3. Execute ALL activation steps exactly as written in the agent file
|
|
||||||
4. Follow the agent's persona and menu system precisely
|
|
||||||
5. Stay in character throughout the session
|
|
||||||
</agent-activation>
|
|
||||||
|
|
@ -1,127 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Execute the Advanced Elicitation task'
|
|
||||||
---
|
|
||||||
|
|
||||||
# Advanced Elicitation Task
|
|
||||||
|
|
||||||
<task id="_bmad/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
|
|
||||||
methods="{project-root}/_bmad/core/tasks/advanced-elicitation-methods.csv"
|
|
||||||
agent-party="{project-root}/_bmad/_config/agent-manifest.csv">
|
|
||||||
<llm critical="true">
|
|
||||||
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
|
|
||||||
<i>DO NOT skip steps or change the sequence</i>
|
|
||||||
<i>HALT immediately when halt-conditions are met</i>
|
|
||||||
<i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
|
|
||||||
<i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
|
|
||||||
</llm>
|
|
||||||
|
|
||||||
<integration description="When called from workflow">
|
|
||||||
<desc>When called during template workflow processing:</desc>
|
|
||||||
<i>1. Receive or review the current section content that was just generated or</i>
|
|
||||||
<i>2. Apply elicitation methods iteratively to enhance that specific content</i>
|
|
||||||
<i>3. Return the enhanced version back when user selects 'x' to proceed and return back</i>
|
|
||||||
<i>4. The enhanced content replaces the original section content in the output document</i>
|
|
||||||
</integration>
|
|
||||||
|
|
||||||
<flow>
|
|
||||||
<step n="1" title="Method Registry Loading">
|
|
||||||
<action>Load and read {{methods}} and {{agent-party}}</action>
|
|
||||||
|
|
||||||
<csv-structure>
|
|
||||||
<i>category: Method grouping (core, structural, risk, etc.)</i>
|
|
||||||
<i>method_name: Display name for the method</i>
|
|
||||||
<i>description: Rich explanation of what the method does, when to use it, and why it's valuable</i>
|
|
||||||
<i>output_pattern: Flexible flow guide using → arrows (e.g., "analysis → insights → action")</i>
|
|
||||||
</csv-structure>
|
|
||||||
|
|
||||||
<context-analysis>
|
|
||||||
<i>Use conversation history</i>
|
|
||||||
<i>Analyze: content type, complexity, stakeholder needs, risk level, and creative potential</i>
|
|
||||||
</context-analysis>
|
|
||||||
|
|
||||||
<smart-selection>
|
|
||||||
<i>1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential</i>
|
|
||||||
<i>2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV</i>
|
|
||||||
<i>3. Select 5 methods: Choose methods that best match the context based on their descriptions</i>
|
|
||||||
<i>4. Balance approach: Include mix of foundational and specialized techniques as appropriate</i>
|
|
||||||
</smart-selection>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
<step n="2" title="Present Options and Handle Responses">
|
|
||||||
|
|
||||||
<format>
|
|
||||||
**Advanced Elicitation Options (If you launched Party Mode, they will participate randomly)**
|
|
||||||
Choose a number (1-5), [r] to Reshuffle, [a] List All, or [x] to Proceed:
|
|
||||||
|
|
||||||
1. [Method Name]
|
|
||||||
2. [Method Name]
|
|
||||||
3. [Method Name]
|
|
||||||
4. [Method Name]
|
|
||||||
5. [Method Name]
|
|
||||||
r. Reshuffle the list with 5 new options
|
|
||||||
a. List all methods with descriptions
|
|
||||||
x. Proceed / No Further Actions
|
|
||||||
</format>
|
|
||||||
|
|
||||||
<response-handling>
|
|
||||||
<case n="1-5">
|
|
||||||
<i>Execute the selected method using its description from the CSV</i>
|
|
||||||
<i>Adapt the method's complexity and output format based on the current context</i>
|
|
||||||
<i>Apply the method creatively to the current section content being enhanced</i>
|
|
||||||
<i>Display the enhanced version showing what the method revealed or improved</i>
|
|
||||||
<i>CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.</i>
|
|
||||||
<i>CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to
|
|
||||||
follow the instructions given by the user.</i>
|
|
||||||
<i>CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations</i>
|
|
||||||
</case>
|
|
||||||
<case n="r">
|
|
||||||
<i>Select 5 random methods from advanced-elicitation-methods.csv, present new list with same prompt format</i>
|
|
||||||
<i>When selecting, try to think and pick a diverse set of methods covering different categories and approaches, with 1 and 2 being
|
|
||||||
potentially the most useful for the document or section being discovered</i>
|
|
||||||
</case>
|
|
||||||
<case n="x">
|
|
||||||
<i>Complete elicitation and proceed</i>
|
|
||||||
<i>Return the fully enhanced content back to create-doc.md</i>
|
|
||||||
<i>The enhanced content becomes the final version for that section</i>
|
|
||||||
<i>Signal completion back to create-doc.md to continue with next section</i>
|
|
||||||
</case>
|
|
||||||
<case n="a">
|
|
||||||
<i>List all methods with their descriptions from the CSV in a compact table</i>
|
|
||||||
<i>Allow user to select any method by name or number from the full list</i>
|
|
||||||
<i>After selection, execute the method as described in the n="1-5" case above</i>
|
|
||||||
</case>
|
|
||||||
<case n="direct-feedback">
|
|
||||||
<i>Apply changes to current section content and re-present choices</i>
|
|
||||||
</case>
|
|
||||||
<case n="multiple-numbers">
|
|
||||||
<i>Execute methods in sequence on the content, then re-offer choices</i>
|
|
||||||
</case>
|
|
||||||
</response-handling>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
<step n="3" title="Execution Guidelines">
|
|
||||||
<i>Method execution: Use the description from CSV to understand and apply each method</i>
|
|
||||||
<i>Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection")</i>
|
|
||||||
<i>Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)</i>
|
|
||||||
<i>Creative application: Interpret methods flexibly based on context while maintaining pattern consistency</i>
|
|
||||||
<i>Focus on actionable insights</i>
|
|
||||||
<i>Stay relevant: Tie elicitation to specific content being analyzed (the current section from the document being created unless user
|
|
||||||
indicates otherwise)</i>
|
|
||||||
<i>Identify personas: For single or multi-persona methods, clearly identify viewpoints, and use party members if available in memory
|
|
||||||
already</i>
|
|
||||||
<i>Critical loop behavior: Always re-offer the 1-5,r,a,x choices after each method execution</i>
|
|
||||||
<i>Continue until user selects 'x' to proceed with enhanced content, confirm or ask the user what should be accepted from the session</i>
|
|
||||||
<i>Each method application builds upon previous enhancements</i>
|
|
||||||
<i>Content preservation: Track all enhancements made during elicitation</i>
|
|
||||||
<i>Iterative enhancement: Each selected method (1-5) should:</i>
|
|
||||||
<i> 1. Apply to the current enhanced version of the content</i>
|
|
||||||
<i> 2. Show the improvements made</i>
|
|
||||||
<i> 3. Return to the prompt for additional elicitations or completion</i>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
</flow>
|
|
||||||
</task>
|
|
||||||
|
|
||||||
## Module
|
|
||||||
|
|
||||||
BMAD CORE module
|
|
||||||
|
|
@ -1,77 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Execute the Index Docs task'
|
|
||||||
---
|
|
||||||
|
|
||||||
# Index Docs Task
|
|
||||||
|
|
||||||
<task id="_bmad/core/tasks/index-docs" name="Index Docs"
|
|
||||||
description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
|
|
||||||
<llm critical="true">
|
|
||||||
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
|
|
||||||
<i>DO NOT skip steps or change the sequence</i>
|
|
||||||
<i>HALT immediately when halt-conditions are met</i>
|
|
||||||
<i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
|
|
||||||
<i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
|
|
||||||
</llm>
|
|
||||||
|
|
||||||
<flow>
|
|
||||||
<step n="1" title="Scan Directory">
|
|
||||||
<i>List all files and subdirectories in the target location</i>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
<step n="2" title="Group Content">
|
|
||||||
<i>Organize files by type, purpose, or subdirectory</i>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
<step n="3" title="Generate Descriptions">
|
|
||||||
<i>Read each file to understand its actual purpose and create brief (3-10 word) descriptions based on the content, not just the
|
|
||||||
filename</i>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
<step n="4" title="Create/Update Index">
|
|
||||||
<i>Write or update index.md with organized file listings</i>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
</flow>
|
|
||||||
|
|
||||||
<output-format>
|
|
||||||
<example>
|
|
||||||
# Directory Index
|
|
||||||
|
|
||||||
## Files
|
|
||||||
|
|
||||||
- **[filename.ext](./filename.ext)** - Brief description
|
|
||||||
- **[another-file.ext](./another-file.ext)** - Brief description
|
|
||||||
|
|
||||||
## Subdirectories
|
|
||||||
|
|
||||||
### subfolder/
|
|
||||||
|
|
||||||
- **[file1.ext](./subfolder/file1.ext)** - Brief description
|
|
||||||
- **[file2.ext](./subfolder/file2.ext)** - Brief description
|
|
||||||
|
|
||||||
### another-folder/
|
|
||||||
|
|
||||||
- **[file3.ext](./another-folder/file3.ext)** - Brief description
|
|
||||||
</example>
|
|
||||||
|
|
||||||
</output-format>
|
|
||||||
|
|
||||||
<halt-conditions critical="true">
|
|
||||||
<i>HALT if target directory does not exist or is inaccessible</i>
|
|
||||||
<i>HALT if user does not have write permissions to create index.md</i>
|
|
||||||
</halt-conditions>
|
|
||||||
|
|
||||||
<validation>
|
|
||||||
<i>Use relative paths starting with ./</i>
|
|
||||||
<i>Group similar files together</i>
|
|
||||||
<i>Read file contents to generate accurate descriptions - don't guess from filenames</i>
|
|
||||||
<i>Keep descriptions concise but informative (3-10 words)</i>
|
|
||||||
<i>Sort alphabetically within groups</i>
|
|
||||||
<i>Skip hidden files (starting with .) unless specified</i>
|
|
||||||
</validation>
|
|
||||||
</task>
|
|
||||||
|
|
||||||
## Module
|
|
||||||
|
|
||||||
BMAD CORE module
|
|
||||||
|
|
@ -1,120 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Use the Shard Document tool'
|
|
||||||
---
|
|
||||||
|
|
||||||
# Shard Document Tool
|
|
||||||
|
|
||||||
<tool id="_bmad/core/tasks/shard-doc" name="Shard Document"
|
|
||||||
description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections" webskip="true"
|
|
||||||
standalone="true">
|
|
||||||
<objective>Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool</objective>
|
|
||||||
|
|
||||||
<llm critical="true">
|
|
||||||
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
|
|
||||||
<i>DO NOT skip steps or change the sequence</i>
|
|
||||||
<i>HALT immediately when halt-conditions are met</i>
|
|
||||||
<i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
|
|
||||||
<i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
|
|
||||||
</llm>
|
|
||||||
|
|
||||||
<critical-context>
|
|
||||||
<i>Uses `npx @kayvan/markdown-tree-parser` to automatically shard documents by level 2 headings and generate an index</i>
|
|
||||||
</critical-context>
|
|
||||||
|
|
||||||
<flow>
|
|
||||||
<step n="1" title="Get Source Document">
|
|
||||||
<action>Ask user for the source document path if not provided already</action>
|
|
||||||
<action>Verify file exists and is accessible</action>
|
|
||||||
<action>Verify file is markdown format (.md extension)</action>
|
|
||||||
<action if="file not found or not markdown">HALT with error message</action>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
<step n="2" title="Get Destination Folder">
|
|
||||||
<action>Determine default destination: same location as source file, folder named after source file without .md extension</action>
|
|
||||||
<action>Example: /path/to/architecture.md → /path/to/architecture/</action>
|
|
||||||
<action>Ask user for the destination folder path ([y] to confirm use of default: [suggested-path], else enter a new path)</action>
|
|
||||||
<action if="user accepts default">Use the suggested destination path</action>
|
|
||||||
<action if="user provides custom path">Use the custom destination path</action>
|
|
||||||
<action>Verify destination folder exists or can be created</action>
|
|
||||||
<action>Check write permissions for destination</action>
|
|
||||||
<action if="permission denied">HALT with error message</action>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
<step n="3" title="Execute Sharding">
|
|
||||||
<action>Inform user that sharding is beginning</action>
|
|
||||||
<action>Execute command: `npx @kayvan/markdown-tree-parser explode [source-document] [destination-folder]`</action>
|
|
||||||
<action>Capture command output and any errors</action>
|
|
||||||
<action if="command fails">HALT and display error to user</action>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
<step n="4" title="Verify Output">
|
|
||||||
<action>Check that destination folder contains sharded files</action>
|
|
||||||
<action>Verify index.md was created in destination folder</action>
|
|
||||||
<action>Count the number of files created</action>
|
|
||||||
<action if="no files created">HALT with error message</action>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
<step n="5" title="Report Completion">
|
|
||||||
<action>Display completion report to user including:</action>
|
|
||||||
<i>- Source document path and name</i>
|
|
||||||
<i>- Destination folder path</i>
|
|
||||||
<i>- Number of section files created</i>
|
|
||||||
<i>- Confirmation that index.md was created</i>
|
|
||||||
<i>- Any tool output or warnings</i>
|
|
||||||
<action>Inform user that sharding completed successfully</action>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
<step n="6" title="Handle Original Document">
|
|
||||||
<critical>Keeping both the original and sharded versions defeats the purpose of sharding and can cause confusion</critical>
|
|
||||||
<action>Present user with options for the original document:</action>
|
|
||||||
|
|
||||||
<ask>What would you like to do with the original document `[source-document-name]`?
|
|
||||||
|
|
||||||
Options:
|
|
||||||
[d] Delete - Remove the original (recommended - shards can always be recombined)
|
|
||||||
[m] Move to archive - Move original to a backup/archive location
|
|
||||||
[k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
|
|
||||||
|
|
||||||
Your choice (d/m/k):</ask>
|
|
||||||
|
|
||||||
<check if="user selects 'd' (delete)">
|
|
||||||
<action>Delete the original source document file</action>
|
|
||||||
<action>Confirm deletion to user: "✓ Original document deleted: [source-document-path]"</action>
|
|
||||||
<note>The document can be reconstructed from shards by concatenating all section files in order</note>
|
|
||||||
</check>
|
|
||||||
|
|
||||||
<check if="user selects 'm' (move)">
|
|
||||||
<action>Determine default archive location: same directory as source, in an "archive" subfolder</action>
|
|
||||||
<action>Example: /path/to/architecture.md → /path/to/archive/architecture.md</action>
|
|
||||||
<ask>Archive location ([y] to use default: [default-archive-path], or provide custom path):</ask>
|
|
||||||
<action if="user accepts default">Use default archive path</action>
|
|
||||||
<action if="user provides custom path">Use custom archive path</action>
|
|
||||||
<action>Create archive directory if it doesn't exist</action>
|
|
||||||
<action>Move original document to archive location</action>
|
|
||||||
<action>Confirm move to user: "✓ Original document moved to: [archive-path]"</action>
|
|
||||||
</check>
|
|
||||||
|
|
||||||
<check if="user selects 'k' (keep)">
|
|
||||||
<action>Display warning to user:</action>
|
|
||||||
<output>⚠️ WARNING: Keeping both original and sharded versions is NOT recommended.
|
|
||||||
|
|
||||||
This creates confusion because:
|
|
||||||
- The discover_inputs protocol may load the wrong version
|
|
||||||
- Updates to one won't reflect in the other
|
|
||||||
- You'll have duplicate content taking up space
|
|
||||||
|
|
||||||
Consider deleting or archiving the original document.</output>
|
|
||||||
<action>Confirm user choice: "Original document kept at: [source-document-path]"</action>
|
|
||||||
</check>
|
|
||||||
</step>
|
|
||||||
|
|
||||||
</flow>
|
|
||||||
|
|
||||||
<halt-conditions critical="true">
|
|
||||||
<i>HALT if npx command fails or produces no output files</i>
|
|
||||||
</halt-conditions>
|
|
||||||
</tool>
|
|
||||||
|
|
||||||
## Module
|
|
||||||
|
|
||||||
BMAD CORE module
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Creates personalized meal plans through collaborative nutrition planning between an expert facilitator and individual seeking to improve their nutrition habits.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Interactive workflow to build BMAD Core compliant agents with optional brainstorming, persona development, and command structure'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmb/workflows/create-agent/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmb/workflows/create-module/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Create structured standalone workflows using markdown-based step architecture'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmb/workflows/create-workflow/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Edit existing BMAD agents while following all best practices and conventions'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmb/workflows/edit-agent/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Intelligent workflow editor that helps modify existing workflows while following best practices'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmb/workflows/edit-workflow/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Systematic validation of workflows against BMAD standards with adversarial analysis and detailed reporting'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmb/workflows/workflow-compliance-check/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Facilitate game brainstorming sessions with game-specific context, guidance, and game design techniques.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval. Game-specific focus on 60fps, feel, and platform considerations.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/code-review/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/4-production/code-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/4-production/correct-course/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Creates a comprehensive Game Brief through collaborative step-by-step discovery to capture game vision before detailed design.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmgd/workflows/1-preproduction/game-brief/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Creates a comprehensive Game Design Document through collaborative step-by-step discovery between game designer and user.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmgd/workflows/2-design/gdd/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Create the next user story markdown from epics/PRD and architecture, using a standard template and saving to the stories folder'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/create-story/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/4-production/create-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Conversational spec engineering for games - ask questions, investigate code, produce implementation-ready tech-spec.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/bmgd-quick-flow/create-tech-spec/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/bmgd-quick-flow/create-tech-spec/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/dev-story/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/4-production/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Collaborative game architecture workflow for AI-agent consistency. Intelligent, adaptive conversation that produces a decision-focused game architecture document covering engine, systems, networking, and technical design optimized for game development.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/3-technical/game-architecture/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/3-technical/game-architecture/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Interactive game brief creation workflow that guides users through defining their game vision with multiple input sources and conversational collaboration'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/1-preproduction/game-brief/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/1-preproduction/game-brief/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Generate automated game tests for Unity, Unreal, or Godot based on test design scenarios'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/automate/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/gametest/automate/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Initialize game test framework architecture for Unity, Unreal Engine, or Godot projects'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/test-framework/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/gametest/test-framework/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Design performance testing strategy for frame rate, memory, and loading times'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/performance/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/gametest/performance/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Create structured playtesting sessions for gameplay validation and user feedback'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/playtest-plan/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/gametest/playtest-plan/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Create comprehensive game test scenarios covering gameplay, progression, and quality requirements'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/test-design/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/gametest/test-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Review test quality, coverage, and identify gaps in game testing'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/test-review/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/gametest/test-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Game Design Document workflow for all game project levels - from small prototypes to full AAA games. Generates comprehensive GDD with game mechanics, systems, progression, and implementation guidance.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/2-design/gdd/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/2-design/gdd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing game code. Optimized for LLM context efficiency.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmgd/workflows/3-technical/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Narrative design workflow for story-driven games. Creates comprehensive narrative documentation including story structure, character arcs, world-building, dialogue systems, and production planning.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/2-design/narrative/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/2-design/narrative/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Flexible game development - execute tech-specs, implement features, or refactor code with game-specific considerations.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Rapid game prototyping - quickly test gameplay ideas, mechanics, or features with minimal setup.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/retrospective/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/4-production/retrospective/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Summarize sprint-status.yaml for game project, surface risks, and route to the right implementation workflow.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/sprint-status/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/4-production/sprint-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Initialize a new BMGD game project by determining level, type, and creating workflow path'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/workflow-status/init/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/workflow-status/init/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Lightweight status checker - answers ""what should I do now?"" for any game dev agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/workflow-status/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmgd/workflows/workflow-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/code-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Create data flow diagrams (DFD) in Excalidraw format'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Create a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Create website or app wireframes in Excalidraw format'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Creates a comprehensive PRD through collaborative step-by-step discovery between two product managers working as peers.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/create-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Work with a peer UX Design expert to plan your applications UX patterns, look and feel.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/document-project/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/document-project/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmm/workflows/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Flexible development - execute tech-specs OR direct instructions with optional planning.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,5 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @\_bmad/bmm/workflows/1-analysis/research/workflow.md, READ its entire contents and follow its directions exactly!
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Generate failing acceptance tests before implementation using TDD red-green-refactor cycle'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/atdd/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/testarch/atdd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/automate/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/testarch/automate/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/ci/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/testarch/ci/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/framework/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/testarch/framework/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/test-design/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/testarch/test-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Review test quality using comprehensive knowledge base and best practices validation'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/test-review/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/testarch/test-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/trace/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/testarch/trace/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Initialize a new BMM project by determining level, type, and creating workflow path'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/workflow-status/init/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/workflow-status/init/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Lightweight status checker - answers ""what should I do now?"" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/workflow-status/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/bmm/workflows/workflow-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/cis/workflows/design-thinking/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/cis/workflows/design-thinking/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/cis/workflows/innovation-strategy/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/cis/workflows/innovation-strategy/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
||||||
---
|
|
||||||
description: 'Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.'
|
|
||||||
---
|
|
||||||
|
|
||||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
|
||||||
|
|
||||||
<steps CRITICAL="TRUE">
|
|
||||||
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
|
|
||||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/cis/workflows/problem-solving/workflow.yaml
|
|
||||||
3. Pass the yaml path _bmad/cis/workflows/problem-solving/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
|
||||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
|
||||||
5. Save outputs after EACH section when generating any documents from templates
|
|
||||||
</steps>
|
|
||||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue