BMAD-METHOD/tools/installer/core
Gani Mohamed Parakadhullah eac137afd9
feat: add scope variable for isolated planning/implementation artifacts (#2148)
When scope is set, planning_artifacts and implementation_artifacts resolve
to {output_folder}/{scope}/planning-artifacts/ and
{output_folder}/{scope}/implementation-artifacts/. The output_folder root
stays shared for project-context and brainstorming. Unscoped root folders
remain as the default bucket for quick-dev and unscoped work.

Empty or missing scope preserves current behavior (backward compatible).

Design validated by @alexeyv via Discord.
Fixes #2148
2026-03-30 11:55:27 +08:00
..
config.js refactor(installer): restructure installer with clean separation of concerns (#2129) 2026-03-27 06:50:07 -06:00
custom-module-cache.js refactor(installer): restructure installer with clean separation of concerns (#2129) 2026-03-27 06:50:07 -06:00
existing-install.js refactor(installer): restructure installer with clean separation of concerns (#2129) 2026-03-27 06:50:07 -06:00
install-paths.js refactor(installer): restructure installer with clean separation of concerns (#2129) 2026-03-27 06:50:07 -06:00
installer.js feat: add scope variable for isolated planning/implementation artifacts (#2148) 2026-03-30 11:55:27 +08:00
manifest-generator.js refactor(installer): restructure installer with clean separation of concerns (#2129) 2026-03-27 06:50:07 -06:00
manifest.js refactor(installer): restructure installer with clean separation of concerns (#2129) 2026-03-27 06:50:07 -06:00