-
-
Notifications
You must be signed in to change notification settings - Fork 13
refactor: replace bmad-init with direct config loading #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -36,10 +36,10 @@ When you are in this persona and the user calls a skill, this persona must carry | |||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||
| ## On Activation | ||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||
| 1. **Load config via bmad-init skill** — Store all returned vars for use: | ||||||||||||||||||||||||||||
| - Use `{user_name}` from config for greeting | ||||||||||||||||||||||||||||
| - Use `{communication_language}` from config for all communications | ||||||||||||||||||||||||||||
| - Store any other config variables as `{var-name}` and use appropriately | ||||||||||||||||||||||||||||
| 1. Load config from `{project-root}/_bmad/cis/config.yaml` and resolve: | ||||||||||||||||||||||||||||
| - Use `{user_name}` for greeting | ||||||||||||||||||||||||||||
| - Use `{communication_language}` for all communications | ||||||||||||||||||||||||||||
| - Use `{document_output_language}` for output documents | ||||||||||||||||||||||||||||
|
Comment on lines
+39
to
+42
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Define fallback/error handling for config load failures. This activation flow can hard-fail if Suggested doc patch 1. Load config from `{project-root}/_bmad/cis/config.yaml` and resolve:
- Use `{user_name}` for greeting
- Use `{communication_language}` for all communications
- Use `{document_output_language}` for output documents
+ - If file is missing/invalid, continue with safe defaults:
+ - `{user_name}` = `there`
+ - `{communication_language}` = `English`
+ - `{document_output_language}` = `{communication_language}`
+ - If any key is missing, apply the same defaults and continue.📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||
| 2. **Continue with steps below:** | ||||||||||||||||||||||||||||
| - **Load project context** — Search for `**/project-context.md`. If found, load as foundational reference for project standards and conventions. If not found, continue without it. | ||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This now instructs agents to use
{document_output_language}, but this repo’s CIS configuration reference/defaults only defineoutput_folder,user_name, andcommunication_language; if the key isn’t present in a user’s_bmad/cis/config.yaml, the placeholder could remain unresolved or lead to inconsistent document language. Consider confirming this config key is part of the supported contract (and documented) wherever CIS config defaults are defined.Severity: medium
Other Locations
src/skills/bmad-cis-agent-creative-problem-solver/SKILL.md:42src/skills/bmad-cis-agent-design-thinking-coach/SKILL.md:43src/skills/bmad-cis-agent-innovation-strategist/SKILL.md:42src/skills/bmad-cis-agent-presentation-master/SKILL.md:53src/skills/bmad-cis-agent-storyteller/SKILL.md:47🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.