mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
roo installer had some bugs
This commit is contained in:
@@ -12,16 +12,14 @@ agent:
|
||||
role: "Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator"
|
||||
identity: "Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations."
|
||||
communication_style: "Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability."
|
||||
principles:
|
||||
principles: |
|
||||
- "Load resources at runtime never pre-load, and always present numbered lists for choices."
|
||||
|
||||
# Agent-specific critical actions
|
||||
critical_actions:
|
||||
- "Load into memory {project-root}/_bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
|
||||
- "Remember the users name is {user_name}"
|
||||
- "ALWAYS communicate in {communication_language}"
|
||||
|
||||
# Agent menu items
|
||||
menu:
|
||||
- trigger: "list-tasks"
|
||||
action: "list all tasks from {project-root}/_bmad/_config/task-manifest.csv"
|
||||
@@ -34,5 +32,3 @@ agent:
|
||||
- trigger: "party-mode"
|
||||
exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
|
||||
description: "Group chat with all agents"
|
||||
|
||||
prompts: []
|
||||
|
||||
@@ -16,7 +16,7 @@ communication_language:
|
||||
|
||||
document_output_language:
|
||||
prompt: "Preferred document output language?"
|
||||
default: "{communication_language}"
|
||||
default: "English"
|
||||
result: "{value}"
|
||||
|
||||
output_folder:
|
||||
|
||||
@@ -35,17 +35,17 @@ planning_artifacts: # Phase 1-3 artifacts
|
||||
default: "{output_folder}/project-planning-artifacts"
|
||||
result: "{project-root}/{value}"
|
||||
|
||||
implementation_artifacts: # Phase 4 artifacts
|
||||
prompt: "Where should implementation artifacts be stored?\n - Such as: (sprint status, individual story files and reviews, retrospectives, Quick Flow output)"
|
||||
implementation_artifacts: # Phase 4 artifacts and quick-dev flow output
|
||||
prompt: "Where should implementation artifacts be stored?\n(sprint status, individual story files and reviews, retrospectives, Quick Flow output)"
|
||||
default: "{output_folder}/implementation-artifacts"
|
||||
result: "{project-root}/{value}"
|
||||
|
||||
project_knowledge: # Artifacts from research, document-project output, other long lived accurate kn
|
||||
prompt: "Where should non-ephemeral project knowledge be stored (docs, research, references)?"
|
||||
project_knowledge: # Artifacts from research, document-project output, other long lived accurate knowledge
|
||||
prompt: "Where should non-ephemeral project knowledge be searched for and stored\n(docs, research, references)?"
|
||||
default: "docs"
|
||||
result: "{project-root}/{value}"
|
||||
# tea_use_mcp_enhancements:
|
||||
# prompt: "Enable Test Architect Playwright MCP capabilities (healing, exploratory, verification)?\nYou have to setup your MCPs yourself; refer to test-architecture.md for hints."
|
||||
# prompt: "Test Architect Playwright MCP capabilities (healing, exploratory, verification) are optionally available.\nYou will have to setup your MCPs yourself; refer to test-architecture.md for hints.\nWould you like to enable MCP enhancements in Test Architect?"
|
||||
# default: false
|
||||
# result: "{value}"
|
||||
|
||||
|
||||
Reference in New Issue
Block a user