bed9052d49
* feat(agents): convert all BMM agents to conformant skill structure Replace legacy XML-based .agent.yaml files with new SKILL.md + bmad-manifest.json format for all 9 BMM agents (analyst, architect, dev, pm, qa, sm, quick-flow-solo-dev, ux-designer, tech-writer). Each agent now has: - SKILL.md with persona, activation flow (bmad-init, project context, dynamic menu) - bmad-manifest.json with capabilities referencing external skills - bmad-skill-manifest.yaml for party-mode agent-manifest.csv generation Tech-writer includes internal prompt files for write-document, mermaid-gen, validate-doc, and explain-concept capabilities. Also includes core bmad-init skill and removes legacy agent compilation tests that referenced the old .agent.yaml format. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat(installer): support new SKILL.md agent format in manifest generation Update getAgentsFromDir to detect directories with bmad-skill-manifest.yaml where type=agent and extract metadata directly from the YAML fields. This allows the agent-manifest.csv to be populated from both old-format compiled .md agents (XML parsing) and new-format SKILL.md agents (YAML manifest). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(installer): install type:agent skills to IDE native skills directory The collectSkills scanner only recognized type:skill manifests, causing new-format agents (type:agent in bmad-skill-manifest.yaml) to be added to agent-manifest.csv but not installed to .claude/skills/. Now both type:skill and type:agent are recognized as installable skills, while collectAgents still processes type:agent dirs for the agent manifest even when claimed by the skill scanner. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(installer): suppress canonicalId warning for type:agent skills Agent-type skill manifests legitimately use canonicalId for agent-manifest mapping (e.g., bmad-analyst). Only warn for regular type:skill manifests. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat(skills): update analyst manifest and simplify bmad-init instructions Switch analyst's create-brief menu entry to the new product-brief-preview skill. Simplify bmad-init SKILL.md by removing hardcoded code fences and making the script path relative to the skill directory. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(bmm): update tech-writer CSV refs to new skill path The module-help.csv still referenced the old agent YAML path for tech-writer entries. Update to skill:bmad-agent-tech-writer to match the conformant skill structure. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| commands | ||
| installers | ||
| lib | ||
| README.md | ||
| bmad-cli.js | ||
| external-official-modules.yaml | ||
README.md
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.
Post-Install Notes
Modules can display setup guidance to users after configuration is collected during npx bmad-method install. Notes are defined in the module's own module.yaml — no changes to the installer are needed.
Simple Format
Always displayed after the module is configured:
post-install-notes: |
Thank you for choosing the XYZ Cool Module
For Support about this Module call 555-1212
Conditional Format
Display different messages based on a config question's answer:
post-install-notes:
config_key_name:
value1: |
Instructions for value1...
value2: |
Instructions for value2...
Values without an entry (e.g., none) display nothing. Multiple config keys can each have their own conditional notes.
Example: TEA Module
The TEA module uses the conditional format keyed on tea_browser_automation:
post-install-notes:
tea_browser_automation:
cli: |
Playwright CLI Setup:
npm install -g @playwright/cli@latest
playwright-cli install --skills
mcp: |
Playwright MCP Setup (two servers):
1. playwright — npx @playwright/mcp@latest
2. playwright-test — npx playwright run-test-mcp-server
auto: |
Playwright CLI Setup:
...
Playwright MCP Setup (two servers):
...
When a user selects auto, they see both CLI and MCP instructions. When they select none, nothing is shown.