History

Davor Racić 0b219d09e8 fix(opencode): use mode: all in agent template, remove name frontmatter, fix directory names - Replace name: '{{name}}' with mode: all in opencode-agent.md mode: all enables both Tab-key agent switching in the TUI and @subagent invocation via the Task tool (mode: primary blocked subagent use) - Remove name: '{{name}}' from opencode-task/tool/workflow/workflow-yaml templates OpenCode derives command name from filename, not from a name frontmatter field; the bare {{name}} value was overriding the bmad- prefixed filename causing name collisions with built-in OpenCode commands (fixes #1762) - Fix deprecated singular directory names in platform-codes.yaml: .opencode/agent -> .opencode/agents, .opencode/command -> .opencode/commands - Add legacy_targets migration: cleanup() now removes stale bmad-* files from old singular directories on reinstall so existing users don't get duplicates - Fix removeEmptyParents to continue walking up to parent when starting dir is already absent instead of breaking early Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>		2026-02-25 10:24:36 +01:00
..
commands	feat(cli): add uninstall command with selective component removal (#1650 )	2026-02-15 08:13:03 -06:00
installers	fix(opencode): use mode: all in agent template, remove name frontmatter, fix directory names	2026-02-25 10:24:36 +01:00
lib	fix(config): remove Windsurf from recommended/preferred IDEs (#1727 )	2026-02-20 20:16:43 -06:00
README.md	modify post install notes example	2026-02-14 21:25:58 -06:00
bmad-cli.js	fix(cli): use semantic versioning for update check (#1671 )	2026-02-16 09:39:03 -06:00
external-official-modules.yaml	refactor: replace module installer scripts with declarative directories config	2026-02-08 19:21:48 -06:00

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.