fix: replace bmad-init dependency with direct config.yaml loading in party-mode
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
a4a7400bb5
commit
294de6ed3a
|
|
@ -22,7 +22,9 @@ Party mode accepts optional arguments when invoked:
|
||||||
|
|
||||||
1. **Parse arguments** — check for `--model` and `--solo` flags from the user's invocation.
|
1. **Parse arguments** — check for `--model` and `--solo` flags from the user's invocation.
|
||||||
|
|
||||||
2. **Load config via bmad-init skill** — store `{user_name}`, `{communication_language}`, and other config vars.
|
2. Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
||||||
|
- Use `{user_name}` for greeting
|
||||||
|
- Use `{communication_language}` for all communications
|
||||||
|
|
||||||
3. **Read the agent manifest** at `{project-root}/_bmad/_config/agent-manifest.csv`. Build an internal roster of available agents with their displayName, title, icon, role, identity, communicationStyle, and principles.
|
3. **Read the agent manifest** at `{project-root}/_bmad/_config/agent-manifest.csv`. Build an internal roster of available agents with their displayName, title, icon, role, identity, communicationStyle, and principles.
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue