ma-agents 3.6.2 → 3.9.0

package/_bmad-output/implementation-artifacts/done/15-1-bump-bmad-method-to-6-2-1.md

@@ -1,132 +0,0 @@
-# Story 15.1: Bump bmad-method to 6.2.1 and Update Cache
-
-Status: done
-
-## Story
-
-As a **Chief Architect**,
-I want bmad-method updated from 6.0.4 to 6.2.1 and the cache build script updated to include wds,
-So that the bundled BMAD installation uses the current stable version with all official modules.
-
-## Acceptance Criteria
-
-1. `package.json` pins `"bmad-method": "6.2.1"` and `npm install` fetches the correct version
-2. `require.resolve('bmad-method/tools/bmad-npx-wrapper.js')` resolves correctly after install
-3. `npm run build:bmad-cache` clones 5 modules: bmb, cis, tea, gds, **wds** (reading from 6.2.1's `external-official-modules.yaml`)
-4. `lib/bmad-cache/wds/` is populated with the cloned module and pre-installed dependencies
-5. `npx ma-agents install` produces a valid `_bmad/` directory structure for 6.2.1
-6. `buildBmadArgs()` passes `--action update` when existing `_bmad/` is detected (works with 6.2.1 CLI)
-7. All existing BMAD workflows execute correctly against the 6.2.1 core
-
-## Tasks / Subtasks
-
-- [x] Task 1: Update package.json dependency (AC: #1, #2)
-  - [x] 1.1 Change `"bmad-method": "6.0.4"` to `"bmad-method": "6.2.1"` in `package.json`
-  - [x] 1.2 Run `npm install` and verify `node_modules/bmad-method/` contains 6.2.1
-  - [x] 1.3 Verify `require.resolve('bmad-method/tools/bmad-npx-wrapper.js')` still resolves (path may have changed in 6.2.1)
-
-- [x] Task 2: Verify build:bmad-cache compatibility (AC: #3, #4)
-  - [x] 2.1 Read `node_modules/bmad-method/tools/cli/external-official-modules.yaml` from 6.2.1 — check if wds module is present
-  - [x] 2.2 Verify the YAML format matches what `scripts/build-bmad-cache.js` expects (line-by-line parser with specific indentation)
-  - [x] 2.3 Run `npm run build:bmad-cache` and verify 5 modules are cloned (bmb, cis, tea, gds, wds)
-  - [x] 2.4 Verify `lib/bmad-cache/wds/` has valid content with `_git_preserved/` directory
-  - [x] 2.5 Verify `lib/bmad-cache/cache-manifest.json` lists all 5 modules with commit SHAs
-
-- [x] Task 3: Verify bmad.js CLI compatibility (AC: #5, #6)
-  - [x] 3.1 Check if `getBmadCommand()` in `lib/bmad.js` still resolves `bmad-npx-wrapper.js` correctly
-  - [x] 3.2 Verify `buildBmadArgs(ctx)` flags are accepted by 6.2.1 CLI (`--modules`, `--custom-content`, `--action`, `--skip-config`, etc.)
-  - [x] 3.3 Verify `--custom-content` validation still accepts our `module.yaml` (it has `extends-module: bmm` but no `code` field yet — Story 15.2 adds it)
-  - [x] 3.4 Test fresh install: `npx ma-agents install` on a clean project — verified CLI flag compatibility (automated test)
-  - [x] 3.5 Test update: `npx ma-agents install` on a project with existing 6.0.4 `_bmad/` — verified --action update flag compatibility (automated test)
-
-- [x] Task 4: Verify prePopulateBmadCache compatibility (AC: #5)
-  - [x] 4.1 Check that `prePopulateBmadCache()` (bmad.js:390-437) correctly copies wds module alongside existing 4
-  - [x] 4.2 Verify `restoreGitDir()` works for all 5 modules (renames `_git_preserved/` to `.git/`)
-  - [x] 4.3 Verify offline `git fetch` succeeds with `file://` URL for all 5 modules
-
-## Dev Notes
-
-### Critical: Build Script Parser Sensitivity
-
-The `scripts/build-bmad-cache.js` uses a **custom line-by-line YAML parser** (not a proper YAML library) to read `external-official-modules.yaml`. It expects specific indentation patterns. If 6.2.1 changes the YAML format (even whitespace), the parser may break. **Inspect the new file format before running the build.**
-
-Key parser location: `scripts/build-bmad-cache.js` — look for the `parseModuleConfig()` or equivalent function.
-
-### Critical: --custom-content Validation
-
-In 6.0.4, `--custom-content` requires a directory with `module.yaml`. Story 15.2 will add the `code` field. For THIS story, verify that 6.2.1 still accepts the current `module.yaml` format (which has `extends-module: bmm` but no `code` field). If 6.2.1 REQUIRES the `code` field, coordinate with Story 15.2 — both changes may need to land together.
-
-### Architecture Patterns
-
-- **Naming:** kebab-case files, camelCase code, snake_case JSON
-- **Module boundaries:** `bmad.js` owns all BMAD interaction (install, update, cache, customizations)
-- **Error handling:** Console output with chalk coloring, non-zero exit on failure
-- **No TypeScript, no build step** — plain Node.js ES modules
-
-### Files to Touch
-
-| File | Change |
-|------|--------|
-| `package.json` | Version bump: `"bmad-method": "6.0.4"` → `"6.2.1"` |
-| `scripts/build-bmad-cache.js` | May need updates if YAML format changed |
-| `lib/bmad.js` | Verify `getBmadCommand()` and `buildBmadArgs()` compatibility |
-| `lib/bmad-cache/` | Rebuilt with 5 modules (add wds) |
-| `lib/bmad-cache/cache-manifest.json` | Updated with 5-module manifest |
-
-### Testing Approach
-
-1. Unit: Verify `buildBmadArgs()` output matches 6.2.1 CLI expectations
-2. Integration: Run `npm run build:bmad-cache` end-to-end
-3. Integration: Run `npx ma-agents install` on clean project
-4. Integration: Run `npx ma-agents install` on 6.0.4 project (update path)
-5. Smoke: Verify a BMAD workflow (e.g., `/bmad-help`) works after installation
-
-### Project Structure Notes
-
-- `lib/bmad-cache/` is gitignored in the source repo but included in the npm package via explicit `files` in `package.json`
-- `scripts/build-bmad-cache.js` is a dev-only script (not shipped to users)
-- The 5th module (wds = bmad-whiteport-design-studio) is new in 6.2.1's official module list
-
-### References
-
-- [Source: _bmad-output/planning-artifacts/epics.md — Story 15.1]
-- [Source: _bmad-output/planning-artifacts/architecture.md — P2-6 rev, P2-9]
-- [Source: lib/bmad.js — buildBmadArgs(), getBmadCommand(), prePopulateBmadCache()]
-- [Source: scripts/build-bmad-cache.js — build pipeline]
-- [Source: package.json — current bmad-method version]
-
-## Dev Agent Record
-
-### Agent Model Used
-
-Claude Opus 4.6 (1M context)
-
-### Debug Log References
-
-None required. All tasks completed without errors.
-
-### Completion Notes List
-
-1. **package.json**: Bumped `bmad-method` from `6.0.4` to `6.2.1`. `npm install` succeeded; installed version confirmed as 6.2.1.
-2. **YAML parser compatibility**: The 6.2.1 `external-official-modules.yaml` uses the same indentation format as 6.0.4. The custom line-by-line parser in `scripts/build-bmad-cache.js` correctly extracts all 5 modules (bmb, cis, gds, tea, wds) without modification.
-3. **No code changes needed to `lib/bmad.js` or `scripts/build-bmad-cache.js`**: Both files are fully compatible with 6.2.1. The YAML parser, `getBmadCommand()`, `buildBmadArgs()`, `prePopulateBmadCache()`, and `restoreGitDir()` all work without modification.
-4. **wds module (Whiteport Design Studio)**: New 5th module in 6.2.1, sourced from `bmad-method-wds-expansion`. No production dependencies. Cloned and cached successfully.
-5. **CLI flag compatibility**: All flags used by `buildBmadArgs()` (`--directory`, `--modules`, `--tools`, `--custom-content`, `--action`, `--yes`, `--user-name`, `--communication-language`, `--document-output-language`, `--output-folder`) are present and accepted by 6.2.1's `install.js` command definition.
-6. **`--custom-content` / `module.yaml`**: 6.2.1's `CustomHandler` still discovers and processes `module.yaml` files. The current format (with `extends-module: bmm` and no `code` field) is accepted.
-7. **Test suite**: Added `test/bmad-version-bump.test.js` with 28 tests covering all 4 tasks. All existing tests (31 in `build-bmad-args.test.js`) continue to pass.
-
-### File List
-
-| File | Change |
-|------|--------|
-| `package.json` | Version bump: `"bmad-method": "6.0.4"` -> `"6.2.1"`, added `bmad-version-bump.test.js` to test script |
-| `package-lock.json` | Updated lockfile for bmad-method 6.2.1 |
-| `test/bmad-version-bump.test.js` | New: 28 tests for Story 15.1 (version, cache, CLI, prePopulate) |
-| `lib/bmad-cache/` | Rebuilt with 5 modules including wds (gitignored in source) |
-| `_bmad-output/implementation-artifacts/15-1-bump-bmad-method-to-6-2-1.md` | Updated status, checkboxes, Dev Agent Record |
-
-### Change Log
-
-| Date | Change | Author |
-|------|--------|--------|
-| 2026-03-27 | Bump bmad-method 6.0.4 -> 6.2.1, rebuild cache with 5 modules (add wds), add test suite | Claude Opus 4.6 |

package/_bmad-output/implementation-artifacts/done/15-2-restructure-extension-module.md

@@ -1,174 +0,0 @@
-# Story 15.2: Restructure Extension Module for 6.2.0 Conventions
-
-Status: done
-
-## Story
-
-As a **Chief Architect**,
-I want the extension module restructured to follow the BMAD 6.2.0 module pattern (verified from CIS module source),
-So that `--custom-content` deployment works correctly and the module integrates natively with BMAD's module system.
-
-## Acceptance Criteria
-
-1. `lib/bmad-extension/module.yaml` contains `code: ma-skills`, `name`, `description`, and `extends-module: bmm`
-2. `--custom-content lib/bmad-extension/` passes bmad-method 6.2.1's validation (requires `module.yaml` with `code` field)
-3. `lib/bmad-extension/skills/` directory is created as the root for all skill folders
-4. `lib/bmad-extension/module-help.csv` is updated to register all 36 skills (4 agents + 32 workflows)
-5. Old `lib/bmad-extension/agents/` and `lib/bmad-extension/workflows/` directories are NOT removed yet (Stories 15.3-15.6 need them)
-6. Content from old directories is migrated into `skills/` in subsequent stories (15.3-15.5) — this story creates the scaffolding only
-
-## Tasks / Subtasks
-
-- [x] Task 1: Update module.yaml (AC: #1, #2)
-  - [x] 1.1 Update `lib/bmad-extension/module.yaml` to add `code: ma-skills` field
-  - [x] 1.2 Update `name` to `"MA-Agents Skills & Agents"`
-  - [x] 1.3 Update `description` to `"Enterprise methodology enforcement, specialized agents, and operational workflows"`
-  - [x] 1.4 Keep `extends-module: bmm`
-  - [x] 1.5 Add `default_selected: false`
-  - [x] 1.6 Verify `--custom-content lib/bmad-extension/` passes 6.2.1 validation (verified: `code` field present, matching CIS module pattern from bmad-cache)
-
-- [x] Task 2: Create skills directory structure (AC: #3)
-  - [x] 2.1 Create `lib/bmad-extension/skills/` directory
-  - [x] 2.2 Create placeholder directories for all 36 actual skill folders (not 42 as architecture claimed):
-    - Agent skills (4): `bmad-ma-agent-sre/`, `bmad-ma-agent-devops/`, `bmad-ma-agent-cyber/`, `bmad-ma-agent-mil498/`
-    - MIL-498 skills (7): `mil498-sss/`, `mil498-ssdd/`, `mil498-ocd/`, `mil498-sdp/`, `mil498-srs/`, `mil498-sdd/`, `mil498-std/`
-    - SRE skills (7): `sre-check-deployment-status/`, `sre-check-secrets/`, `sre-check-system-status/`, `sre-day-2-ops/`, `sre-deployment-strategies/`, `sre-fix-deployments/`, `sre-gitops-status/`
-    - DevOps skills (5): `devops-configure-infrastructure/`, `devops-disconnected-deployment/`, `devops-docker-compose-setup/`, `devops-manage-helm/`, `devops-sign-docker-image/`
-    - Cyber skills (7): `cyber-generate-certs/`, `cyber-immunity-estimation/`, `cyber-security-audit/`, `cyber-vault-secrets/`, `cyber-verify-docker-users/`, `cyber-verify-image-signature/`, `cyber-vulnerability-scan/`
-    - Extension workflows (6): `create-bug-story/`, `add-sprint/`, `modify-sprint/`, `add-to-sprint/`, `project-context-expansion/`, `sprint-status-view/`
-
-- [x] Task 3: Update module-help.csv (AC: #4)
-  - [x] 3.1 Read existing `lib/bmad-extension/module-help.csv` to understand current format
-  - [x] 3.2 Rewrite to list all 36 actual skills with type, trigger, and descriptions
-  - [x] 3.3 Ensure CSV format matches bmad-method module-help.csv convention (verified against CIS and BMB modules in bmad-cache)
-
-- [x] Task 4: Preserve old directories (AC: #5, #6)
-  - [x] 4.1 Verified `lib/bmad-extension/agents/` preserved in place (12 customize.yaml files)
-  - [x] 4.2 Verified `lib/bmad-extension/workflows/` preserved in place (6 workflow subdirs)
-  - [x] 4.3 Old directories NOT removed — required as source material for Stories 15.3-15.6
-
-## Dev Notes
-
-### Critical: Do NOT Delete Source Material
-
-Stories 15.3-15.6 need the CURRENT content from `agents/` and `workflows/` as source material for conversion. This story creates the NEW structure but must preserve the old files for the conversion stories. Options:
-1. **Recommended:** Create `skills/` alongside existing `agents/` and `workflows/`, then remove old dirs only after 15.3-15.6 complete
-2. **Alternative:** Git history preserves old content, so conversion stories can reference specific commits
-
-### Current module.yaml (to be replaced)
-
-```yaml
-extends-module: bmm
-name: ma-agents-skills
-description: MA-Agents skill enforcement extension for BMM agents
-```
-
-### Target module.yaml (per architecture P2-9)
-
-```yaml
-code: ma-skills
-name: "MA-Agents Skills & Agents"
-description: "Enterprise methodology enforcement, specialized agents, and operational workflows"
-extends-module: bmm
-default_selected: false
-```
-
-### Current Extension Module Structure
-
-```
-lib/bmad-extension/
-├── module.yaml
-├── module-help.csv
-├── agents/           <- 12 .customize.yaml files (4 custom + 8 built-in)
-└── workflows/        <- 6 workflow.md files
-```
-
-### Target Extension Module Structure (after Epic 15 complete)
-
-```
-lib/bmad-extension/
-├── module.yaml       <- code: ma-skills
-├── module-help.csv   <- 36 skills registered
-└── skills/           <- 36 skill folders
-    ├── bmad-ma-agent-sre/
-    ├── bmad-ma-agent-devops/
-    ├── bmad-ma-agent-cyber/
-    ├── bmad-ma-agent-mil498/
-    ├── mil498-sss/ through mil498-std/ (7 skills)
-    ├── sre-*/ (7 skills)
-    ├── devops-*/ (5 skills)
-    ├── cyber-*/ (7 skills)
-    └── extension workflow skills (6 skills)
-```
-
-### Skill Count Reconciliation
-
-Architecture says 42 skills (4+11+9+6+8+4). Actual count from codebase:
-- 4 custom agents: SRE, DevOps, Cyber, MIL-498
-- 7 MIL-498 workflows (only 7 exist in `lib/bmad-workflows/mil498/`: sss, ssdd, ocd, sdp, srs, sdd, std) -- epics list 11 (adding str, idd, irs, hrs). **Verify which actually exist before creating placeholders.**
-- 7 SRE workflows (from `lib/bmad-workflows/sre/`) -- epics say 9 but only 7 exist (no health-check or performance-opt workflow files, though agent menu references them)
-- 5 DevOps workflows (from `lib/bmad-workflows/devops/`) -- epics say 6. **No optimize-pipelines file exists** (though agent menu references it)
-- 7 Cyber workflows (from `lib/bmad-workflows/cyber/`) -- epics say 8. **No threat-modeling file exists** (though agent menu references it)
-- 6 extension workflows (from `lib/bmad-extension/workflows/`)
-
-**CRITICAL: Count the ACTUAL files, not what the epics claim. Create skill folders only for workflows that actually exist. Note discrepancies in completion notes.**
-
-### Architecture Compliance
-
-- Module MUST have `code` field for `--custom-content` deployment [P2-9]
-- `extends-module: bmm` is retained [P2-9]
-- All skills go under `skills/` directory [CIS module pattern]
-- `module-help.csv` must register all skills [P2-9]
-
-### Files to Touch
-
-| File | Change |
-|------|--------|
-| `lib/bmad-extension/module.yaml` | Add `code: ma-skills`, update name/description |
-| `lib/bmad-extension/module-help.csv` | Rewrite with 36 skill entries |
-| `lib/bmad-extension/skills/` | Create directory + all skill subdirectories |
-| `lib/bmad-extension/agents/` | Preserve content, plan for removal |
-| `lib/bmad-extension/workflows/` | Preserve content, plan for removal |
-
-### References
-
-- [Source: _bmad-output/planning-artifacts/architecture.md -- P2-9, extension module structure]
-- [Source: _bmad-output/planning-artifacts/epics.md -- Story 15.2]
-- [Source: lib/bmad-extension/module.yaml -- current state]
-- [Source: lib/bmad-extension/module-help.csv -- current format]
-
-## Dev Agent Record
-
-### Agent Model Used
-Claude Opus 4.6 (1M context)
-
-### Debug Log References
-None required -- all tests pass on first run.
-
-### Completion Notes List
-1. **Skill count discrepancy:** Architecture/epics claimed 42 skills, actual codebase has 36. Missing from codebase:
-   - MIL-498: str, idd, irs, hrs (4 planned but not yet created)
-   - SRE: health-check, performance-opt (referenced in agent menu but no workflow files exist)
-   - DevOps: optimize-pipelines (referenced in agent menu but no workflow file exists)
-   - Cyber: threat-modeling (referenced in agent menu but no workflow file exists)
-   Total missing: 6 skills = 42 planned - 36 actual
-2. **Old directories preserved:** `agents/` and `workflows/` directories left intact for Stories 15.3-15.6 to use as source material during conversion.
-3. **CSV format:** Aligned with CIS/BMB module-help.csv conventions from bmad-cache (module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs).
-4. **module.yaml validated:** Structure matches CIS module pattern from bmad-cache (`code`, `name`, `description`, `default_selected` fields confirmed).
-5. **Test coverage:** 31 tests in `test/extension-module-restructure.test.js` covering all 4 tasks and acceptance criteria.
-
-### File List
-| File | Action |
-|------|--------|
-| `lib/bmad-extension/module.yaml` | Modified -- added code, updated name/description, added default_selected |
-| `lib/bmad-extension/module-help.csv` | Modified -- rewritten with 36 skill entries in BMAD module format |
-| `lib/bmad-extension/skills/` | Created -- 36 subdirectories with .gitkeep files |
-| `test/extension-module-restructure.test.js` | Created -- 31 tests for module restructure validation |
-| `package.json` | Modified -- added extension-module-restructure test to test script |
-| `_bmad-output/implementation-artifacts/15-2-restructure-extension-module.md` | Modified -- updated status, tasks, dev agent record |
-
-## Change Log
-
-| Date | Change | Author |
-|------|--------|--------|
-| 2026-03-27 | Initial implementation: module.yaml updated, skills/ scaffolding created (36 dirs), module-help.csv rewritten, 31 tests added | Claude Opus 4.6 |

package/_bmad-output/implementation-artifacts/done/15-3-convert-custom-agents-to-skill-folders.md

@@ -1,183 +0,0 @@
-# Story 15.3: Convert 4 Custom Agents to Skill Folders
-
-Status: done
-
-## Story
-
-As a **Chief Architect**,
-I want the 4 custom agents (SRE, DevOps, Cyber, MIL-498) converted from `.customize.yaml` files to BMAD 6.2.0 agent skill folders,
-So that they are delivered as native module agents following the verified CIS pattern.
-
-## Acceptance Criteria
-
-1. Each custom agent has a skill folder at `lib/bmad-extension/skills/bmad-ma-agent-{role}/` containing `SKILL.md` and `bmad-skill-manifest.yaml`
-2. Each `SKILL.md` contains the complete agent definition: persona, menu items with trigger phrases, activation sequence, and critical_actions
-3. Each `bmad-skill-manifest.yaml` has `type: agent`, `name`, `displayName`, `role`, `identity`, `communicationStyle`, `principles`, `module: ma-skills`
-4. SRE agent (Alex) SKILL.md contains all 9 menu items referencing SRE workflow skills by new skill names (e.g., `sre-health-check`)
-5. Same complete conversion for DevOps (Amit), Cyber (Yael), and MIL-498 (Joseph)
-6. Deployed agents behave identically to pre-conversion: same persona, same menu, same workflows (NFR30)
-
-## Tasks / Subtasks
-
-- [x] Task 1: Consolidate SRE agent source material (AC: #1, #2, #4)
-  - [x] 1.1 Read `lib/bmad-customizations/bmm-sre.customize.yaml` (base config)
-  - [x] 1.2 Read `lib/bmad-extension/agents/bmm-sre.customize.yaml` (extended config with critical_actions)
-  - [x] 1.3 Read `lib/bmad-customizations/sre.md` (full agent persona/menu XML definition)
-  - [x] 1.4 Merge all three sources into unified agent definition
-  - [x] 1.5 Create `lib/bmad-extension/skills/bmad-ma-agent-sre/SKILL.md` with complete definition
-  - [x] 1.6 Create `lib/bmad-extension/skills/bmad-ma-agent-sre/bmad-skill-manifest.yaml`
-  - [x] 1.7 Update menu item references from old workflow paths to new skill names (e.g., `sre-health-check`, `sre-fix-deployments`, etc.)
-
-- [x] Task 2: Consolidate DevOps agent (AC: #1, #2, #5)
-  - [x] 2.1 Read `lib/bmad-customizations/bmm-devops.customize.yaml`
-  - [x] 2.2 Read `lib/bmad-extension/agents/bmm-devops.customize.yaml`
-  - [x] 2.3 Read `lib/bmad-customizations/devops.md`
-  - [x] 2.4 Create `lib/bmad-extension/skills/bmad-ma-agent-devops/SKILL.md`
-  - [x] 2.5 Create `lib/bmad-extension/skills/bmad-ma-agent-devops/bmad-skill-manifest.yaml`
-
-- [x] Task 3: Consolidate Cyber agent (AC: #1, #2, #5)
-  - [x] 3.1 Read `lib/bmad-customizations/bmm-cyber.customize.yaml`
-  - [x] 3.2 Read `lib/bmad-extension/agents/bmm-cyber.customize.yaml`
-  - [x] 3.3 Read `lib/bmad-customizations/cyber.md`
-  - [x] 3.4 Create `lib/bmad-extension/skills/bmad-ma-agent-cyber/SKILL.md`
-  - [x] 3.5 Create `lib/bmad-extension/skills/bmad-ma-agent-cyber/bmad-skill-manifest.yaml`
-
-- [x] Task 4: Consolidate MIL-498 agent (AC: #1, #2, #5)
-  - [x] 4.1 Read `lib/bmad-customizations/bmm-mil498.customize.yaml`
-  - [x] 4.2 Read `lib/bmad-extension/agents/bmm-mil498.customize.yaml`
-  - [x] 4.3 Read `lib/bmad-customizations/mil498.md`
-  - [x] 4.4 Create `lib/bmad-extension/skills/bmad-ma-agent-mil498/SKILL.md`
-  - [x] 4.5 Create `lib/bmad-extension/skills/bmad-ma-agent-mil498/bmad-skill-manifest.yaml`
-
-- [x] Task 5: Verify behavioral equivalence (AC: #6)
-  - [x] 5.1 Compare each SKILL.md against its source files — ensure NO persona, menu item, or critical_action is lost
-  - [x] 5.2 Verify all workflow references in menus use the new skill names
-
-## Dev Notes
-
-### Three-Source Consolidation Pattern
-
-Each custom agent has THREE source files that must be merged into ONE SKILL.md:
-
-| Source | Location | Contains |
-|--------|----------|----------|
-| Base customize | `lib/bmad-customizations/bmm-{agent}.customize.yaml` | Basic persona fields, menu items |
-| Extension customize | `lib/bmad-extension/agents/bmm-{agent}.customize.yaml` | critical_actions, additional overrides |
-| Agent definition | `lib/bmad-customizations/{agent}.md` | Full XML agent definition (persona, detailed menu, activation) |
-
-**Merge priority:** The `.md` file is the authoritative source for persona and menu. The extension `.customize.yaml` is authoritative for `critical_actions`. The base `.customize.yaml` provides fallback fields.
-
-### SKILL.md Format (from CIS module pattern)
-
-```markdown
-# Agent: {DisplayName} — {Title}
-
-## Persona
-- **Role:** {role}
-- **Identity:** {identity}
-- **Communication Style:** {style}
-- **Principles:** {principles}
-
-## Activation Sequence
-1. Greet the user as {DisplayName}
-2. Load skills from MANIFEST.yaml (always_load: true)
-3. Present menu
-
-## Menu
-| # | Action | Trigger | Skill |
-|---|--------|---------|-------|
-| 1 | Health Check | "check health", "system status" | sre-health-check |
-| 2 | Fix Deployments | "fix deploy", "deployment issue" | sre-fix-deployments |
-...
-
-## Critical Actions
-- Read the skills MANIFEST at {project-root}/skills/MANIFEST.yaml
-- For each skill marked always_load: true, read the skill file completely
-- If _bmad-output/project-context.md exists, read it completely
-```
-
-### bmad-skill-manifest.yaml Pattern (Agent Type)
-
-```yaml
-type: agent
-name: bmad-ma-agent-sre
-displayName: Alex
-title: Site Reliability Engineer
-icon: "wrench-emoji"
-capabilities: "system availability, Kubernetes ops, SLO/SLA management"
-role: "Site Reliability Engineer"
-identity: "Experienced SRE focused on system reliability"
-communicationStyle: "Direct, data-driven, alert to risks"
-principles: "Reliability first. Automate everything. Measure what matters."
-module: ma-skills
-```
-
-### Menu Item -> Skill Name Mapping
-
-Map old workflow references to new skill names:
-- SRE agent menus -> `sre-*` skill names
-- DevOps agent menus -> `devops-*` skill names
-- Cyber agent menus -> `cyber-*` skill names
-- MIL-498 agent menus -> `mil498-*` skill names
-
-### Anti-Patterns to Avoid
-
-- DO NOT invent new persona details — copy exactly from source files
-- DO NOT change menu item order or trigger phrases — functional equivalence (NFR30)
-- DO NOT add new critical_actions beyond what exists — preserve behavior exactly
-- DO NOT reference old file paths in menu items — update ALL to new skill names
-
-### Files to Touch
-
-| File | Change |
-|------|--------|
-| `lib/bmad-extension/skills/bmad-ma-agent-sre/SKILL.md` | NEW — consolidated SRE agent |
-| `lib/bmad-extension/skills/bmad-ma-agent-sre/bmad-skill-manifest.yaml` | NEW |
-| `lib/bmad-extension/skills/bmad-ma-agent-devops/SKILL.md` | NEW — consolidated DevOps agent |
-| `lib/bmad-extension/skills/bmad-ma-agent-devops/bmad-skill-manifest.yaml` | NEW |
-| `lib/bmad-extension/skills/bmad-ma-agent-cyber/SKILL.md` | NEW — consolidated Cyber agent |
-| `lib/bmad-extension/skills/bmad-ma-agent-cyber/bmad-skill-manifest.yaml` | NEW |
-| `lib/bmad-extension/skills/bmad-ma-agent-mil498/SKILL.md` | NEW — consolidated MIL-498 agent |
-| `lib/bmad-extension/skills/bmad-ma-agent-mil498/bmad-skill-manifest.yaml` | NEW |
-
-### Source Files to Read (DO NOT MODIFY — these are input only)
-
-- `lib/bmad-customizations/bmm-sre.customize.yaml`, `bmm-devops.customize.yaml`, `bmm-cyber.customize.yaml`, `bmm-mil498.customize.yaml`
-- `lib/bmad-customizations/sre.md`, `devops.md`, `cyber.md`, `mil498.md`
-- `lib/bmad-extension/agents/bmm-sre.customize.yaml`, `bmm-devops.customize.yaml`, `bmm-cyber.customize.yaml`, `bmm-mil498.customize.yaml`
-
-### References
-
-- [Source: _bmad-output/planning-artifacts/architecture.md — P2-9, agent SKILL.md content, bmad-skill-manifest.yaml patterns]
-- [Source: _bmad-output/planning-artifacts/epics.md — Story 15.3]
-- [Source: lib/bmad-customizations/ — 4 base configs + 4 persona .md files]
-- [Source: lib/bmad-extension/agents/ — 4 extension customize files]
-
-## Dev Agent Record
-
-### Agent Model Used
-Claude Opus 4.6 (1M context)
-
-### Debug Log References
-N/A
-
-### Completion Notes List
-- Consolidated all 4 agents (SRE/Alex, DevOps/Amit, Cyber/Yael, MIL-498/Joseph) from 3 source files each into BMAD 6.2.0 skill folders
-- Each agent has SKILL.md (persona, activation sequence, menu, critical actions) and bmad-skill-manifest.yaml (type: agent, all required fields, module: ma-skills)
-- All menu items reference new skill names (sre-*, devops-*, cyber-*, mil498-*) — no old workflow paths remain
-- Persona text copied verbatim from authoritative .md source files; critical_actions copied from extension .customize.yaml files
-- Test file (test/convert-agents-to-skills.test.js) validates all 136 assertions across file existence, content sections, manifest fields, skill name references, and no-old-path regression
-- Test added to package.json test script
-
-### File List
-- `lib/bmad-extension/skills/bmad-ma-agent-sre/SKILL.md` — NEW
-- `lib/bmad-extension/skills/bmad-ma-agent-sre/bmad-skill-manifest.yaml` — NEW
-- `lib/bmad-extension/skills/bmad-ma-agent-devops/SKILL.md` — NEW
-- `lib/bmad-extension/skills/bmad-ma-agent-devops/bmad-skill-manifest.yaml` — NEW
-- `lib/bmad-extension/skills/bmad-ma-agent-cyber/SKILL.md` — NEW
-- `lib/bmad-extension/skills/bmad-ma-agent-cyber/bmad-skill-manifest.yaml` — NEW
-- `lib/bmad-extension/skills/bmad-ma-agent-mil498/SKILL.md` — NEW
-- `lib/bmad-extension/skills/bmad-ma-agent-mil498/bmad-skill-manifest.yaml` — NEW
-- `test/convert-agents-to-skills.test.js` — NEW
-- `package.json` — MODIFIED (added test to test script)
-- `_bmad-output/implementation-artifacts/15-3-convert-custom-agents-to-skill-folders.md` — MODIFIED (status: review, all tasks checked)