chore: sync upstream BMAD-METHOD v6.6.0 (plugin v6.6.0.0)#71
Open
tgorka wants to merge 29 commits into
Open
Conversation
Complements clean-orphaned-skills.ts (which removes whole orphan skill directories) by detecting individual files that survive inside skill directories that still exist. For example, when upstream renames or removes a sub-file while keeping the skill's top-level directory, the stale file is never cleaned up because sync only copies/overwrites. Multiple upstream sources can contribute into the same plugin skill directory (e.g., skills/research/ receives content from both core and GDS), so the expected file set is the union across all enabled sources, plus SKILL.md (generated) and plugin-only data. Run: bun run find-orphans # report all sources bun run find-orphans -- --source core # filter report bun run find-orphans:delete # delete orphans Opt-in only — not wired into sync-all, mirroring clean:orphaned's invocation pattern.
Upstream release: https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v6.3.0 Notable upstream changes pulled in: - bmad-init skill eliminated; config now loads from _bmad/bmm/config.yaml - Dev personas Barry/Quinn/Bob consolidated into Developer (Amelia) — corresponding skill dirs removed (bmad-agent-qa, bmad-agent-quick-flow- solo-dev, bmad-agent-sm) - spec-wip.md singleton replaced by spec-{slug}.md (status field) - Custom content installation removed in favor of marketplace-based install Tooling fix included: clean-orphaned-skills.ts now also checks src/core-skills/ for valid skill names. Upstream renamed src/core/skills/ → src/core-skills/ at v6.2.x but the cleanup script was still pointing at the old path, causing it to wrongly remove core skills that sync had just populated (bmad-brainstorming, bmad-distillator, etc.). Backward-compatible: older paths are still checked as fallbacks. Plugin version bumped to 6.3.0.0 via bun run bump-core.
Upstream releases covered: v1.8.0 through v1.12.2 Latest at https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/releases Notable upstream changes pulled in: - v1.9.0: Skills made self-contained with embedded resources (tea-index.csv) - v1.9.1: Playwright 1.59 compatibility, banner and doc cross-link updates - v1.10+: Continued refinements to testarch workflows (atdd, trace, nfr, ci, framework, automate, test-design, test-review, teach-me-testing) The fetch-latest bump picked v1.12.2 rather than the v1.9.1 referenced in issue PabloLION#58 because several intermediate releases have shipped since the issue was opened. Happy to pin to v1.9.1 via --tag if preferred — this brings the plugin to the actual latest TEA release. Plugin version bumped to 6.3.0.1 via bun run bump-module --source tea.
Upstream releases covered: v0.2.3, v0.2.4, v0.3.0 Latest at https://github.com/bmad-code-org/bmad-module-game-dev-studio/releases Notable upstream changes pulled in: - v0.2.2: All 22 workflows renamed with gds- prefix (applied earlier, inherited here) - v0.2.3: Workflow refs changed from markdown links to bare paths (Opencode compatibility) - v0.2.4: Hardcoded _bmad/ paths replaced with relative / skill: prefixes (future-proofing) - v0.3.0: Latest tag — brings plugin to newest GDS release Structural changes surfaced by find-orphan-files: - gds-create-gdd: steps/ → steps-c/ reorganization — 15 old step files removed - gds-quick-dev: steps/ → steps-c/ reorganization — 6 old step files removed - 3 orphan skill dirs removed by clean:orphaned (create-prd, gds-quick-dev-new-preview, gds-quick-spec) - 5 new game-dev agents regenerated The fetch-latest bump picked v0.3.0 rather than the v0.2.4 referenced in issue PabloLION#56 because v0.3.0 shipped between the issue opening and this sync. Happy to pin to v0.2.4 via --tag if preferred. Plugin version bumped to 6.3.0.2 via bun run bump-module --source gds.
Brings main up to 6.3.0.2 (core v6.3.0, TEA v1.12.2, GDS v0.3.0) so the fork's main branch can be used as a Claude Code marketplace source for testing before upstream PR PabloLION#60 merges.
Strip legacy paths and fallbacks ahead of the v6.5.0 regression-style sync: - clean-orphaned-skills.ts: drop 3-element candidate array (src/core/skills, src/core/workflows) and check only the canonical src/core-skills/ location. - path-rewriter.ts (addCoreSpecialWorkflows): remove try-newDir-then-oldDir fallback. Drop the un-prefixed-name back-compat alias map -- v6.5.0 upstream no longer emits _bmad/core/workflows/<name>/ references (verified with grep, zero hits). - sync-upstream-content.ts: replace the inline ad-hoc version-update block (which only touched .plugin-version, package.json, plugin.json) with a delegation to updateJsonVersionFiles() from bump-utils.ts. This fixes the long-standing marketplace.json drift (was stuck at 6.2.0.4 because the inline block never updated it). - upstream-sources.ts: TODO note on TEA agentRefMappings, to be reviewed after Phase 5 validation against TEA v1.15.1 (which moved the agent to SKILL.md format). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Delete the entire plugins/bmad/skills/, plugins/bmad/_shared/, and plugins/bmad/templates/ trees so the next sync rebuilds them purely from the v6.5.0-era upstream sources. This is the strongest guarantee that no v6.3-era artifact survives the upgrade. Preserved: - plugins/bmad/agents/ (22 files, 100% plugin-owned per pluginOnlyAgents) - plugins/bmad/.claude-plugin/plugin.json (plugin manifest) - plugins/bmad/README.md (marketplace landing readme) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
While running the v6.5.0 sync, two new path-pattern categories surfaced that
the rewriter didn't yet handle:
1. **User-side passthrough aliases** (zero rewrites, no warnings):
- _bmad/scripts/ — resolve_config.py / resolve_customization.py (upstream
tooling the user invokes from their project root)
- _bmad/custom/ — user-authored config.toml overrides
- _bmad/planning/ — user-authored PRD / architecture docs
These reference the user's project tree, not plugin content. Treating them
like _memory (silent passthrough) is the correct semantics.
2. **Un-prefixed core skill aliases** (cross-module refs):
- TEA v1.15.1 still emits {project-root}/_bmad/core/workflows/<un-prefixed-name>/
references (e.g., advanced-elicitation, party-mode). Restore the un-prefixed
fallback alias in addCoreSpecialWorkflows so cross-module callers continue
to resolve until upstream catches up.
After both fixes, sync now reports zero rewrite warnings.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Upstream release: https://github.com/bmad-code-org/bmad-module-game-dev-studio/releases/tag/v0.4.0 Notable upstream changes pulled in: - customize.toml authoring pattern adopted across GDS workflow skills - Various agent SKILL.md frontmatter refreshes - Knowledge / step-file content updates Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Upstream release: https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite/releases/tag/v0.2.0 Notable upstream changes pulled in: - customize.toml authoring pattern adopted for all bmad-cis-* workflow skills - Step-file refreshes across design-thinking / brainstorming / problem-solving suites Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Upstream release: https://github.com/bmad-code-org/bmad-builder/releases/tag/v1.7.0 Notable upstream changes pulled in: - bmad-agent-builder, bmad-module-builder, bmad-workflow-builder, bmad-bmb-setup workflow / step refreshes - customize.toml introduced where applicable Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Upstream release: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/releases/tag/v1.15.1 Notable upstream changes pulled in: - TEA agent moved from YAML to SKILL.md format (bmad-tea/SKILL.md) - customize.toml adopted for testarch-* workflow skills - Knowledge base, step-file, and checklist refreshes across the test-architecture workflows (atdd, automate, ci, framework, nfr, test-design, test-review, trace) Note: agentRefMappings retained in scripts/lib/upstream-sources.ts for now — TEA still emits some un-prefixed cross-module refs (advanced-elicitation, party-mode) which the path-rewriter handles via the un-prefixed core alias fallback. TODO to drop these mappings once upstream catches up. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Upstream release: https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v6.5.0 Notable v6.5.0 upstream changes pulled in: - NEW core skill `bmad-customize` (skill-level [agent]/[workflow] override layer, replacing the older central-config approach) - customize.toml authoring pattern adopted across BMM and core skills - module.yaml introduced at module roots - workflow.md / bmad-skill-manifest.yaml deletions across implementation phase (already in skipContentFiles list, transparent to plugin) - Step-file, instruction, and checklist refreshes across most workflows Plugin version anchors updated to v6.5.0.0 across: - .plugin-version - package.json - plugins/bmad/.claude-plugin/plugin.json - .claude-plugin/marketplace.json (was stuck at v6.2.0.4 — fixed by the bump-utils delegation in the earlier sync-upstream-content.ts edit) - README badge Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ugin-only Validate flagged these two GDS agents as having no upstream counterpart in v0.4.0. They are maintained directly in plugins/bmad/agents/ and are not generated from any upstream SKILL.md, so list them in pluginOnlyAgents. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Add an Added/Changed/Removed/Fixed entry covering the v6.5.0 sync, backward-compat removal, marketplace.json fix, and plugin-only agent registrations. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
chore: sync upstreams v6.5.0.0 (regression-style upgrade, no backward compat)
Update all stale numbers and references to reflect the v6.5.0.0 state: - Features section: 9 → 22 agents, 26 → 93 skills (with module breakdown: 40 core + 10 TEA + 4 BMB + 10 CIS + 29 GDS) - Add Customization Layer feature note (new in v6.5.0) - Marketplace pin example: v6.0.0-Beta.4.2 → v6.5.0.0 - Quick Start: drop the removed `init` and `status` skills, point at the current `bmad-help`, `bmad-product-brief`, `bmad-customize` entry points - Agents table: replaced 10-agent flat list with 5-module structure reflecting all 22 agents (10 core, 3 BMB, 1 TEA, 1 plugin-only, 7 GDS) - Workflow Phases: name actual skills per phase, add Phase 5 (Customization) for v6.5.0 - Comparison table: bump version, skill count, agent count, last-updated date; tighten the Key Advantages bullets - Deprecation Notice: capture the per-module SKILL.md migration progress (TEA fully migrated, GDS mostly, BMM still on workflow.yaml) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…n references User audit surfaced a 3-month gap in CHANGELOG.md (no entries between v6.0.0-Beta.4.1 in late January and v6.5.0.0 just released) plus several old-version traces in docs and source comments. CHANGELOG.md: - Reconstruct 10 missing tag entries from git log + tag metadata: v6.0.3.4, v6.0.4.2, v6.0.4.3, v6.2.0.0-4, v6.2.2.0, v6.3.0.2. Each entry summarises the actual sync / fix / refactor that landed. - Fenced as "Reconstructed entries" since they were not authored at the time. - Add compare-link footers for all 11 new entries plus v6.5.0.0. Source comments cleaned (no more pinning historical migrations to v6.2.2): - scripts/lib/upstream-sources.ts: drop "Core v6.2.2:" prefixes from contentRoot and pluginOnlyAgents comments — the layout is just current. - scripts/lib/checks/workflows.ts: same — "since v6.2.2" → just describes what the code does. - scripts/lib/checks/paths.ts: drop "(v6.2.2+ layout)" parenthetical. Examples in scripts/docs updated to current versions: - scripts/release.sh: "6.0.0-Beta.8.0" → "6.5.1.0" - scripts/bump-module.ts: comment example now leads with "6.5.0.1" and notes legacy beta tag support as a fallback case. - AGENTS.md: example "6.0.0-Beta.9.0" → "6.5.1.0". - docs/versioning.md: example "(e.g., 6.0.0-Beta.4)" → "(e.g., 6.5.0)". - docs/releasing.md: examples bumped to 6.5.1.0 / 6.5.0.0. - docs/script-pipeline.md: version-file CSV examples + release example bumped to 6.5.0.0 / 6.5.1.0. docs/bmad-ecosystem.md: - Re-audit date 2026-02-05 → 2026-04-27. - Replace stale module-version table (BMM 6.0.0-Beta.6, TEA 0.1.1-beta.3, CIS 0.1.3, GDS 0.1.4, BMB 0.1.4) with current v6.5.0 state and reframe counts as "plugin output" (post-prefix-rename, post-sync) so the totals reconcile against the README (22 agents / 93 skills). - Update Plugin Integration Status table: CIS / GDS / BMB no longer "Blocked" — they're configured. Drop stale beads issue refs. - Note TEA v1.15.1's move to SKILL.md and GDS v0.4.0's customize.toml adoption. Two intentional Beta references retained: - docs/project-decisions.md historical checklist (project history). - scripts/bump-module.ts comment documenting legacy-tag fallback. Validation: typecheck / lint / validate all green. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…shots Both files are point-in-time research artifacts from January 2026 (v6.0.0- alpha.23 era) that drove the plugin's initial design. research.md has a "Created: 2026-01-25" footer; bmad-method-analysis.md ends with a "Source: bmadcode/BMAD-METHOD v6.0.0-alpha.23" citation. Refreshing them would erase useful project history (the Research Needed / Project Goal / .agent.yaml schema sections capture why and how the plugin came to exist). Add a clear Historical-Snapshot callout at the top of each, pointing readers to the current README / bmad-ecosystem / CHANGELOG for live data, and to project-decisions / upstream-sync-design for the decisions that followed from this analysis. Numbers, versions, and "verified" stamps in the body remain frozen as a record of the starting point. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…uation
User audit surfaced ambiguities in the Agents section:
- Did not distinguish auto-generated agents (regenerated each sync) from
hand-maintained plugin-only agents (persist across syncs).
- The two "Quinn" entries (qa.md and quinn.md) looked like duplicates.
Per quinn.md identity ("Simpler, more direct approach than the advanced
Test Architect module") they are intentional flavours: qa is the broad
BMM QA Engineer persona; quinn is a focused rapid-test-generation
alternative with a narrower tool surface (adds Bash, drops the deep
test-architecture workflows). Same first name, different scope.
- The two "Paige" entries (tech-writer + gds-agent-tech-writer) were not
acknowledged at all — game-scoped vs general docs.
Changes:
- Add provenance preamble: 6 generated + 16 plugin-owned (with the exact
list of which is which).
- Add a "Source" column to the GDS table flagging which 5 are generated
and which 2 are plugin-only (gds-agent-game-qa = GLaDOS,
gds-agent-game-scrum-master = Max).
- Re-label the Core section as "9 personas + 1 orchestrator" so the count
is parseable (9 BMM personas + bmad-master = 10).
- Expand the qa/quinn rows to make the distinction obvious.
- Add an explicit Note at the bottom calling out that duplicate persona
names (Quinn × 2, Paige × 2) are intentional, with the disambiguation.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Introduces scripts/sync-from-installer.ts which delegates 100% of the
content-shaping work to the official `npx bmad-method install --tools
claude-code` CLI. The installer already produces a Claude Code-native
tree (correct flat layout, customize.toml per skill, agents-as-skills),
so the plugin becomes a thin wrapper:
1. Run `npx bmad-method@<version> install --yes --directory
.upstream-install --modules bmm,bmb,cis,gds,tea --tools claude-code`
2. Wipe plugins/bmad/{skills,_shared,agents,templates}
3. Copy .upstream-install/.claude/skills/* 1:1 to plugins/bmad/skills/
4. Bump version anchors (.plugin-version, package.json, plugin.json,
marketplace.json, .upstream-versions/*.json) via bump-utils.ts
Also:
- package.json: rewire `bun run sync` to the new script. Drop generate:*,
sync:source, sync-all, clean:orphaned, find-orphans (these become
redundant once the installer does the merging — they will be deleted in
Phase 3 of the migration plan).
- .gitignore: add .upstream-install/.
- docs/plan-npx-resync.md: track the multi-phase migration plan that this
commit kicks off.
This commit only adds the new script; the actual wipe-and-regenerate of
plugins/bmad/ happens in the next commit (Phase 2).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Wipes plugins/bmad/skills/, plugins/bmad/_shared/, plugins/bmad/agents/, and plugins/bmad/templates/, then runs the new installer-based sync to rebuild plugins/bmad/skills/ from the official `npx bmad-method@6.5.0 install --tools claude-code` output. This is the first sync since the migration to the installer-based pipeline. Net result: - 102 skill directories (was 93) — picks up the 9 missing/misplaced skills (gds-document-project, bmad-tea, 5 GDS agent skills, plus the 3 research skills that were nested under skills/research/ instead of flat). - 1392 files (was 1296). The increase is mostly customize.toml files the old sync was missing for agent skills, plus correctly-placed resources/. - 90 customize.toml files (was 79) — full upstream coverage. - No plugins/bmad/agents/ directory (Q1 = A: drop entirely). All 22 agent .md files are gone; agent personas now live as skills under plugins/bmad/skills/bmad-agent-* / bmad-tea / gds-agent-*. Invoke via `/bmad:bmad-agent-pm` instead of `Use the pm agent…`. - No plugins/bmad/_shared/ (was 1 file: agent-manifest.csv, made redundant by the installer's per-skill resources/). - No plugins/bmad/templates/ (made redundant — templates ship inside individual skill dirs now). - Zero zombie agents (Bob, Quinn-as-QA, Barry, BMad Master) — they were already gone upstream since v6.3.0; deleting agents/ removes the last trace. - Byte-identical between source (plugins/bmad/) and installed cache (~/.claude/plugins/cache/bmad-method/bmad/6.5.0.0/) — 1392 files, zero hash diffs. The next commit (Phase 3) deletes the now-redundant scripts that the old multi-source sync needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The installer-based sync introduced in 'feat(scripts): add installer-
based sync' makes the entire multi-source sync pipeline redundant. The
installer (npx bmad-method install --tools claude-code) does all the
merging, path-rewriting, and per-skill structuring that this code used
to do — and does it correctly because it's the upstream's own canonical
output.
Deleted scripts (16 files, ~3455 lines net):
scripts/sync-upstream-content.ts # replaced by sync-from-installer
scripts/sync-all.ts # was sync + generate:* chain
scripts/generate-agents.ts # installer ships agents-as-skills
scripts/generate-skills.ts # installer ships SKILL.md
scripts/generate-agent-manifest.ts # installer ships help-catalog
scripts/clean-orphaned-skills.ts # not needed (wipe-and-replace)
scripts/find-orphan-files.ts # not needed
scripts/bump-core.ts # bumping is in sync now
scripts/bump-module.ts # ditto
scripts/lib/path-rewriter.ts # installer outputs final paths
scripts/lib/workflow-iterator.ts # no per-source iteration
scripts/lib/checks/agents.ts # nothing to cross-check
scripts/lib/checks/agent-skills.ts # ditto
scripts/lib/checks/content.ts # ditto
scripts/lib/checks/naming.ts # ditto
scripts/lib/checks/paths.ts # ditto
scripts/lib/checks/sync.ts # ditto
scripts/lib/checks/workflows.ts # ditto
Shrunken (kept, simplified):
scripts/lib/upstream-sources.ts # 277 → 95 lines: keep only
# the module list + version
# helpers; drop all the
# sync-config fields
scripts/lib/checks/index.ts # only checkVersion survives
scripts/lib/checks/version.ts # no longer needs upstream
# git clones — checks the
# version files directly
scripts/validate-upstream-coverage.ts # was three-way coverage
# check; now: version
# consistency + sanity
# check that
# plugins/bmad/skills/ has
# contents
scripts/update-readme-version.ts # drop "Released" column
# (would have needed git
# clones); keep Version +
# Last-Checked
package.json:
- Drop bump-core, bump-module from scripts (no callers)
- Keep sync, sync:dry, validate, update-readme, typecheck, lint, test
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- README.md
• Replace "Deprecation Notice" + "Features" sections with a "How
it's built" preamble (thin wrapper around npx bmad-method) plus a
feature list framed around the 102-skill output.
• Replace the multi-section Agents listing with a single Agent
Personas table — agents are skills now, no separate directory.
• Update Workflow Phase examples to reference the actual flat skill
names (bmad-market-research etc.).
• Update the comparison table: 102 skills (41 BMM + 11 TEA + 4 BMB +
10 CIS + 36 GDS), 21 agent personas (shipped as skills), source-of-
truth = official npx installer, validation strategy simplified.
• Drop "Released" column from upstream version table (would require
git clones).
- AGENTS.md
• Available Scripts: drop generate:*, sync:source, sync-all,
bump-core, bump-module (deleted in Phase 3).
• Upstream Sync section: rewrite for the npx-installer flow.
• Replace 26-row "Current Agents" table (which mixed BMM zombie
personas + CIS skills) with a smaller reference table pointing
readers at the canonical SKILL.md frontmatter for the full list.
• Automation First: restate around `bun run sync` as the single
sync command.
- docs/upstream-sync-design.md, docs/script-pipeline.md
Mark both as historical (pre-v6.5.0+) since the pipeline they
describe no longer exists. Body of each doc kept as archaeological
reference.
- tests/e2e/skill-load.test.ts
• Update skill names to current v6.5.0 prefixed form (bmad-help,
bmad-brainstorming, bmad-customize, bmad-create-prd, …).
• Replace removed init/status tests with bmad-customize coverage.
• Replace "Use the quinn agent" delegation with /bmad:bmad-tea and
/bmad:bmad-agent-pm slash invocations (agents-as-skills).
• Refresh smoke pool to use real v6.5.0 skill slugs.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Detailed CHANGELOG entry covering:
- The architectural shift to npx bmad-method install as the source of
truth (vs the previous multi-source git-clone pipeline).
- The 102-skill output (was 93), with the 9 net-new entries called out
by category (research skills flattened, 6 agent-skills relocated,
gds-document-project added).
- Removal of plugins/bmad/{agents,_shared,templates}/ — agents are
skills now, _shared content moved into per-skill resources/.
- Removal of 16 scripts (~3455 lines net) and the package.json
entries that backed them.
- Migration steps for existing users.
Bump versions: 6.5.0.0 → 6.5.0.1 across .plugin-version,
package.json, plugins/bmad/.claude-plugin/plugin.json,
.claude-plugin/marketplace.json. README badge regenerated.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
chore: re-source plugin from npx bmad-method install (v6.5.0.1)
Bumps core BMAD-METHOD to v6.6.0 and TEA to v1.17.0. BMB / CIS / GDS remain at v1.7.0 / v0.2.0 / v0.4.0 (already at the latest stable GitHub tag). Skill count holds at 102; only 3 upstream skill files changed (the new "Implementation Efficiency" guidance for bmad-create-epics-and-stories). Breaking-change matrix from upstream v6.6.0: - --tools none removed: not used (sync passes --tools claude-code) - project_name moved to [core] in config.toml: end-user install only - legacy bmad-bmm-* / bmad-agent-bmm-* skills auto-removed: none in tree Sync script fixes: - bumpModuleVersions() now reads canonical _bmad/_config/manifest.yaml produced by the v6.6.0 installer. Previous regex against _bmad/<mod>/config.yaml silently no-op'd because that file no longer carries a version: field. Without this fix TEA v1.17.0 would not have been picked up. - Reordered: updateReadmeBadge() runs after bumpModuleVersions() so the README badge and version table reflect freshly-written module versions. Quality gates: typecheck, lint, validate, e2e (6/6 passing) — all green. Idempotent: re-running the sync produces no further diff.
6 tasks
…kill use (v6.6.0.1)
Bundles the installer's _bmad/ scaffolding inside the plugin and adds a
PreToolUse hook scoped to the Skill tool that idempotently copies it into
the user's project root when a `bmad-*` or `gds-*` skill is invoked. This
removes the Python "No such file or directory" trace users hit when they
hadn't separately run `npx bmad-method install` — the documented fallback
("If the script fails, resolve the workflow block yourself…") still works,
but users would see the scary error first.
Changes:
- plugins/bmad/_bmad-template/ — bundled snapshot of `_bmad/`, with
installer-leaked identity fields (user_name, project_name) sanitized
to neutral defaults
- plugins/bmad/hooks/scaffold-bmad.py — hook that copies the template
into ${CLAUDE_PROJECT_DIR}/_bmad/ on first bmad/gds Skill call. Silent
for non-BMAD tool calls, idempotent on repeat, never blocks the
original call
- plugins/bmad/.claude-plugin/plugin.json — hook registration +
version bump (6.6.0.0 → 6.6.0.1)
- scripts/sync-from-installer.ts — bundleBmadTemplate() step that
wipes + regenerates the template from .upstream-install/_bmad/ on
every sync, with identity-field sanitization
No upstream version change — same BMAD-METHOD v6.6.0 / TEA v1.17.0 /
BMB v1.7.0 / CIS v0.2.0 / GDS v0.4.0 pinning.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
bmad-create-epics-and-stories).This PR is opened from the tgorka/bmad-plugin fork (parent fork has been ahead with installer-based sync since v6.5.0.1; see tgorka#3 for the corresponding fork-side PR). Synced 2026-05-10.
Issues closed
This PR brings every module to a version at or above what each open
upstream-syncissue requested:Breaking-change matrix (from upstream v6.6.0)
--tools noneno longer accepted on fresh--yesinstalls--tools claude-code(scripts/sync-from-installer.ts:90-91).project_namemoved from[modules.bmm]→[core]inconfig.toml; auto-migrated on user installconfig.toml; this affects end-user installs only.bmad-bmm-*/bmad-agent-bmm-*auto-removed on upgradeplugins/bmad/skills/.Sync script fixes (included in this PR)
bumpModuleVersions()rewritten to read the canonical_bmad/_config/manifest.yamlproduced by the v6.6.0 installer. The previous regex against_bmad/<mod>/config.yamlsilently no-op'd because that file no longer carries aversion:field. Without this fix, TEA v1.17.0 would not have been picked up.updateReadmeBadge()runs afterbumpModuleVersions(). Otherwise the README badge and version table reflect stale module versions.Test plan
bun run typecheck— passbun run lint— passbun run validate— passbun run test— 6/6 e2e skill-load tests pass (claude CLI v2.1.126)bun run sync -- --tag v6.6.0produces a clean diffNote for upstream maintainer
Since
PabloLION/bmad-pluginmay have diverged in its sync architecture relative to the fork, please cherry-pick the parts that apply rather than blanket-merging if needed. The two key changes outside upstream-content sync are:scripts/sync-from-installer.ts:bumpModuleVersions()— manifest-yaml based.updateReadmeBadge()runs after module versions are written.🤖 Generated with Claude Code