feat: Add Badge for Projects built with BMAD

[terryso]

I created a BMAD badge that can be easily added to any project README.

Usage

Add the following to your README:

[![BMAD](https://bmad-badge.vercel.app/{owner}/{repo}.svg)](https://github.com/bmad-code-org/BMAD-METHOD)

Example

[![BMAD](https://bmad-badge.vercel.app/terryso/polyv-live-cli.svg)](https://github.com/bmad-code-org/BMAD-METHOD)

Prerequisite

The repository must include a _bmad directory.

---

Repository: https://github.com/terryso/bmad-badge

[37795272]

That's cool...

[bmadcode]

this is great @terryso - can you add this to the main project?

[terryso]

Thanks @bmadcode! After reviewing the current installer architecture, here's a concrete integration proposal for discussion:

1. Badge Service (Server-side)

The simplest approach: the BMAD org forks terryso/bmad-badge and deploys it to Vercel under the org's own domain (e.g., badge.bmadcode.com).

• No code changes needed in BMAD-METHOD itself for this part
• The fork can be maintained independently by the BMAD team
• Once deployed, the badge URL changes from bmad-badge.vercel.app to the official domain
• I'm happy to transfer the repo or make any adjustments needed

2. README Badge Injection — Two Options

Option A: Installer Integration

Embed badge injection into the bmad install / bmad update flow:

• Add a BadgeInserter module to tools/installer/core/
• Auto-detect git remote to resolve owner/repo
• Inject badge markdown into the project's README
• Add --no-badge CLI flag to opt out
• Handle badge removal in bmad uninstall

Pros: Zero-friction, most users get the badge automatically
Cons: More code changes in the installer (new module, UI prompt, CLI flag, uninstall handling)

Option B: Skill-based Approach (Minimal Change)

Provide a BMAD skill that adds the badge line to the README on demand:

• Since the badge service is already live, users just need one line of markdown in their README
• A skill can auto-detect the git remote and generate the correct badge snippet
• The user invokes the skill when they want the badge — no installer changes needed
• Can also be used as a reference/template for other badge-related tasks

Pros: Minimal code change to the main project, follows existing skill patterns, user has full control
Cons: Not automatic — users need to invoke the skill explicitly

My Recommendation

I'd suggest Option B (Skill-based) as a starting point. It keeps the integration lightweight and respects the existing architecture. If the community wants auto-injection later, Option A can be layered on top without conflict.

---

What are your thoughts? Happy to implement whichever direction you prefer.