History

jheyworth 2db8d7f428 docs: add comments explaining hardcoded bmm/config.yaml in prompts Clarify that bmm/config.yaml is safe to hardcode in generated prompt content because these prompts are only created when bmm module data (bmad-help.csv, agent artifacts) exists. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>		2026-02-09 09:51:36 +00:00
..
commands	refactor: Complete @clack/prompts Migration & Installer Output Consolidation (#1586 )	2026-02-08 00:40:13 -06:00
installers	docs: add comments explaining hardcoded bmm/config.yaml in prompts	2026-02-09 09:51:36 +00:00
lib	Minor installer fixes (#1590 )	2026-02-08 15:41:51 -06:00
README.md	remove modules moved to new repos and update installer to support the remote module isntallation and updates. this is a temporary imlemtation machanism	2026-01-15 22:20:56 -06:00
bmad-cli.js	refactor: Complete @clack/prompts Migration & Installer Output Consolidation (#1586 )	2026-02-08 00:40:13 -06:00
external-official-modules.yaml	refactor: replace module installer scripts with declarative directories config	2026-02-08 19:21:48 -06:00

BMad CLI Tool

Installing external repo BMad official modules

For external official modules to be discoverable during install, ensure an entry for the external repo is added to external-official-modules.yaml.

For community modules - this will be handled in a different way. This file is only for registration of modules under the bmad-code-org.