ma-agents 3.6.2 → 3.9.0

package/_bmad-output/implementation-artifacts/4-2-vs-skill-template-format.md

@@ -1,129 +0,0 @@
-# Story 4.2: Visual Studio Skill Template Format
-
-Status: ready-for-dev
-
-<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
-<!-- Dependency: Story 4-1 must be completed first (research findings determine this story's implementation) -->
-
-## Story
-
-As an **engineer**,
-I want skills to install correctly into Visual Studio with proper format translation,
-So that my VS AI assistant receives the same methodology content as other agents.
-
-## Acceptance Criteria
-
-1. **Given** a skill with no VS-specific template exists
-   **When** installed to the VS agent
-   **Then** the `SKILL.md` fallback content is used (standard template resolution chain)
-   **And** the content is valid for VS's expected format
-
-2. **Given** VS requires a format different from standard markdown
-   **When** a skill needs VS-specific content
-   **Then** a `visual-studio.md` (or format-appropriate) template can be added to the skill
-   **And** the template resolution chain picks it up automatically
-
-3. **Given** skills are installed to both VS and other agents simultaneously
-   **When** the install completes
-   **Then** each agent receives the correct format (VS-specific or fallback)
-   **And** the manifest tracks both installations independently
-
-4. **Given** the VS agent has resource mapping rules
-   **When** a skill with `references/` or `assets/` is installed
-   **Then** supporting files are mapped to the correct VS directories per the resource map
-
-## Tasks / Subtasks
-
-- [ ] Task 1: Determine VS template requirements (AC: #1, #2)
-  - [ ] 1.1: Based on Story 4-1 research, determine if VS needs a format different from standard markdown
-  - [ ] 1.2: If VS uses markdown (like most agents): no template format work needed — SKILL.md fallback works
-  - [ ] 1.3: If VS needs a different format: define the template transformation requirements
-  - [ ] 1.4: Determine the template filename: likely `visual-studio.md` matching the agent registry key
-- [ ] Task 2: Define resource mapping for VS (AC: #4)
-  - [ ] 2.1: Based on Story 4-1 research, determine where VS expects supporting files (references/, assets/)
-  - [ ] 2.2: **Only if VS uses non-standard directory names**: add `resourceMap` to the VS agent entry in `lib/agents.js`. Currently only `cline` has a resourceMap (maps `references` → `docs`, `assets` → `templates` at `agents.js:122-125`). Example:
-    ```javascript
-    resourceMap: {
-      'references': 'docs',
-      'assets': 'templates'
-    }
-    ```
-  - [ ] 2.3: If VS uses standard directory names (`references/`, `assets/`), **omit `resourceMap` entirely** — do not set to null/empty (follow pattern of the other 10 agents that have no resourceMap)
-- [ ] Task 3: Test template resolution for VS (AC: #1, #2, #3)
-  - [ ] 3.1: Install a skill WITHOUT a VS template — verify SKILL.md fallback works
-  - [ ] 3.2: If VS-specific template created: install a skill WITH a VS template — verify template is used
-  - [ ] 3.3: Install skills to VS + another agent simultaneously — verify both get correct content
-  - [ ] 3.4: Verify manifest tracks VS installations correctly
-- [ ] Task 4: Create VS-specific templates for critical skills (AC: #2) — if needed
-  - [ ] 4.1: If VS needs format-specific templates, create them for high-priority skills (e.g., `git-workflow-skill`, `code-documentation`)
-  - [ ] 4.2: If VS uses standard markdown, this task is a no-op — SKILL.md fallback is sufficient
-
-## Dev Notes
-
-### Epic Scope Note
-
-This story covers template format verification — a scope not in the original epics (which defined 4.2 as "Add Visual Studio Agent to Registry"). The registry addition is handled in Story 4-1. This story focuses on ensuring the template resolution chain works correctly for the VS agent.
-
-### Architecture Compliance
-
-- **Template resolution chain:** `templates/<agent-id>.md` -> `templates/generic.md` -> `SKILL.md`. The template filename must match the agent's `id` field in `agents.js` (e.g., if VS agent has `id: 'visual-studio'`, then template is `templates/visual-studio.md`). The `template` field on the agent config specifies which template to use as default (e.g., `template: 'generic'`). [Source: architecture.md#Extensibility-Model]
-- **Adding a new agent target must not require changes to existing skills** (NFR11). The SKILL.md fallback ensures all existing skills work with VS out of the box.
-- **Resource mapping** is optional per-agent in the registry. Only `cline` currently uses it. The installer reads resourceMap from agents.js if present and remaps directory names accordingly. [Source: architecture.md#Module-Boundaries, lib/agents.js:122-125]
-
-### Dependency on Story 4-1
-
-This story **cannot be implemented** until Story 4-1's research is complete. The research determines:
-1. Whether VS needs a different format (markdown vs JSON vs other)
-2. Where VS expects skill files (directory paths)
-3. How resources (references, assets) are mapped
-4. What the template filename should be
-
-**If VS uses `.github/copilot-instructions.md`** (same as VS Code Copilot):
-- This story is minimal — the existing `copilot` agent template format already works
-- Resource mapping may already be defined in the `copilot` agent entry
-- The main work is verifying the existing template chain works for VS
-
-**If VS has a unique configuration mechanism:**
-- Template format definition is needed
-- Resource mapping must be researched and configured
-- Some skills may need VS-specific templates
-
-### Most Likely Scenario
-
-VS Copilot likely shares the `.github/copilot-instructions.md` mechanism with VS Code. In this case:
-- All existing skills work via SKILL.md fallback (no VS templates needed)
-- Skills with `copilot.md` templates work for both VS and VS Code
-- This story becomes primarily a verification/testing story
-
-### Critical Guardrails
-
-- **Do not modify existing skills** unless VS genuinely needs a different format [Source: NFR11]
-- **Only modify `lib/agents.js`** for resource mapping updates [Source: architecture.md, NFR13]
-- **Use `path.join()` for all paths** [Source: architecture.md#Enforcement-Guidelines]
-- **No new npm dependencies** [Source: architecture.md#Anti-Patterns]
-
-### Project Structure Notes
-
-- Files to modify: `lib/agents.js` (resource map update for VS agent — may already be done in 4-1)
-- Files to create: VS-specific templates in individual skills ONLY if research shows VS needs them
-- No changes to installer logic, CLI, or BMAD modules
-
-### References
-
-- [Source: _bmad-output/planning-artifacts/epics.md#Epic-4] — Story 4.2 definition
-- [Source: _bmad-output/planning-artifacts/prd.md#IDE-Agent-Integration-Model] — Agent integration points table
-- [Source: _bmad-output/planning-artifacts/architecture.md#Extensibility-Model] — Template resolution priority chain
-- [Source: _bmad-output/planning-artifacts/architecture.md#Module-Boundaries] — agents.js resource mapping
-- [Source: _bmad-output/planning-artifacts/prd.md#NFR11] — New agents don't require changes to existing skills
-- [Source: lib/agents.js] — Agent registry with resource maps
-- [Source: _bmad-output/implementation-artifacts/4-1-vs-agent-registry-entry.md] — Prerequisite story
-
-## Dev Agent Record
-
-### Agent Model Used
-
-### Debug Log References
-
-### Completion Notes List
-
-### File List

package/_bmad-output/implementation-artifacts/5-5-explicit-parameter-passing.md

@@ -1,274 +0,0 @@
-# Story 5.5: Explicit Parameter Passing to bmad-method
-
-Status: review
-
-<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
-<!-- Epic: 5 — Bundled BMAD Installation (Phase 2) -->
-<!-- Sprint Phase: Phase A — Installation Fixes (next release) -->
-<!-- Dependencies: Stories 5.1-5.4 (all done). Story 5.6 (space-in-path) shares same code — coordinate. -->
-
-## Story
-
-As a **DevOps engineer**,
-I want ma-agents to pass all collected installation parameters to bmad-method as explicit CLI flags,
-so that BMAD is fully configured for all selected platforms (including OpenCode) without relying on the broken silent install mode.
-
-## Acceptance Criteria
-
-1. **Given** the user selects platforms during the ma-agents wizard (e.g., claude-code, cursor, opencode)
-   **When** bmad.js invokes bmad-method
-   **Then** it passes `--tools claude-code,cursor,opencode` explicitly
-   **And** bmad-method configures all selected platforms correctly
-
-2. **Given** the user provides their name and language preference during the ma-agents wizard
-   **When** bmad.js invokes bmad-method
-   **Then** it passes `--user-name`, `--communication-language`, `--document-output-language`, and `--output-folder` as explicit flags
-   **And** bmad-method uses these values without prompting
-
-3. **Given** all BMAD-relevant parameters are passed as explicit CLI flags
-   **When** the `--yes` flag is also included
-   **Then** bmad-method skips prompts only for parameters already supplied via flags
-   **And** applies its own defaults for any new parameters ma-agents hasn't mapped (FR125)
-   **And** no interactive BMAD prompt appears to the user (FR126)
-
-4. **Given** the installer runs in CI/CD mode (`--yes --force`)
-   **When** bmad.js constructs the bmad-method command
-   **Then** it uses the same `buildBmadArgs()` function with pre-determined default answers
-   **And** produces identical BMAD configuration as interactive mode (FR127)
-
-5. **Given** the extension module exists at `lib/bmad-extension/`
-   **When** bmad.js invokes bmad-method
-   **Then** it passes `--custom-content` with the quoted path to the extension module
-   **And** bmad-method validates the module.yaml and deploys the extension
-
-6. **Given** bmad-method is invoked with `--action update` for existing installations
-   **When** the update completes
-   **Then** all explicit parameters are applied to the update
-   **And** existing customizations are preserved per bmad-method's update behavior
-
-## Tasks / Subtasks
-
-- [x] Task 1: Create `buildBmadArgs()` function in `lib/bmad.js` (AC: #1, #2, #3, #5)
-  - [x] 1.1 Define `buildBmadArgs(installContext)` that returns a complete command string
-  - [x] 1.2 Map all available parameters to bmad-method CLI flags (see parameter mapping table below)
-  - [x] 1.3 Quote ALL path arguments with double quotes for space-in-path safety (AC ties to Story 5.6)
-  - [x] 1.4 Always include `--yes` flag to suppress interactive prompts
-  - [x] 1.5 Include `--custom-content` pointing to `lib/bmad-extension/` if it exists
-- [x] Task 2: Update `installBmad()` to use `buildBmadArgs()` (AC: #1, #2, #3)
-  - [x] 2.1 Replace string-concatenation command building with `buildBmadArgs()` call
-  - [x] 2.2 Pass `action: 'install'` in the install context
-  - [x] 2.3 Verify `prePopulateBmadCache(force)` still runs BEFORE execSync
-- [x] Task 3: Update `updateBmad()` to use `buildBmadArgs()` (AC: #6)
-  - [x] 3.1 Replace string-concatenation command building with `buildBmadArgs()` call
-  - [x] 3.2 Pass `action: 'update'` in the install context
-- [x] Task 4: Update `applyCustomizations()` recompile step to use `buildBmadArgs()` (AC: #3, #4)
-  - [x] 4.1 Replace the recompile command at current line ~130 with `buildBmadArgs()` call
-  - [x] 4.2 This call uses `action: 'install'` (it's a recompile, not update)
-- [x] Task 5: Update function signatures to accept install context (AC: #2, #4)
-  - [x] 5.1 Add `userName`, `commLang`, `docLang`, `outputFolder` parameters (with defaults)
-  - [x] 5.2 Verify `cli.js` call sites are backward-compatible with new optional params (no changes needed — defaults apply)
-  - [x] 5.3 Ensure CI/CD path (`--yes`) uses same `buildBmadArgs()` with default values (FR127)
-- [x] Task 6: Manual smoke test (AC: #1-#6)
-  - [x] 6.1 Run `npx ma-agents install --yes` and verify command output includes all explicit flags
-  - [x] 6.2 Verify `_bmad/` output includes all expected modules and tool configurations
-  - [x] 6.3 Test update path on existing installation
-
-## Dev Notes
-
-### Core Change: Replace ad-hoc command building with `buildBmadArgs()`
-
-The current `lib/bmad.js` builds bmad-method commands via string concatenation in 3 places (lines 26, 52, 130). Each duplicates the pattern: `getBmadCommand('install --yes --directory "..."')` + manual `+= --modules` + manual `+= --tools`. This story replaces all 3 with a single `buildBmadArgs(installContext)` function per architecture Decision P2-6.
-
-### Current State of `lib/bmad.js` (428 lines)
-
-**3 command construction sites to replace:**
-
-| Function | Line | Current pattern | Action flag |
-|---|---|---|---|
-| `installBmad()` | 26 | `getBmadCommand('install --yes --directory "..."')` + modules + tools | `install` |
-| `updateBmad()` | 52 | `getBmadCommand('install --action update --yes --directory "..."')` + modules + tools | `update` |
-| `applyCustomizations()` | 130 | `getBmadCommand('install --yes --directory "..."')` + modules + tools | `install` (recompile) |
-
-**What is NOT changing:**
-- `getBmadCommand(args)` stays — it resolves `bmad-npx-wrapper.js` via `require.resolve()` (Story 5.1)
-- `prePopulateBmadCache(force)` stays — cache pre-population logic is correct (Story 5.3)
-- `deployMethodology()` stays — runs AFTER execSync, unrelated to parameter passing
-- `restoreGitDir()` stays — internal cache helper
-- `applyCustomizations()` stages 1-7 (file copy, extension deploy, workflow deploy) stay — only the recompile execSync changes
-
-### `buildBmadArgs()` Reference Implementation (from Architecture P2-6)
-
-```javascript
-function buildBmadArgs(installContext) {
-  const bmadPath = require.resolve('bmad-method/tools/bmad-npx-wrapper.js');
-  const args = [
-    'node', `"${bmadPath}"`, 'install',
-    '--directory', `"${installContext.projectRoot}"`,
-    '--modules', installContext.modules.join(','),
-    '--tools', installContext.tools.length > 0 ? installContext.tools.join(',') : 'none',
-    '--yes',
-  ];
-  // Optional params — only include if provided (let bmad-method default otherwise)
-  if (installContext.userName) {
-    args.push('--user-name', `"${installContext.userName}"`);
-  }
-  if (installContext.commLang) {
-    args.push('--communication-language', installContext.commLang);
-  }
-  if (installContext.docLang) {
-    args.push('--document-output-language', installContext.docLang);
-  }
-  if (installContext.outputFolder) {
-    args.push('--output-folder', installContext.outputFolder);
-  }
-  // Extension module — only if directory exists
-  const extensionPath = path.join(__dirname, 'bmad-extension');
-  if (fs.existsSync(extensionPath)) {
-    args.push('--custom-content', `"${extensionPath}"`);
-  }
-  if (installContext.action === 'update') {
-    args.push('--action', 'update');
-  }
-  return args.join(' ');
-}
-```
-
-### Parameter Mapping Table (FR123)
-
-| ma-agents source | bmad-method flag | Current state | Notes |
-|---|---|---|---|
-| `projectRoot` (detected) | `--directory` | Already passed (Story 5.4 fix) | **Must quote for spaces** |
-| `tools` array from wizard | `--tools` | Already passed | Fixes OpenCode bug — previously not configured |
-| `modules` array | `--modules` | Already passed | Default: `['bmm', 'bmb']` |
-| `userName` | `--user-name` | **NOT passed** — new | Optional; let bmad-method default if absent |
-| `commLang` | `--communication-language` | **NOT passed** — new | Optional; defaults to "English" |
-| `docLang` | `--document-output-language` | **NOT passed** — new | Optional; defaults to "English" |
-| `outputFolder` | `--output-folder` | **NOT passed** — new | Optional; defaults to "_bmad-output" |
-| extension module path | `--custom-content` | **NOT passed** — new | Path to `lib/bmad-extension/`; quote for spaces |
-| install vs update | `--action` | Already passed for update | `install` (default) or `update` |
-| `--yes` | `--yes` | Already passed | Suppresses prompts for supplied params only |
-
-### bmad-method v6.0.4 CLI Flags (Verified from `node_modules`)
-
-From `node_modules/bmad-method/tools/cli/commands/install.js` lines 14-26:
-```
---directory <path>               Installation directory
---modules <modules>              Comma-separated list of module IDs
---tools <tools>                  Comma-separated list of tools/IDEs
---custom-content <paths>         Comma-separated list of custom module paths
---action <type>                  install, update, quick-update, compile-agents
---user-name <name>               Name for agents to use
---communication-language <lang>  Language for agent communication
---document-output-language <lang> Language for document output
---output-folder <path>           Output folder relative to project root
--y, --yes                        Accept all defaults and skip prompts
-```
-
-### Critical: `--custom-content` Replaces Manual Extension Deployment
-
-Currently `applyCustomizations()` manually copies `lib/bmad-extension/` to `_bmad/extensions/ma-agents-skills/` (lines 156-162). With `--custom-content`, bmad-method handles this natively. **However**, the manual copy may still be needed for the recompile step in `applyCustomizations()` if bmad-method's `--custom-content` doesn't deploy to the same target path. Verify during implementation:
-- Does `--custom-content` deploy to `_bmad/extensions/<module-name>/`?
-- If yes: the manual `fs.copy` at line 160 can be removed (bmad-method handles it)
-- If no: keep the manual copy AND pass `--custom-content` (belt-and-suspenders)
-
-### Wizard Gap: `userName`, `commLang`, `docLang` Not Collected
-
-The `bin/cli.js` wizard does NOT currently prompt for user name, communication language, document output language, or output folder. These are new parameters from FR123. For this story:
-- Add the new params to function signatures with sensible defaults
-- Pass defaults to `buildBmadArgs()` — bmad-method's `--yes` behavior will apply its own defaults for unprovided params
-- **Do NOT add wizard prompts in this story** — that's a future enhancement. The goal is to stop the silent install from skipping config, not to collect new data from users yet.
-
-### Three Bugs This Story Fixes
-
-1. **OpenCode not configured**: `--tools` explicitly lists all selected platforms including opencode (currently tools ARE passed, but this ensures consistency through `buildBmadArgs()`)
-2. **Spaces in paths**: All path arguments quoted in `buildBmadArgs()` — `--directory "d:\My Projects\agents"` (ties to Story 5.6)
-3. **Silent install skips config**: `--yes` combined with explicit flags means bmad-method applies full config from flags, defaults only for unmapped params
-
-### Project Structure Notes
-
-- **Primary file**: `lib/bmad.js` — all changes in this file (existing 428 lines)
-- **Secondary file**: `bin/cli.js` — update call sites to pass new optional params (existing patterns)
-- **No new files created**
-- **No new dependencies**
-- Extension module at `lib/bmad-extension/` stays unchanged — just referenced by `--custom-content`
-
-### References
-
-- [Source: architecture.md, Decision P2-6] — Full `buildBmadArgs()` architecture with parameter mapping table
-- [Source: epics.md, Story 5.5 lines 531-577] — Acceptance criteria and technical notes
-- [Source: epics.md, Story 5.6 lines 578-603] — Space-in-path bug fix (shares code with this story)
-- [Source: prd.md, FR123-FR127] — Explicit parameter passing requirements
-- [Source: prd.md, NFR20-NFR21] — Version pinning and deterministic installation
-- [Source: lib/bmad.js lines 25-49] — Current `installBmad()` implementation
-- [Source: lib/bmad.js lines 51-75] — Current `updateBmad()` implementation
-- [Source: lib/bmad.js lines 77-200] — Current `applyCustomizations()` with recompile at line 130
-- [Source: node_modules/bmad-method/tools/cli/commands/install.js lines 14-26] — Verified CLI flag definitions
-- [Source: bin/cli.js lines 374-432] — Call sites for installBmad/updateBmad/applyCustomizations
-- [Source: 5-4-validate-bundled-installation.md] — Previous story: critical `--directory` bug fix, validation results
-
-## Previous Story Intelligence (5.4)
-
-**Critical bug found and fixed**: All 3 `getBmadCommand()` callsites were missing `--directory "${projectRoot}"`. bmad-method v6.0.4 only skips the directory prompt when `--directory` is explicitly provided; without it, non-TTY `execSync` silently exits with code 0 and no `_bmad/` is created. This was fixed in Story 5.4.
-
-**Learnings to apply:**
-- bmad-method silently succeeds when params are missing — always verify `_bmad/` output after install
-- The `--directory` parameter MUST be quoted for paths with spaces (discovered but not fully fixed in 5.4 — this story completes the fix)
-- `force` parameter must thread through all callsites — verify `buildBmadArgs()` doesn't drop it
-- The `ac#3 status gap` (BMAD module status not surfaced by `npx ma-agents status`) is out of scope
-
-**From Story 5.3 code review:**
-- `prePopulateBmadCache()` removed `projectRoot` param — call is `prePopulateBmadCache(force)` only
-- `fs.existsSync()` replaced with `await fs.pathExists()` — use async consistently
-- Summary log only prints when `copied > 0 || replaced > 0` — correct behavior
-
-## Git Intelligence
-
-Recent commits (descending):
-```
-998fa13 docs(planning): add F9 migration, F10 multi-repo, F6 explicit params, Epic 17 sprint rework
-8e88686 chore(release): bump version to 2.21.0
-63610de feat(epic-13): auto-generate project-context.md at install time
-```
-
-Current version: **2.21.0**. bmad-method pinned at **6.0.4** in `package.json` line 29.
-
-No recent code changes to `lib/bmad.js` since Story 5.4 — the file is stable and ready for modification.
-
-## Dev Agent Record
-
-### Agent Model Used
-
-Claude Opus 4.6 (1M context)
-
-### Debug Log References
-
-- Verified bmad-method `--custom-content` deploys to `_bmad/custom/` NOT `_bmad/extensions/` — kept manual extension copy (belt-and-suspenders approach per Dev Notes)
-- cli.js call sites unchanged since new params use default destructured options `{} = {}` — backward compatible without modification
-
-### Completion Notes List
-
-- Created `buildBmadArgs(ctx)` function implementing Architecture Decision P2-6, replacing 3 ad-hoc string-concatenation command construction sites
-- `buildBmadArgs()` delegates to existing `getBmadCommand()` for wrapper path resolution (preserving Story 5.1 fix)
-- All 3 callsites (`installBmad`, `updateBmad`, `applyCustomizations` recompile) now use `buildBmadArgs()`
-- Added `{ userName, commLang, docLang, outputFolder }` options object to `installBmad()`, `updateBmad()`, and `applyCustomizations()` with empty-string defaults
-- `--custom-content` automatically included when `lib/bmad-extension/` directory exists
-- ALL string arguments double-quoted for space-in-path safety: `--directory`, `--user-name`, `--communication-language`, `--document-output-language`, `--output-folder`, `--custom-content` (ties to Story 5.6)
-- Input validation added: `buildBmadArgs()` throws clear error on missing `projectRoot` or non-array `modules`
-- Graceful handling of undefined/null `tools` array (defaults to `--tools none`)
-- 31 unit tests covering all parameter combinations, quoting, edge cases, input validation, and function signatures
-- Full regression suite: 148 tests pass, 0 failures
-- Code review findings addressed: H1 (--output-folder quoting), H2 (language flag quoting), M2 (Task 5.2 clarification), M3/M4 (unconditional --custom-content test + edge case), M5 (input validation), L1 (null tools test)
-- M1 (shell injection via execSync) noted as pre-existing pattern — deferred to future wizard story when user-facing params are collected
-
-### File List
-
-- `lib/bmad.js` — Added `buildBmadArgs()`, updated `installBmad()`, `updateBmad()`, `applyCustomizations()` signatures and command construction
-- `test/build-bmad-args.test.js` — New: 22 unit tests for `buildBmadArgs()` and updated function signatures
-- `package.json` — Added `build-bmad-args.test.js` to test script
-- `_bmad-output/implementation-artifacts/sprint-status.yaml` — Status: ready-for-dev → review
-- `_bmad-output/implementation-artifacts/5-5-explicit-parameter-passing.md` — Story file updates (tasks, status, dev record)
-
-## Change Log
-
-- 2026-03-26: Implemented Story 5.5 — replaced 3 ad-hoc command construction sites with single `buildBmadArgs()` function per Architecture Decision P2-6. Added explicit parameter passing for `--user-name`, `--communication-language`, `--document-output-language`, `--output-folder`, and `--custom-content` flags. All string arguments double-quoted for space safety. 31 tests, 0 regressions.
-- 2026-03-26: Addressed code review findings — 2 High, 5 Medium, 1 Low. Fixed inconsistent quoting (H1/H2), added input validation (M5), improved test coverage (M3/M4/L1), clarified Task 5.2 (M2). Shell injection concern (M1) noted for future wizard story.

package/_bmad-output/implementation-artifacts/5-6-fix-space-in-path-bug.md

@@ -1,186 +0,0 @@
-# Story 5.6: Fix Space-in-Path Bug
-
-Status: review
-
-<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
-<!-- Epic: 5 — Bundled BMAD Installation (Phase 2) -->
-<!-- Sprint Phase: Phase A — Installation Fixes (next release) -->
-<!-- Dependencies: Story 5.5 (buildBmadArgs) must be implemented first — this story verifies and hardens its path quoting. -->
-
-## Story
-
-As an **engineer**,
-I want ma-agents installation to work in directories containing spaces,
-so that I can install in any project location without path-related failures.
-
-## Acceptance Criteria
-
-1. **Given** the project is located at a path with spaces (e.g., `d:\My Projects\agents`)
-   **When** `npx ma-agents install` is run
-   **Then** the installation completes without errors
-   **And** all file paths are properly quoted in `execSync` calls
-
-2. **Given** any `execSync` call in `bmad.js` that constructs shell commands with paths
-   **When** the path contains spaces, parentheses, or other shell-special characters
-   **Then** the path is enclosed in double quotes in the command string
-
-3. **Given** `require.resolve()` returns a path with spaces
-   **When** the resolved path is used in an `execSync` call
-   **Then** the path is quoted: `execSync('node "${resolvedPath}" install ...')`
-
-## Tasks / Subtasks
-
-- [x] Task 1: Audit all `execSync` calls in `lib/bmad.js` (AC: #1, #2, #3)
-  - [x] 1.1 Verify `buildBmadArgs()` (from Story 5.5) quotes `--directory` path — line 47: `"${ctx.projectRoot}"`
-  - [x] 1.2 Verify `buildBmadArgs()` quotes the `bmadPath` from `require.resolve()` — line 13 in `getBmadCommand()`: `"${wrapperPath}"`
-  - [x] 1.3 Verify `buildBmadArgs()` quotes `--custom-content` extension path — line 69: `"${extensionPath}"`
-  - [x] 1.4 Verify `buildBmadArgs()` quotes `--user-name` (may contain spaces) — line 54: `"${ctx.userName}"`
-  - [x] 1.5 Verify `restoreGitDir()` line 464 quotes `localUrl` — confirmed: `"${localUrl}"`
-  - [x] 1.6 Confirm NO other `execSync` calls exist outside `bmad.js` in ma-agents source — verified: `bin/cli.js` has none, `scripts/build-bmad-cache.js` uses `execFileSync` (array-based, immune)
-- [x] Task 2: Verify `cwd` option handling (AC: #1)
-  - [x] 2.1 Confirm all `execSync` calls pass `cwd` as a Node.js option (not embedded in command string) — all 4 calls (lines 95, 120, 196, 465) use `{ cwd: ... }` option
-  - [x] 2.2 Node.js `cwd` option handles spaces natively — no quoting needed
-- [x] Task 3: Smoke test with space-in-path directory (AC: #1, #2, #3)
-  - [x] 3.1 Created test directory: `d:\tmp\My Test Project\`
-  - [x] 3.2 Ran `npm init -y && npm install d:\Code\agents` — success
-  - [x] 3.3 Ran `npx ma-agents install --yes` — completed without path-related errors
-  - [x] 3.4 Verified `_bmad/` output: `_config`, `_memory`, `bmb`, `bmm`, `core`, `custom`, `extensions`, `skills` all present
-  - [x] 3.5 Ran update path: triggered `updateBmad()` with `--action update` — path handling correct (bmad-method module source issue is upstream, not path-related)
-- [x] Task 4: Edge case verification (AC: #2)
-  - [x] 4.1 Tested path with parentheses: `d:\tmp\Project (v2)\` — `buildBmadArgs()` correctly produces `--directory "D:\tmp\Project (v2)"` from real `process.cwd()`
-  - [x] 4.2 Ampersand in path: `buildBmadArgs()` correctly quotes — double quotes protect `&` from shell interpretation on Windows
-  - [x] 4.3 No unsupported characters found. All tested special chars (spaces, parentheses, ampersand) are correctly handled by double-quoting
-
-## Dev Notes
-
-### Relationship to Story 5.5
-
-The epics file explicitly states: "This is a bug fix — can be combined with Story 5.5 implementation since both touch the same code." Story 5.5's `buildBmadArgs()` function is the PRIMARY fix — it centralizes all path quoting in one place. Story 5.6 exists to:
-
-1. **Audit completeness** — verify `buildBmadArgs()` didn't miss any path arguments
-2. **Test with real space-in-path directories** — prove the fix works end-to-end
-3. **Cover edge cases** — parentheses, ampersands, unicode in paths
-
-If Story 5.5 is implemented correctly, Story 5.6 should mostly be a verification pass with minimal (or zero) additional code changes.
-
-### Complete `execSync` Audit of `lib/bmad.js`
-
-Only 4 `execSync` calls exist in the entire ma-agents codebase (all in `lib/bmad.js`):
-
-| Line | Function | Call | Path safety |
-|---|---|---|---|
-| 42 | `installBmad()` | `execSync(command, { cwd: projectRoot, ... })` | Command built by `buildBmadArgs()` (after 5.5). `cwd` is Node option — safe. |
-| 68 | `updateBmad()` | `execSync(command, { cwd: projectRoot, ... })` | Same as line 42. |
-| 143 | `applyCustomizations()` | `execSync(command, { cwd: projectRoot, ... })` | Same as line 42. |
-| 411 | `restoreGitDir()` | `execSync(\`git remote set-url origin "${localUrl}"\`, { cwd: moduleDir, ... })` | `localUrl` already quoted. `cwd` is Node option — safe. |
-
-**Other files:** No `execSync` calls in `bin/cli.js`, `lib/installer.js`, or `lib/agents.js`. The `scripts/build-bmad-cache.js` uses `execFileSync` (array-based args, immune to space issues).
-
-### Paths That Must Be Quoted in `buildBmadArgs()`
-
-After Story 5.5, `buildBmadArgs()` constructs the command string. These paths MUST be double-quoted:
-
-| Path | Source | Example with spaces |
-|---|---|---|
-| `bmadPath` | `require.resolve('bmad-method/...')` | `C:\Users\John Smith\node_modules\bmad-method\tools\bmad-npx-wrapper.js` |
-| `--directory` value | `installContext.projectRoot` | `d:\My Projects\agents` |
-| `--custom-content` value | `path.join(__dirname, 'bmad-extension')` | `C:\Users\John Smith\node_modules\ma-agents\lib\bmad-extension` |
-| `--user-name` value | `installContext.userName` | `John Smith` |
-| `--output-folder` value | `installContext.outputFolder` | Unlikely to have spaces, but quote defensively |
-
-Non-path values that do NOT need quoting: `--modules`, `--tools`, `--communication-language`, `--document-output-language`, `--action`, `--yes`.
-
-### `restoreGitDir()` — Already Safe
-
-Line 411: `execSync(\`git remote set-url origin "${localUrl}"\`)` — the `localUrl` is already wrapped in double quotes. The `cwd: moduleDir` is a Node.js option, not interpolated into the command string. No changes needed here.
-
-### Windows-Specific Considerations
-
-- Windows paths use backslashes (`\`), which are NOT shell-special in `cmd.exe` or PowerShell
-- Double quotes in `execSync` on Windows are handled correctly by Node.js
-- `require.resolve()` returns native path separators (backslash on Windows)
-- The `cwd` option in `execSync` works with both forward and backslashes on Windows
-
-### Previous Story Intelligence (5.5)
-
-Story 5.5 creates `buildBmadArgs(installContext)` which centralizes command construction. Its reference implementation quotes all path arguments with template literals: `\`"${path}"\``. The key things to verify:
-
-- `bmadPath` is quoted: `\`"${bmadPath}"\``
-- `projectRoot` is quoted: `'--directory', \`"${installContext.projectRoot}"\``
-- `extensionPath` is quoted: `'--custom-content', \`"${extensionPath}"\``
-- `userName` is quoted: `'--user-name', \`"${installContext.userName}"\``
-
-If any of these are missing in the actual 5.5 implementation, add the quotes in this story.
-
-### Previous Story Intelligence (5.4)
-
-Story 5.4 discovered the `--directory` bug — the parameter was missing entirely. After adding it, the format was `--directory "${projectRoot}"` which correctly handles spaces. However, 5.4 only fixed the 3 `getBmadCommand()` callsites — it didn't audit the wrapper path or extension path for space safety.
-
-### Project Structure Notes
-
-- **Primary file**: `lib/bmad.js` — audit and fix if needed (changes from 5.5 should cover this)
-- **No new files created**
-- **No new dependencies**
-- This story is primarily verification/testing with code fixes only if gaps are found
-
-### References
-
-- [Source: epics.md, Story 5.6 lines 578-603] — Acceptance criteria and technical notes
-- [Source: epics.md, Story 5.5 lines 571-572] — "All path arguments must be quoted" technical note
-- [Source: architecture.md, Decision P2-6] — "all path arguments are quoted" design decision
-- [Source: lib/bmad.js lines 10-18] — `getBmadCommand()` with quoted wrapperPath
-- [Source: lib/bmad.js lines 398-418] — `restoreGitDir()` with quoted localUrl
-- [Source: 5-5-explicit-parameter-passing.md] — buildBmadArgs() reference implementation with quoting
-- [Source: 5-4-validate-bundled-installation.md] — --directory bug fix discovery
-
-## Previous Story Intelligence (5.5)
-
-Story 5.5 introduces `buildBmadArgs(installContext)` that replaces all 3 ad-hoc command construction sites. The function centralizes path quoting. Key design decisions from 5.5:
-
-- All path arguments use `\`"${value}"\`` template literal quoting
-- `getBmadCommand()` may be subsumed or called internally by `buildBmadArgs()`
-- `--custom-content` flag added for extension module deployment
-- Optional params (`userName`, etc.) only included if provided
-
-**Key learning from 5.4**: bmad-method silently succeeds when params are missing or malformed — always verify `_bmad/` output after install to catch silent failures.
-
-## Git Intelligence
-
-Recent commits (descending):
-```
-998fa13 docs(planning): add F9 migration, F10 multi-repo, F6 explicit params, Epic 17 sprint rework
-8e88686 chore(release): bump version to 2.21.0
-63610de feat(epic-13): auto-generate project-context.md at install time
-```
-
-Current version: **2.21.0**. No code changes to `lib/bmad.js` since Story 5.4.
-
-## Dev Agent Record
-
-### Agent Model Used
-
-Claude Opus 4.6 (1M context)
-
-### Debug Log References
-
-- Smoke test in `d:\tmp\My Test Project\`: full install completed, `_bmad/` has 8 expected subdirectories
-- Update path test: command correctly included `--action update` with all quoted paths; bmad-method "module source not available" error is upstream (custom module update behavior), not path-related
-- Parentheses test in `d:\tmp\Project (v2)\`: `buildBmadArgs()` correctly produces `--directory "D:\tmp\Project (v2)"` from real `process.cwd()`
-
-### Completion Notes List
-
-- Story 5.6 is a verification/audit pass — Story 5.5's `buildBmadArgs()` already correctly quotes ALL path arguments
-- Zero code changes required: the `buildBmadArgs()` function from Story 5.5 handles all space-in-path scenarios correctly
-- Audit confirmed: only 4 `execSync` calls in entire ma-agents codebase, all in `lib/bmad.js`, all with proper path quoting and `cwd` as Node.js options
-- End-to-end smoke test confirmed: full install + update path work in `d:\tmp\My Test Project\` (directory with spaces)
-- Edge cases verified: parentheses in path `Project (v2)` and ampersand `R&D` both handled by double quoting
-- No unsupported characters identified
-
-### File List
-
-- `_bmad-output/implementation-artifacts/5-6-fix-space-in-path-bug.md` — Story file updates (tasks, status, dev record)
-- `_bmad-output/implementation-artifacts/sprint-status.yaml` — Status: ready-for-dev → review
-
-## Change Log
-
-- 2026-03-26: Completed Story 5.6 — verification/audit pass confirming Story 5.5's `buildBmadArgs()` correctly handles all space-in-path scenarios. Smoke-tested in `d:\tmp\My Test Project\` (spaces) and `d:\tmp\Project (v2)\` (parentheses). Zero code changes needed — all path quoting was already correct from Story 5.5.