fix: improve code in the installer to be more memory efficient
This commit is contained in:
Brian Madison
@@ -1,6 +1,6 @@
|
||||
name: bmad-2d-phaser-game-dev
|
||||
version: 1.10.0
|
||||
short-title: 2D game development with Phaser 3 & TypeScript
|
||||
short-title: Phaser 3 2D Game Dev Pack
|
||||
description: >-
|
||||
2D Game Development expansion pack for BMad Method - Phaser 3 & TypeScript
|
||||
focused
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
name: bmad-2d-unity-game-dev
|
||||
version: 1.1.1
|
||||
short-title: 2D game development with Unity & C#
|
||||
short-title: Unity C# 2D Game Dev Pack
|
||||
description: >-
|
||||
2D Game Development expansion pack for BMad Method - Unity & C#
|
||||
focused
|
||||
|
||||
@@ -1,8 +0,0 @@
|
||||
# BMad Creator Tools
|
||||
|
||||
Tools for creating and extending BMad framework components.
|
||||
|
||||
## Tasks
|
||||
|
||||
- **create-agent**: Create new AI agent definitions
|
||||
- **generate-expansion-pack**: Generate new expansion pack templates
|
||||
@@ -1,66 +0,0 @@
|
||||
# bmad-the-creator
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
|
||||
|
||||
## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
|
||||
|
||||
```yaml
|
||||
IDE-FILE-RESOLUTION:
|
||||
- FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
|
||||
- Dependencies map to {root}/{type}/{name}
|
||||
- type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
|
||||
- Example: create-doc.md → {root}/tasks/create-doc.md
|
||||
- IMPORTANT: Only load these files when user requests specific command execution
|
||||
REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Greet user with your name/role and mention `*help` command
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
- The agent.customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
|
||||
- MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
|
||||
- CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
- STAY IN CHARACTER!
|
||||
- CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
|
||||
agent:
|
||||
name: The Creator
|
||||
id: bmad-the-creator
|
||||
title: BMad Framework Extension Specialist
|
||||
icon: 🏗️
|
||||
whenToUse: Use for creating new agents, expansion packs, and extending the BMad framework
|
||||
customization: null
|
||||
persona:
|
||||
role: Expert BMad Framework Architect & Creator
|
||||
style: Methodical, creative, framework-aware, systematic
|
||||
identity: Master builder who extends BMad capabilities through thoughtful design and deep framework understanding
|
||||
focus: Creating well-structured agents, expansion packs, and framework extensions that follow BMad patterns and conventions
|
||||
core_principles:
|
||||
- Framework Consistency - All creations follow established BMad patterns
|
||||
- Modular Design - Create reusable, composable components
|
||||
- Clear Documentation - Every creation includes proper documentation
|
||||
- Convention Over Configuration - Follow BMad naming and structure patterns
|
||||
- Extensibility First - Design for future expansion and customization
|
||||
- Numbered Options Protocol - Always use numbered lists for user selections
|
||||
commands:
|
||||
- '*help" - Show numbered list of available commands for selection'
|
||||
- '*chat-mode" - Conversational mode with advanced-elicitation for framework design advice'
|
||||
- '*create" - Show numbered list of components I can create (agents, expansion packs)'
|
||||
- '*brainstorm {topic}" - Facilitate structured framework extension brainstorming session'
|
||||
- '*research {topic}" - Generate deep research prompt for framework-specific investigation'
|
||||
- '*elicit" - Run advanced elicitation to clarify extension requirements'
|
||||
- '*exit" - Say goodbye as The Creator, and then abandon inhabiting this persona'
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-agent.md
|
||||
- generate-expansion-pack.md
|
||||
- advanced-elicitation.md
|
||||
- create-deep-research-prompt.md
|
||||
templates:
|
||||
- agent-tmpl.yaml
|
||||
- expansion-pack-plan-tmpl.yaml
|
||||
```
|
||||
@@ -1,6 +0,0 @@
|
||||
name: bmad-creator-tools
|
||||
version: 1.9.0
|
||||
short-title: Tools for creating BMad framework components
|
||||
description: Tools for creating and extending BMad framework components.
|
||||
author: Brian (BMad)
|
||||
slashPrefix: bmadCreator
|
||||
@@ -1,200 +0,0 @@
|
||||
# Create Agent Task
|
||||
|
||||
This task guides you through creating a new BMad agent following the standard template.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- Agent template: `../templates/agent-tmpl.md`
|
||||
- Target directory: `.bmad-core/agents/`
|
||||
|
||||
## Steps
|
||||
|
||||
### 1. Gather Agent Information
|
||||
|
||||
Collect the following information from the user:
|
||||
|
||||
- **Agent ID**: Unique identifier (lowercase, hyphens allowed, e.g., `data-analyst`)
|
||||
- **Agent Name**: Display name (e.g., `Data Analyst`)
|
||||
- **Agent Title**: Professional title (e.g., `Data Analysis Specialist`)
|
||||
- **Role Description**: Brief description of the agent's primary role
|
||||
- **Communication Style**: How the agent communicates (e.g., `analytical, data-driven, clear`)
|
||||
- **Identity**: Detailed description of who this agent is
|
||||
- **Focus Areas**: Primary areas of expertise and focus
|
||||
- **Core Principles**: 3-5 guiding principles for the agent
|
||||
- **Customization**: Optional specific behaviors or overrides
|
||||
|
||||
### 2. Define Agent Capabilities
|
||||
|
||||
**IMPORTANT**:
|
||||
|
||||
- If your agent will perform any actions → You MUST create corresponding tasks in `.bmad-core/tasks/`
|
||||
- If your agent will create any documents → You MUST create templates in `.bmad-core/templates/` AND include the `create-doc` task
|
||||
|
||||
Determine:
|
||||
|
||||
- **Custom Commands**: Agent-specific commands beyond the defaults
|
||||
- **Required Tasks**: Tasks from `.bmad-core/tasks/` the agent needs
|
||||
- For any action the agent performs, a corresponding task file must exist
|
||||
- Always include `create-doc` if the agent creates any documents
|
||||
- **Required Templates**: Templates from `.bmad-core/templates/` the agent uses
|
||||
- For any document the agent can create, a template must exist
|
||||
- **Required Checklists**: Checklists the agent references
|
||||
- **Required Data**: Data files the agent needs access to
|
||||
- **Required Utils**: Utility files the agent uses
|
||||
|
||||
### 3. Handle Missing Dependencies
|
||||
|
||||
**Protocol for Missing Tasks/Templates:**
|
||||
|
||||
1. Check if each required task/template exists
|
||||
2. For any missing items:
|
||||
- Create a basic version following the appropriate template
|
||||
- Track what was created in a list
|
||||
3. Continue with agent creation
|
||||
4. At the end, present a summary of all created items
|
||||
|
||||
**Track Created Items:**
|
||||
|
||||
```text
|
||||
Created during agent setup:
|
||||
- Tasks:
|
||||
- [ ] task-name-1.md
|
||||
- [ ] task-name-2.md
|
||||
- Templates:
|
||||
- [ ] template-name-1.md
|
||||
- [ ] template-name-2.md
|
||||
```
|
||||
|
||||
### 4. Create Agent File
|
||||
|
||||
1. Copy the template from `.bmad-core/templates/agent-tmpl.md`
|
||||
2. Replace all placeholders with gathered information:
|
||||
|
||||
- `[AGENT_ID]` → agent id
|
||||
- `[AGENT_NAME]` → agent name
|
||||
- `[AGENT_TITLE]` → agent title
|
||||
- `[AGENT_ROLE_DESCRIPTION]` → role description
|
||||
- `[COMMUNICATION_STYLE]` → communication style
|
||||
- `[AGENT_IDENTITY_DESCRIPTION]` → identity description
|
||||
- `[PRIMARY_FOCUS_AREAS]` → focus areas
|
||||
- `[PRINCIPLE_X]` → core principles
|
||||
- `[OPTIONAL_CUSTOMIZATION]` → customization (or remove if none)
|
||||
- `[DEFAULT_MODE_DESCRIPTION]` → description of default chat mode
|
||||
- `[STARTUP_INSTRUCTIONS]` → what the agent should do on activation
|
||||
- Add custom commands, tasks, templates, etc.
|
||||
|
||||
3. Save as `.bmad-core/agents/[agent-id].md`
|
||||
|
||||
### 4. Validate Agent
|
||||
|
||||
Ensure:
|
||||
|
||||
- All placeholders are replaced
|
||||
- Dependencies (tasks, templates, etc.) actually exist
|
||||
- Commands are properly formatted
|
||||
- YAML structure is valid
|
||||
|
||||
### 5. Build and Test
|
||||
|
||||
1. Run `npm run build:agents` to include in builds
|
||||
2. Test agent activation and commands
|
||||
3. Verify all dependencies load correctly
|
||||
|
||||
### 6. Final Summary
|
||||
|
||||
Present to the user:
|
||||
|
||||
```text
|
||||
✅ Agent Created: [agent-name]
|
||||
Location: .bmad-core/agents/[agent-id].md
|
||||
|
||||
📝 Dependencies Created:
|
||||
Tasks:
|
||||
- ✅ task-1.md - [brief description]
|
||||
- ✅ task-2.md - [brief description]
|
||||
|
||||
Templates:
|
||||
- ✅ template-1.md - [brief description]
|
||||
- ✅ template-2.md - [brief description]
|
||||
|
||||
⚠️ Next Steps:
|
||||
1. Review and customize the created tasks/templates
|
||||
2. Run npm run build:agents
|
||||
3. Test the agent thoroughly
|
||||
```
|
||||
|
||||
## Template Reference
|
||||
|
||||
The agent template structure:
|
||||
|
||||
- **activation-instructions**: How the AI should interpret the file
|
||||
- **agent**: Basic agent metadata
|
||||
- **persona**: Character and behavior definition
|
||||
- **startup**: Initial actions on activation
|
||||
- **commands**: Available commands (always include defaults)
|
||||
- **dependencies**: Required resources organized by type
|
||||
|
||||
## Example Usage
|
||||
|
||||
```yaml
|
||||
agent:
|
||||
name: Data Analyst
|
||||
id: data-analyst
|
||||
title: Data Analysis Specialist
|
||||
persona:
|
||||
role: Expert in data analysis, visualization, and insights extraction
|
||||
style: analytical, data-driven, clear, methodical
|
||||
identity: I am a seasoned data analyst who transforms raw data into actionable insights
|
||||
focus: data exploration, statistical analysis, visualization, reporting
|
||||
core_principles:
|
||||
- Data integrity and accuracy above all
|
||||
- Clear communication of complex findings
|
||||
- Actionable insights over raw numbers
|
||||
```
|
||||
|
||||
## Creating Missing Dependencies
|
||||
|
||||
When a required task or template doesn't exist:
|
||||
|
||||
1. **For Missing Tasks**: Create using `.bmad-core/templates/task-template.md`
|
||||
|
||||
- Name it descriptively (e.g., `analyze-metrics.md`)
|
||||
- Define clear steps for the action
|
||||
- Include any required inputs/outputs
|
||||
|
||||
2. **For Missing Templates**: Create a basic structure
|
||||
|
||||
- Name it descriptively (e.g., `metrics-report-template.md`)
|
||||
- Include placeholders for expected content
|
||||
- Add sections relevant to the document type
|
||||
|
||||
3. **Always Track**: Keep a list of everything created to report at the end
|
||||
|
||||
## Important Reminders
|
||||
|
||||
### Tasks and Templates Requirement
|
||||
|
||||
- **Every agent action needs a task**: If an agent can "analyze data", there must be an `analyze-data.md` task
|
||||
- **Every document type needs a template**: If an agent can create reports, there must be a `report-template.md`
|
||||
- **Document creation requires**: Both the template AND the `create-doc` task in dependencies
|
||||
|
||||
### Example Dependencies
|
||||
|
||||
```yaml
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-doc
|
||||
- analyze-requirements
|
||||
- generate-report
|
||||
templates:
|
||||
- requirements-doc
|
||||
- analysis-report
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Keep agent definitions focused and specific
|
||||
- Ensure dependencies are minimal and necessary
|
||||
- Test thoroughly before distribution
|
||||
- Follow existing agent patterns for consistency
|
||||
- Remember: No task = agent can't do it, No template = agent can't create it
|
||||
File diff suppressed because it is too large
Load Diff
@@ -1,178 +0,0 @@
|
||||
template:
|
||||
id: agent-teams-template-v2
|
||||
name: Agent Team Configuration
|
||||
version: 2.0
|
||||
output:
|
||||
format: yaml
|
||||
filename: "agent-teams/{{team_name}}.yaml"
|
||||
title: "{{team_name}}"
|
||||
|
||||
workflow:
|
||||
mode: interactive
|
||||
|
||||
sections:
|
||||
- id: header
|
||||
title: Agent Team Configuration Template
|
||||
instruction: |
|
||||
This template is for creating agent team configurations in YAML format. Follow the structure carefully and replace all placeholders with appropriate values. The team name should reflect the team's purpose and domain focus.
|
||||
|
||||
- id: yaml-configuration
|
||||
type: code
|
||||
language: yaml
|
||||
template: |
|
||||
bundle:
|
||||
name: {{team_display_name}}
|
||||
icon: {{team_emoji}}
|
||||
description: {{team_description}}
|
||||
|
||||
agents:
|
||||
{{agent_list}}
|
||||
|
||||
workflows:
|
||||
{{workflow_list}}
|
||||
instruction: |
|
||||
Use format "Team [Descriptor]" for generic teams or "[Domain] Team" for specialized teams. Examples: "Team Fullstack", "Healthcare Team", "Legal Team"
|
||||
|
||||
Choose a single emoji that best represents the team's function or name
|
||||
|
||||
Write a concise description (1 sentence) that explains:
|
||||
1. The team's primary purpose
|
||||
2. What types of projects they handle
|
||||
3. Any special capabilities or focus areas
|
||||
4. Keep it short as its displayed in menus
|
||||
Example: "Full Stack Ideation Web App Team." or "Startup Business Coaching team"
|
||||
|
||||
List the agents that make up this team. Guidelines:
|
||||
- Use shortened agent names (e.g., 'analyst' not 'business-analyst')
|
||||
- Include 'bmad-orchestrator' for bmad-core teams as the coordinator
|
||||
- Only use '*' for an all-inclusive team (rare)
|
||||
- Order agents logically by workflow (analysis → design → development → testing)
|
||||
- For expansion packs, include both core agents and custom agents
|
||||
|
||||
Define the workflows this team can execute that will guide the user through a multi-step multi agent process. Guidelines:
|
||||
- Use null if the team doesn't have predefined workflows
|
||||
- Workflow names should be descriptive
|
||||
- use domain-specific workflow names
|
||||
sections:
|
||||
- id: standard-team
|
||||
condition: Standard team configuration
|
||||
template: |
|
||||
# Core workflow agents
|
||||
- bmad-orchestrator # Team coordinator
|
||||
- analyst # Requirements and analysis
|
||||
- pm # Product management
|
||||
- architect # System design
|
||||
- dev # Development
|
||||
- qa # Quality assurance
|
||||
- id: minimal-team
|
||||
condition: Minimal team configuration
|
||||
template: |
|
||||
# Minimal team for quick iterations
|
||||
- bmad-orchestrator # Team coordinator
|
||||
- architect # Design and planning
|
||||
- dev # Implementation
|
||||
- id: specialized-team
|
||||
condition: Domain-specific team
|
||||
template: |
|
||||
# Domain-specific team composition
|
||||
- {{domain}}-orchestrator # Domain coordinator
|
||||
- {{agent_short_name}} # {{agent_role_description}}
|
||||
- id: all-agents
|
||||
condition: Include all available agents
|
||||
template: |
|
||||
- '*' # Include all available agents
|
||||
- id: no-workflows
|
||||
condition: No predefined workflows
|
||||
template: |
|
||||
null # No predefined workflows
|
||||
- id: standard-workflows
|
||||
condition: Standard project workflows
|
||||
template: |
|
||||
# New project workflows
|
||||
- greenfield-fullstack # New full-stack application
|
||||
- greenfield-service # New backend service
|
||||
- greenfield-ui # New frontend application
|
||||
|
||||
# Existing project workflows
|
||||
- brownfield-fullstack # Enhance existing full-stack app
|
||||
- brownfield-service # Enhance existing service
|
||||
- brownfield-ui # Enhance existing UI
|
||||
- id: domain-workflows
|
||||
condition: Domain-specific workflows
|
||||
template: |
|
||||
# Domain-specific workflows
|
||||
- {{workflow_name}} # {{workflow_description}}
|
||||
|
||||
- id: examples
|
||||
title: Examples
|
||||
sections:
|
||||
- id: example-1
|
||||
title: "Example 1: Standard fullstack team"
|
||||
type: code
|
||||
language: yaml
|
||||
template: |
|
||||
bundle:
|
||||
name: Team Fullstack
|
||||
icon: 🚀
|
||||
description: Complete agile team for full-stack web applications. Handles everything from requirements to deployment.
|
||||
agents:
|
||||
- bmad-orchestrator
|
||||
- analyst
|
||||
- pm
|
||||
- architect
|
||||
- dev
|
||||
- qa
|
||||
- ux-expert
|
||||
workflows:
|
||||
- greenfield-fullstack
|
||||
- greenfield-service
|
||||
- greenfield-ui
|
||||
- brownfield-fullstack
|
||||
- brownfield-service
|
||||
- brownfield-ui
|
||||
- id: example-2
|
||||
title: "Example 2: Healthcare expansion pack team"
|
||||
type: code
|
||||
language: yaml
|
||||
template: |
|
||||
bundle:
|
||||
name: Healthcare Compliance Team
|
||||
icon: ⚕️
|
||||
description: Specialized team for healthcare applications with HIPAA compliance focus. Manages clinical workflows and regulatory requirements.
|
||||
agents:
|
||||
- healthcare-orchestrator
|
||||
- clinical-analyst
|
||||
- compliance-officer
|
||||
- architect
|
||||
- dev
|
||||
- qa
|
||||
workflows:
|
||||
- healthcare-patient-portal
|
||||
- healthcare-compliance-audit
|
||||
- clinical-trial-management
|
||||
- id: example-3
|
||||
title: "Example 3: Minimal IDE team"
|
||||
type: code
|
||||
language: yaml
|
||||
template: |
|
||||
bundle:
|
||||
name: Team IDE Minimal
|
||||
icon: ⚡
|
||||
description: Minimal team for IDE usage. Just the essentials for quick development.
|
||||
agents:
|
||||
- bmad-orchestrator
|
||||
- architect
|
||||
- dev
|
||||
workflows: null
|
||||
|
||||
- id: creation-instructions
|
||||
instruction: |
|
||||
When creating a new team configuration:
|
||||
|
||||
1. Choose the most appropriate condition block based on team type
|
||||
2. Remove all unused condition blocks
|
||||
3. Replace all placeholders with actual values
|
||||
4. Ensure agent names match available agents in the system
|
||||
5. Verify workflow names match available workflows
|
||||
6. Save as team-[descriptor].yaml or [domain]-team.yaml
|
||||
7. Place in the agent-teams directory of the appropriate location
|
||||
@@ -1,154 +0,0 @@
|
||||
template:
|
||||
id: agent-template-v2
|
||||
name: Agent Definition
|
||||
version: 2.0
|
||||
output:
|
||||
format: markdown
|
||||
filename: "agents/{{agent_id}}.md"
|
||||
title: "{{agent_id}}"
|
||||
|
||||
workflow:
|
||||
mode: interactive
|
||||
|
||||
sections:
|
||||
- id: header
|
||||
title: "{{agent_id}}"
|
||||
instruction: |
|
||||
This is an agent definition template. When creating a new agent:
|
||||
|
||||
1. ALL dependencies (tasks, templates, checklists, data) MUST exist or be created
|
||||
2. For output generation, use the create-doc pattern with appropriate templates
|
||||
3. Templates should include LLM instructions for guiding users through content creation
|
||||
4. Character personas should be consistent and domain-appropriate
|
||||
5. Follow the numbered options protocol for all user interactions
|
||||
|
||||
- id: agent-definition
|
||||
content: |
|
||||
CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
|
||||
sections:
|
||||
- id: yaml-definition
|
||||
type: code
|
||||
language: yaml
|
||||
template: |
|
||||
activation-instructions:
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
- Command
|
||||
|
||||
agent:
|
||||
name: {{agent_name}}
|
||||
id: {{agent_id}}
|
||||
title: {{agent_title}}
|
||||
customization: {{optional_customization}}
|
||||
|
||||
persona:
|
||||
role: {{agent_role_description}}
|
||||
style: {{communication_style}}
|
||||
identity: {{agent_identity_description}}
|
||||
focus: {{primary_focus_areas}}
|
||||
|
||||
core_principles:
|
||||
- {{principle_1}}
|
||||
- {{principle_2}}
|
||||
- {{principle_3}}
|
||||
# Add more principles as needed
|
||||
|
||||
startup:
|
||||
- Greet the user with your name and role, and inform of the *help command.
|
||||
- {{startup_instruction_1}}
|
||||
- {{startup_instruction_2}}
|
||||
|
||||
commands:
|
||||
- "*help" - Show: numbered list of the following commands to allow selection
|
||||
- "*chat-mode" - (Default) {{default_mode_description}}
|
||||
- "*create-doc {template}" - Create doc (no template = show available templates)
|
||||
{{custom_commands}}
|
||||
- "*exit" - Say goodbye as the {{agent_title}}, and then abandon inhabiting this persona
|
||||
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-doc # Required if agent creates documents from templates
|
||||
{{task_list}}
|
||||
|
||||
templates:
|
||||
{{template_list}}
|
||||
|
||||
checklists:
|
||||
{{checklist_list}}
|
||||
|
||||
data:
|
||||
{{data_list}}
|
||||
|
||||
utils:
|
||||
- template-format # Required if using templates
|
||||
{{util_list}}
|
||||
instruction: |
|
||||
For output generation tasks, always use create-doc with templates rather than custom tasks.
|
||||
Example: Instead of a "create-blueprint" task, use "*create-doc blueprint-tmpl"
|
||||
The template should contain LLM instructions for guiding users through the creation process
|
||||
|
||||
Only create custom tasks for actions that don't produce documents, like analysis, validation, or process execution
|
||||
|
||||
CRITICAL - All dependencies listed here MUST exist in the expansion pack or be created:
|
||||
- Tasks: Must exist in tasks/ directory (include create-doc if using templates)
|
||||
- Templates: Must exist in templates/ directory with proper LLM instructions
|
||||
- Checklists: Must exist in checklists/ directory for quality validation
|
||||
- Data: Must exist in data/ directory or be documented as user-required
|
||||
- Utils: Must exist in utils/ directory (include template-format if using templates)
|
||||
|
||||
- id: example
|
||||
title: Example: Construction Contractor Agent
|
||||
type: code
|
||||
language: yaml
|
||||
template: |
|
||||
activation-instructions:
|
||||
- Follow all instructions in this file
|
||||
- Stay in character as Marcus Thompson, Construction Manager
|
||||
- Use numbered options for all interactions
|
||||
agent:
|
||||
name: Marcus Thompson
|
||||
id: construction-contractor
|
||||
title: Construction Project Manager
|
||||
customization: null
|
||||
persona:
|
||||
role: Licensed general contractor with 20 years experience
|
||||
style: Professional, detail-oriented, safety-conscious
|
||||
identity: Former site foreman who worked up to project management
|
||||
focus: Building design, code compliance, project scheduling, cost estimation
|
||||
core_principles:
|
||||
- Safety first - all designs must prioritize worker and occupant safety
|
||||
- Code compliance - ensure all work meets local building codes
|
||||
- Quality craftsmanship - no shortcuts on structural integrity
|
||||
startup:
|
||||
- Greet as Marcus Thompson, Construction Project Manager
|
||||
- Briefly mention your experience and readiness to help
|
||||
- Ask what type of construction project they're planning
|
||||
- DO NOT auto-execute any commands
|
||||
commands:
|
||||
- '*help" - Show numbered list of available commands'
|
||||
- '*chat-mode" - Discuss construction projects and provide expertise'
|
||||
- '*create-doc blueprint-tmpl" - Create architectural blueprints'
|
||||
- '*create-doc estimate-tmpl" - Create project cost estimate'
|
||||
- '*create-doc schedule-tmpl" - Create construction schedule'
|
||||
- '*validate-plans" - Review plans for code compliance'
|
||||
- '*safety-assessment" - Evaluate safety considerations'
|
||||
- '*exit" - Say goodbye as Marcus and exit'
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-doc
|
||||
- validate-plans
|
||||
- safety-assessment
|
||||
templates:
|
||||
- blueprint-tmpl
|
||||
- estimate-tmpl
|
||||
- schedule-tmpl
|
||||
checklists:
|
||||
- blueprint-checklist
|
||||
- safety-checklist
|
||||
data:
|
||||
- building-codes.md
|
||||
- materials-guide.md
|
||||
utils:
|
||||
- template-format
|
||||
@@ -1,120 +0,0 @@
|
||||
template:
|
||||
id: expansion-pack-plan-template-v2
|
||||
name: Expansion Pack Plan
|
||||
version: 2.0
|
||||
output:
|
||||
format: markdown
|
||||
filename: "{{pack_name}}-expansion-pack-plan.md"
|
||||
title: "{{pack_display_name}} Expansion Pack Plan"
|
||||
|
||||
workflow:
|
||||
mode: interactive
|
||||
|
||||
sections:
|
||||
- id: overview
|
||||
title: Overview
|
||||
template: |
|
||||
- **Pack Name**: {{pack_identifier}}
|
||||
- **Display Name**: {{full_expansion_pack_name}}
|
||||
- **Description**: {{brief_description}}
|
||||
- **Target Domain**: {{industry_domain}}
|
||||
- **Author**: {{author_name_organization}}
|
||||
|
||||
- id: problem-statement
|
||||
title: Problem Statement
|
||||
instruction: What specific challenges does this expansion pack solve?
|
||||
template: "{{problem_description}}"
|
||||
|
||||
- id: target-users
|
||||
title: Target Users
|
||||
instruction: Who will benefit from this expansion pack?
|
||||
template: "{{target_user_description}}"
|
||||
|
||||
- id: components
|
||||
title: Components to Create
|
||||
sections:
|
||||
- id: agents
|
||||
title: Agents
|
||||
type: checklist
|
||||
instruction: List all agents to be created with their roles and dependencies
|
||||
items:
|
||||
- id: orchestrator
|
||||
template: |
|
||||
`{{pack_name}}-orchestrator` - **REQUIRED**: Master orchestrator for {{domain}} workflows
|
||||
- Key commands: {{command_list}}
|
||||
- Manages: {{orchestration_scope}}
|
||||
- id: agent-list
|
||||
repeatable: true
|
||||
template: |
|
||||
`{{agent_name}}` - {{role_description}}
|
||||
- Tasks used: {{task_list}}
|
||||
- Templates used: {{template_list}}
|
||||
- Data required: {{data_requirements}}
|
||||
|
||||
- id: tasks
|
||||
title: Tasks
|
||||
type: checklist
|
||||
instruction: List all tasks to be created
|
||||
repeatable: true
|
||||
template: "`{{task_name}}.md` - {{purpose}} (used by: {{using_agents}})"
|
||||
|
||||
- id: templates
|
||||
title: Templates
|
||||
type: checklist
|
||||
instruction: List all templates to be created
|
||||
repeatable: true
|
||||
template: "`{{template_name}}-tmpl.md` - {{document_type}} (used by: {{using_components}})"
|
||||
|
||||
- id: checklists
|
||||
title: Checklists
|
||||
type: checklist
|
||||
instruction: List all checklists to be created
|
||||
repeatable: true
|
||||
template: "`{{checklist_name}}-checklist.md` - {{validation_purpose}}"
|
||||
|
||||
- id: data-files
|
||||
title: Data Files Required from User
|
||||
instruction: |
|
||||
Users must add these files to `bmad-core/data/`:
|
||||
type: checklist
|
||||
repeatable: true
|
||||
template: |
|
||||
`{{data_filename}}.{{extension}}` - {{content_description}}
|
||||
- Format: {{file_format}}
|
||||
- Purpose: {{why_needed}}
|
||||
- Example: {{brief_example}}
|
||||
|
||||
- id: workflow-overview
|
||||
title: Workflow Overview
|
||||
type: numbered-list
|
||||
instruction: Describe the typical workflow steps
|
||||
template: "{{workflow_step}}"
|
||||
|
||||
- id: integration-points
|
||||
title: Integration Points
|
||||
template: |
|
||||
- Depends on core agents: {{core_agent_dependencies}}
|
||||
- Extends teams: {{team_updates}}
|
||||
|
||||
- id: success-criteria
|
||||
title: Success Criteria
|
||||
type: checklist
|
||||
items:
|
||||
- "All components created and cross-referenced"
|
||||
- "No orphaned task/template references"
|
||||
- "Data requirements clearly documented"
|
||||
- "Orchestrator provides clear workflow"
|
||||
- "README includes setup instructions"
|
||||
|
||||
- id: user-approval
|
||||
title: User Approval
|
||||
type: checklist
|
||||
items:
|
||||
- "Plan reviewed by user"
|
||||
- "Approval to proceed with implementation"
|
||||
|
||||
- id: next-steps
|
||||
content: |
|
||||
---
|
||||
|
||||
**Next Steps**: Once approved, proceed with Phase 3 implementation starting with the orchestrator agent.
|
||||
@@ -1,6 +1,6 @@
|
||||
name: bmad-infrastructure-devops
|
||||
version: 1.9.0
|
||||
short-title: Infrastructure and DevOps capabilities
|
||||
short-title: Infrastructure DevOps Pack
|
||||
description: >-
|
||||
This expansion pack extends BMad Method with comprehensive infrastructure and
|
||||
DevOps capabilities. It's designed for teams that need to define, implement,
|
||||
|
||||
Reference in New Issue
Block a user