Skip to content

Replace bmad-init dependency with direct config loading #32

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.

Sign up for GitHub

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

Merged
bmadcode merged 1 commit into from
Mar 19, 2026
Merged

Replace bmad-init dependency with direct config loading #32

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion src/skills/bmad-agent-builder/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,12 @@ These agents become part of the BMad Method ecosystem — personal companions th

## On Activation

1. Load bmb config variables via `bmad-init` skill — store as `{var-name}` for all vars returned. If the skill does not exist, do your best to infer the users name and language. Greet user as `{user_name}`, use `{communication_language}` for all communications.
1. Load config from `{project-root}/_bmad/bmb/config.yaml` and resolve:
Copy link
Copy Markdown

@augmentcode augmentcode Bot Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since bmad-init is no longer invoked, what should the skill do if {project-root}/_bmad/bmb/config.yaml is missing/unreadable or missing expected keys (e.g., first run)? Without an explicit fallback or user prompt, {user_name} / output paths could remain unresolved and break downstream steps.

Severity: medium

Other Locations
  • src/skills/bmad-workflow-builder/SKILL.md:29

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

- Use `{user_name}` for greeting
- Use `{communication_language}` for all communications
- Use `{bmad_builder_output_folder}` for all skill output
- Use `{bmad_builder_reports}` for skill report output


2. Detect user's intent from their request:

Expand Down
6 changes: 5 additions & 1 deletion src/skills/bmad-workflow-builder/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,11 @@ These workflows become part of the BMad Method ecosystem. If the user with your

## On Activation

1. Invoke the `bmad-init` skill to get the config variables for the skill — store as `{var-name}` for all vars returned. If the skill does not exist, do your best to infer the users name and language. Greet user as `{user_name}` with a dream builder's enthusiasm — this will be fun! Always use `{communication_language}` for all communications.
1. Load config from `{project-root}/_bmad/bmb/config.yaml` and resolve:
Copy link
Copy Markdown

@augmentcode augmentcode Bot Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This skill’s prompts reference {document_output_language} (e.g., quality-optimizer.md), but activation no longer mentions loading/resolving it from config. Consider ensuring it’s loaded alongside {communication_language} so report/document generation doesn’t end up with an unresolved placeholder.

Severity: medium

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

- Use `{user_name}` for greeting
- Use `{communication_language}` for all communications
- Use `{bmad_builder_output_folder}` for all skill output
- Use `{bmad_builder_reports}` for skill report output

2. Detect user's intent from their request:

Expand Down
Loading