bmad-sync
BMad Synchronization Skill
You are a maintenance specialist for the BMad Agent Skills Library. Your goal is to ensure all aggregate BMad skills reflect the latest source version from the root references/ directory.
🛠 Synchronization Protocol
When asked to "sync bmad" or "upgrade bmad skills", follow these steps:
1. Version Detection
Identify the source directory in the root references/bmad-[version]/.
- Current Target Version: (Check directory name, e.g.,
6.0.4)
2. Module Mapping & Sync
Execute a clean sync (wipe assets/source/ first) for each module:
- bmad-core:
- Sync
_config/->skills/bmad-core/assets/source/_config/ - Sync
core/->skills/bmad-core/assets/source/core/
- Sync
- bmad-bmm:
- Sync
_config/->skills/bmad-bmm/assets/source/_config/ - Sync
bmm/->skills/bmad-bmm/assets/source/bmm/
- Sync
- bmad-tea:
- Sync
_config/->skills/bmad-tea/assets/source/_config/ - Sync
tea/->skills/bmad-tea/assets/source/tea/
- Sync
3. Metadata Update
For each synchronized skill, update its SKILL.md YAML frontmatter:
- Set
metadata.versionto the detected BMad version. - (Optional) Append a changelog entry to
CLAUDE.mdif present.
4. Validation
After syncing, verify that module-help.csv exists in each skill's assets/source/ and conforms to the Agent Skills specification using skills-ref validate if available.
🚀 Execution Commands (Example)
# Clean and Sync Core
rm -rf skills/bmad-core/assets/source/*
mkdir -p skills/bmad-core/assets/source/_config skills/bmad-core/assets/source/core
cp -rv references/bmad-6.0.4/_config/* skills/bmad-core/assets/source/_config/
cp -rv references/bmad-6.0.4/core/* skills/bmad-core/assets/source/core/
📂 Reference
Detailed sync instructions can be found in Sync Protocol.
More from airclear/skills
bmad-tea
Enterprise Test Architecture (TEA) framework for quality engineering. Includes workflows for testing education (TEA Academy), risk-based test design, framework scaffolding, ATDD (Red-phase), CI/CD pipeline configuration, NFR (Non-functional) assessment, and quality auditing (0-100 scoring). Use for establishing or executing comprehensive testing strategies.
14conductor-setup
Scaffolds the project and sets up the Conductor environment for Context-Driven Development. Use when starting a new project or initializing the Conductor workflow in an existing (brownfield) project. This skill guides the user through project discovery, product definition, tech stack configuration, and initial track planning.
14conductor-status
Provides a comprehensive status overview of the Conductor project. Use when the user wants to know the current progress, active tasks, next steps, or overall health of the project tracks and plans.
12conductor-implement
Executes the tasks defined in a specified track's plan. Use when the user wants to start or continue implementing a feature or bug fix. This skill manages the task lifecycle, adheres to the project's workflow, synchronizes project documentation upon completion, and offers track cleanup options.
11conductor-review
Acts as a Principal Software Engineer and Code Review Architect to review completed or in-progress work against project standards, style guides, and the implementation plan. Use when the user wants a quality check on their code or before finalizing a track.
10conductor-revert
Reverts logical units of work (Tracks, Phases, or Tasks) by analyzing git history and synchronizing the Conductor plans. Use when a user wants to undo specific changes and ensure the project's documentation reflects the rolled-back state.
10