Skip to content

Support bmad-automator runtime copy in BMAD installer - #3

Open
dickymoore wants to merge 4 commits into
bma-d:bma-d/add-automatorfrom
dickymoore:dicky/automator-runtime-source-root-stacked
Open

Support bmad-automator runtime copy in BMAD installer#3
dickymoore wants to merge 4 commits into
bma-d:bma-d/add-automatorfrom
dickymoore:dicky/automator-runtime-source-root-stacked

Conversation

@dickymoore

@dickymoore dickymoore commented May 1, 2026

Copy link
Copy Markdown

Summary

Follow-up on bma-d/add-automator for a gap in the Automator source-root packaging.

BMAD-METHOD installs the Automator module from payload/.claude/skills, but the story automator skill expects its Python helper runtime inside the installed bmad-story-automator skill directory. This PR copies only the required Automator runtime directories from the cloned Automator repo into that installed skill:

  • source/scripts -> bmad-story-automator/scripts
  • source/src -> bmad-story-automator/src

Scope

Intentionally limited to bma source-root installs. This does not change:

  • Codex install-target support
  • Automator workflow wording
  • registry metadata
  • external module resolution
  • generic source-root semantics

What this changes

  • After installing the bma module payload, checks whether bmad-story-automator/SKILL.md exists in the target.

  • If present, copies:

    • source/scripts into bmad-story-automator/scripts
    • source/src into bmad-story-automator/src
  • Adds a regression test covering the source-root layout.

What this does not do

  • Does not register bma in the marketplace.
  • Does not update bmad-plugins-marketplace/registry/official.yaml.
  • Does not attempt to define a general multi-agent packaging model.
  • Does not change install behaviour for other modules.

Open question

Is this the desired place to handle the Automator runtime copy?

If bma is intended to be installable through the normal BMAD installer using the current bmad-automator package layout, this PR looks necessary.

If the marketplace package should instead be made install-shaped, with the runtime already included inside the module payload, then this special-case installer hook may be redundant.

Tests

  • node test/test-installation-components.js
    • 373 passed, 0 failed
  • Commit hook also ran the full BMAD test pipeline successfully:
    • npm run test:refs
    • npm run test:install
    • npm run test:urls
    • npm run test:channels
    • npm run lint
    • npm run lint:md
    • npm run format:check

@dickymoore dickymoore changed the title Package Automator runtime for source-root installs Support bmad-automator runtime copy in BMAD installer May 1, 2026
@dickymoore
dickymoore marked this pull request as ready for review May 2, 2026 06:39
@bma-d
bma-d force-pushed the bma-d/add-automator branch 2 times, most recently from 373badb to a3e0545 Compare May 8, 2026 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants