ma-agents 2.13.2 → 2.13.4

package/bin/cli.js

@@ -52,8 +52,8 @@ function showAgents() {
   const agents = listAgents();
   console.log(chalk.bold('\n Supported Agents:\n'));
 
-  const ideAgents = agents.filter(a => !['bmm-sre', 'bmm-devops', 'bmm-cyber'].includes(a.id));
-  const bmadAgents = agents.filter(a => ['bmm-sre', 'bmm-devops', 'bmm-cyber'].includes(a.id));
+  const ideAgents = agents.filter(a => !['bmm-sre', 'bmm-devops', 'bmm-cyber', 'bmm-mil498'].includes(a.id));
+  const bmadAgents = agents.filter(a => ['bmm-sre', 'bmm-devops', 'bmm-cyber', 'bmm-mil498'].includes(a.id));
 
   console.log(chalk.bold.yellow('  AI Coding Assistants:'));
   ideAgents.forEach(agent => {
@@ -235,8 +235,8 @@ async function installWizard(preselectedSkill, preselectedAgents, customPath, fo
 
   // Step 2: Select agents
   if (selectedAgentIds.length === 0 || isUpdate) {
-    const ideAgents = agents.filter(a => !['bmm-sre', 'bmm-devops', 'bmm-cyber'].includes(a.id));
-    const bmadAgents = agents.filter(a => ['bmm-sre', 'bmm-devops', 'bmm-cyber'].includes(a.id));
+    const ideAgents = agents.filter(a => !['bmm-sre', 'bmm-devops', 'bmm-cyber', 'bmm-mil498'].includes(a.id));
+    const bmadAgents = agents.filter(a => ['bmm-sre', 'bmm-devops', 'bmm-cyber', 'bmm-mil498'].includes(a.id));
 
     // 2.1 Coding Assistants
     const { ideChosen } = await prompts({

package/lib/bmad-workflows/mil498/bmad-mil-generate-ocd.md

@@ -14,4 +14,4 @@ This workflow generates a MIL-STD-498 OCD document to describe the system from a
     - **Section 4 (Nature of proposed changes)**: Overview of the solution.
     - **Section 5 (Operational concept)**: Describe user roles, operational scenarios, and key workflows (from UX/Stories).
 4.  **Clarity**: Ensure the document is written in a way that is easily understood by system users and stakeholders.
-5.  **Output**: Save the generated document to the `{output_folder}` as `OCD.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `OCD.md`.

package/lib/bmad-workflows/mil498/bmad-mil-generate-sdd.md

@@ -15,4 +15,4 @@ This workflow generates a MIL-STD-498 SDD document (using the SSDD template) bas
     - **Section 4 (CSCI architectural design)**: Define components, their interfaces, and data flow.
     - **Section 5 (CSCI detailed design)**: Map Stories to detailed logic and internal data structures.
 4.  **Consistency**: Ensure the design matches the requirements specified in the SRS.
-5.  **Output**: Save the generated document to the `{output_folder}` as `SDD.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SDD.md`.

package/lib/bmad-workflows/mil498/bmad-mil-generate-sdp.md

@@ -14,4 +14,4 @@ This workflow generates a MIL-STD-498 SDP document to outline the development ap
     - **Section 4 (Software development process)**: Describe the BMAD-METHOD lifecycle used.
     - **Section 5 (Software development activities)**: Detail the tasks, schedules, and milestones.
 4.  **Consistency**: Ensure the plan reflects the actual development methodology being followed.
-5.  **Output**: Save the generated document to the `{output_folder}` as `SDP.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SDP.md`.

package/lib/bmad-workflows/mil498/bmad-mil-generate-srs.md

@@ -16,4 +16,4 @@ This workflow generates a MIL-STD-498 SRS document by extracting requirements fr
     - **Section 3.3 (External Interface Requirements)**: Map Architecture interface definitions here.
     - **Section 3.10 (Computer Resource Requirements)**: Extract hardware/software constraints from the Architecture document.
 4.  **Traceability**: Ensure each requirement has a unique CID and is traced to the original PRD entry.
-5.  **Output**: Save the generated document to the `{output_folder}` as `SRS.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SRS.md`.

package/lib/bmad-workflows/mil498/bmad-mil-generate-sss.md

@@ -13,4 +13,4 @@ This workflow generates a MIL-STD-498 SSS document for high-level system require
     - **Section 3.3 (System external interface requirements)**: Map top-level interfaces.
     - **Section 3.4 (System internal interface requirements)**: Map interfaces between major subsystems.
 4.  **High-Level Focus**: Keep requirements at the system/subsystem level, avoiding low-level software details.
-5.  **Output**: Save the generated document to the `{output_folder}` as `SSS.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SSS.md`.

package/lib/bmad-workflows/mil498/bmad-mil-generate-std.md

@@ -14,4 +14,4 @@ This workflow generates a MIL-STD-498 STD document to define the test cases and
     - **Section 4 (Test descriptions)**: Map Story acceptance criteria to specific test cases and procedures.
     - **Section 5 (Requirements traceability)**: Link each test case to one or more SRS requirements.
 4.  **Verification**: Ensure all requirements in the SRS have at least one test case.
-5.  **Output**: Save the generated document to the `{output_folder}` as `STD.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `STD.md`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ma-agents",
-  "version": "2.13.2",
+  "version": "2.13.4",
   "description": "NPX tool to install skills for AI coding agents (Claude Code, Gemini, Copilot, Kilocode, Cline, Cursor)",
   "main": "index.js",
   "bin": {