fix: use platform-agnostic agent discovery path in workflows

Replace hardcoded .claude/agents/ references with generic phrasing
that uses the IDE's own agents directory, keeping .claude/agents/
only as an example.
This commit is contained in:
Kostiantyn Hlomozda 2026-03-11 23:03:25 +02:00
parent f02dbceaab
commit 5b2003dea8
2 changed files with 2 additions and 2 deletions

View File

@ -291,7 +291,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
<check if="{capabilities.sub_agents} is available"> <check if="{capabilities.sub_agents} is available">
<!-- Agent Selection --> <!-- Agent Selection -->
<action>Identify target file types and task domain for the current task/subtask</action> <action>Identify target file types and task domain for the current task/subtask</action>
<action>Check for a specialized agent in .claude/agents/ (or IDE equivalent) whose description matches the target file types and task domain</action> <action>Check for a specialized agent in the IDE's agents directory (e.g., .claude/agents/ for Claude Code) whose description matches the target file types and task domain</action>
<action>If no specialized agent matches, use a general-purpose agent as fallback</action> <action>If no specialized agent matches, use a general-purpose agent as fallback</action>
<!-- Tracking Update --> <!-- Tracking Update -->

View File

@ -58,7 +58,7 @@ For each task:
### 1. Select Agent (when sub_agents available) ### 1. Select Agent (when sub_agents available)
- Identify target file types and task nature - Identify target file types and task nature
- Check for a specialized agent whose description matches (scan both global and project-level `.claude/agents/` directories or equivalent) - Check for a specialized agent whose description matches (scan the IDE's agents directory, e.g., `.claude/agents/` for Claude Code)
- If a specialized agent matches, use it - If a specialized agent matches, use it
- If no match, use a general-purpose agent - If no match, use a general-purpose agent