web build optimization
This commit is contained in:
Brian Madison
63
dist/agents/bmad-orchestrator.txt
vendored
63
dist/agents/bmad-orchestrator.txt
vendored
@@ -8,14 +8,14 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
|
||||
|
||||
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
|
||||
|
||||
- `==================== START: folder#filename ====================`
|
||||
- `==================== END: folder#filename ====================`
|
||||
- `==================== START: .bmad-core/folder/filename.md ====================`
|
||||
- `==================== END: .bmad-core/folder/filename.md ====================`
|
||||
|
||||
When you need to reference a resource mentioned in your instructions:
|
||||
|
||||
- Look for the corresponding START/END tags
|
||||
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
|
||||
- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
|
||||
- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
|
||||
- If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
|
||||
|
||||
**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
|
||||
|
||||
@@ -29,8 +29,8 @@ dependencies:
|
||||
|
||||
These references map directly to bundle sections:
|
||||
|
||||
- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
|
||||
- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
|
||||
- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
|
||||
- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
|
||||
|
||||
3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
|
||||
|
||||
@@ -38,7 +38,8 @@ These references map directly to bundle sections:
|
||||
|
||||
---
|
||||
|
||||
==================== START: agents#bmad-orchestrator ====================
|
||||
|
||||
==================== START: .bmad-core/agents/bmad-orchestrator.md ====================
|
||||
# bmad-orchestrator
|
||||
|
||||
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:
|
||||
@@ -69,7 +70,7 @@ startup:
|
||||
- Announce: Introduce yourself as the BMad Orchestrator, explain you can coordinate agents and workflows
|
||||
- IMPORTANT: Tell users that all commands start with * (e.g., *help, *agent, *workflow)
|
||||
- Mention *help shows all available commands and options
|
||||
- Check for active workflow plan using utils#plan-management
|
||||
- Check for active workflow plan using .bmad-core/utils/plan-management.md
|
||||
- 'If plan exists: Show 📋 Active plan: {workflow} ({progress}% complete). Use *plan-status for details.'
|
||||
- 'If plan exists: Suggest next action based on plan progress'
|
||||
- Assess user goal against available agents and workflows in this bundle
|
||||
@@ -175,9 +176,9 @@ dependencies:
|
||||
- workflow-management
|
||||
- template-format
|
||||
```
|
||||
==================== END: agents#bmad-orchestrator ====================
|
||||
==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
|
||||
|
||||
==================== START: tasks#advanced-elicitation ====================
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -295,9 +296,9 @@ Choose a number (0-8) or 9 to proceed:
|
||||
- **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
|
||||
- **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
|
||||
- **Maintain Flow**: Keep the process moving efficiently
|
||||
==================== END: tasks#advanced-elicitation ====================
|
||||
==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: tasks#create-doc ====================
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
# Create Document from Template Task
|
||||
|
||||
## Purpose
|
||||
@@ -317,7 +318,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
|
||||
|
||||
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
|
||||
|
||||
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
|
||||
- If `workflow.trackProgress: true`, check for active plan using .bmad-core/utils/plan-management.md
|
||||
- If plan exists and this document creation is part of the plan:
|
||||
- Verify this is the expected next step
|
||||
- If out of sequence and `enforceSequence: true`, warn user and halt without user override
|
||||
@@ -326,7 +327,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
|
||||
|
||||
### 1. Identify Template
|
||||
|
||||
- Load from `templates#*` or `{root}/templates directory`
|
||||
- Load from `.bmad-core/templates/*.md` or `.bmad-core/templates directory`
|
||||
- Agent-specific templates are listed in agent's dependencies
|
||||
- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
|
||||
|
||||
@@ -344,14 +345,14 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
|
||||
|
||||
### 4. Key Execution Patterns
|
||||
|
||||
**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
|
||||
**When you see:** `[[LLM: Draft X and immediately execute .bmad-core/tasks/advanced-elicitation.md]]`
|
||||
|
||||
- Draft the content
|
||||
- Present it to user
|
||||
- IMMEDIATELY execute the task
|
||||
- Wait for completion before continuing
|
||||
|
||||
**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
|
||||
**When you see:** `[[LLM: After section completion, apply .bmad-core/tasks/Y.md]]`
|
||||
|
||||
- Finish the section
|
||||
- STOP and execute the task
|
||||
@@ -389,9 +390,9 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
|
||||
## Remember
|
||||
|
||||
Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
|
||||
==================== END: tasks#create-doc ====================
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: tasks#create-workflow-plan ====================
|
||||
==================== START: .bmad-core/tasks/create-workflow-plan.md ====================
|
||||
# Create Workflow Plan Task
|
||||
|
||||
## Purpose
|
||||
@@ -681,9 +682,9 @@ BMad Orchestrator: "Based on your answers, I recommend the brownfield-fullstack
|
||||
|
||||
BMad Orchestrator: "I've created a workflow plan at docs/workflow-plan.md. This shows all the steps we'll go through, what documents will be created, and where you'll need to make decisions. Would you like to review it together?"
|
||||
```
|
||||
==================== END: tasks#create-workflow-plan ====================
|
||||
==================== END: .bmad-core/tasks/create-workflow-plan.md ====================
|
||||
|
||||
==================== START: tasks#kb-mode-interaction ====================
|
||||
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
@@ -754,9 +755,9 @@ Or ask me about anything else related to BMad-Method!
|
||||
**User**: Tell me about workflows
|
||||
|
||||
**Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]
|
||||
==================== END: tasks#kb-mode-interaction ====================
|
||||
==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
|
||||
==================== START: tasks#update-workflow-plan ====================
|
||||
==================== START: .bmad-core/tasks/update-workflow-plan.md ====================
|
||||
# Update Workflow Plan Task
|
||||
|
||||
## Purpose
|
||||
@@ -1005,9 +1006,9 @@ The update is successful when:
|
||||
- Consider creating backup before major updates
|
||||
- Updates should enhance, not complicate, the workflow experience
|
||||
- If plan becomes too cluttered, suggest creating fresh plan for next phase
|
||||
==================== END: tasks#update-workflow-plan ====================
|
||||
==================== END: .bmad-core/tasks/update-workflow-plan.md ====================
|
||||
|
||||
==================== START: data#bmad-kb ====================
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
# BMad Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -1818,9 +1819,9 @@ Use the **expansion-creator** pack to build your own:
|
||||
- **Documentation**: Check `docs/` folder for project-specific context
|
||||
- **Community**: Discord and GitHub resources available for support
|
||||
- **Contributing**: See `CONTRIBUTING.md` for full guidelines
|
||||
==================== END: data#bmad-kb ====================
|
||||
==================== END: .bmad-core/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: utils#plan-management ====================
|
||||
==================== START: .bmad-core/utils/plan-management.md ====================
|
||||
# Plan Management Utility
|
||||
|
||||
## Purpose
|
||||
@@ -2040,9 +2041,9 @@ Would you like to:
|
||||
- Malformed plan: Warn but continue, treat as no plan
|
||||
- Update failures: Log but don't block task completion
|
||||
- Parse errors: Fallback to basic text search
|
||||
==================== END: utils#plan-management ====================
|
||||
==================== END: .bmad-core/utils/plan-management.md ====================
|
||||
|
||||
==================== START: utils#workflow-management ====================
|
||||
==================== START: .bmad-core/utils/workflow-management.md ====================
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
@@ -2112,9 +2113,9 @@ Handle conditional paths by asking clarifying questions when needed.
|
||||
## Agent Integration
|
||||
|
||||
Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
|
||||
==================== END: utils#workflow-management ====================
|
||||
==================== END: .bmad-core/utils/workflow-management.md ====================
|
||||
|
||||
==================== START: utils#template-format ====================
|
||||
==================== START: .bmad-core/utils/template-format.md ====================
|
||||
# Template Format Conventions
|
||||
|
||||
Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation.
|
||||
@@ -2141,4 +2142,4 @@ Templates in the BMad method use standardized markup for AI processing. These co
|
||||
- Template elements are for AI processing only
|
||||
- Focus on faithful template execution and clean output
|
||||
- All template-specific instructions are embedded within templates
|
||||
==================== END: utils#template-format ====================
|
||||
==================== END: .bmad-core/utils/template-format.md ====================
|
||||
|
||||
Reference in New Issue
Block a user