BMAD update

Safely update project-local BMAD modules, mitigate CIS compatibility failures, and remove authorized deprecated components. This is a Hermes profile-local maintenance skill, not an upstream BMAD command.

When to Use

Use for BMAD installation updates, the CIS missing-module-definition failure, or authorized cleanup of deprecated BMAD modules. Do not use for Android feature implementation.

Protect existing work

Inspect Git status, _bmad/_config/manifest.yaml, configured tools, custom overrides, and npm dist-tags. Preserve the release channel unless requested otherwise. Authenticate, fetch origin, and compare HEAD with origin/main before editing. Fast-forward only clean checkouts. For a dirty checkout, use an isolated worktree from fetched origin/main; never reset, stash, clean, pull into, or overwrite existing work.

On WSL, try the existing authenticated Windows Git/gh installation if Linux Git lacks credentials. Run Windows Git fetch from the authoritative checkout: Windows Git may not understand a Linux-created worktree's absolute .git pointer. Use Linux Git inside that worktree.

Keep changes project-local. Never modify another Hermes profile or app/backend source as part of this tooling update. Do not use uninstall --yes for selective removal: it removes all BMAD components.

CIS compatibility mitigation

If installation fails because CIS main lacks src/module.yaml: