ma-agents 2.17.0 → 2.18.0

package/lib/bmad.js

@@ -74,6 +74,7 @@ async function applyCustomizations(projectRoot = process.cwd(), modules = ['bmm'
     };
 
     // 1. Apply YAML customizations (filtered by selected agents)
+    // These must be in place BEFORE recompile so BMAD can use them during compilation
     if (fs.existsSync(sourceDir)) {
         await fs.ensureDir(configTargetDir);
         const files = await fs.readdir(sourceDir);
@@ -89,7 +90,8 @@ async function applyCustomizations(projectRoot = process.cwd(), modules = ['bmm'
         }
     }
 
-    // 2. Apply detailed agent templates (.md files, filtered by selected agents)
+    // 2. Apply detailed agent templates to custom dir (.md files, filtered by selected agents)
+    // These go to _bmad/custom/agents/ for BMAD's custom agent resolution
     if (fs.existsSync(sourceDir)) {
         await fs.ensureDir(agentTargetDir);
         const files = await fs.readdir(sourceDir);
@@ -104,21 +106,9 @@ async function applyCustomizations(projectRoot = process.cwd(), modules = ['bmm'
         }
     }
 
-    // 3. Apply workflows
-    if (fs.existsSync(workflowSourceDir)) {
-        await fs.ensureDir(workflowTargetDir);
-        await fs.copy(workflowSourceDir, workflowTargetDir);
-        console.log(chalk.cyan(`    + Applied BMAD workflows`));
-    }
-
-    // 4. Apply MIL-STD-498 templates
-    if (fs.existsSync(templateSourceDir)) {
-        await fs.ensureDir(templateTargetDir);
-        await fs.copy(templateSourceDir, templateTargetDir);
-        console.log(chalk.cyan(`    + Applied MIL-STD-498 templates`));
-    }
-
-    // Recompile agents to apply changes
+    // Recompile agents to apply YAML customizations
+    // IMPORTANT: Steps 3-5 must run AFTER recompile because the recompile regenerates
+    // the _bmad/bmm/ tree and would wipe any files placed there beforehand.
     let command = 'npx bmad-method install --yes';
     if (modules && modules.length > 0) {
         command += ` --modules ${modules.join(',')}`;
@@ -135,7 +125,39 @@ async function applyCustomizations(projectRoot = process.cwd(), modules = ['bmm'
         console.error(chalk.red(`  BMAD recompile failed: ${error.message}`));
     }
 
-    // 5. Register custom workflows in BMAD CSV registries (after recompile)
+    // 3. Apply workflows (AFTER recompile so they persist)
+    if (fs.existsSync(workflowSourceDir)) {
+        await fs.ensureDir(workflowTargetDir);
+        await fs.copy(workflowSourceDir, workflowTargetDir);
+        console.log(chalk.cyan(`    + Applied BMAD workflows`));
+    }
+
+    // 4. Apply MIL-STD-498 templates (AFTER recompile so they persist)
+    if (fs.existsSync(templateSourceDir)) {
+        await fs.ensureDir(templateTargetDir);
+        await fs.copy(templateSourceDir, templateTargetDir);
+        console.log(chalk.cyan(`    + Applied MIL-STD-498 templates`));
+    }
+
+    // 5. Copy agent templates to compiled location (AFTER recompile)
+    // BMAD recompile doesn't generate custom agents (mil498, cyber) in _bmad/bmm/agents/.
+    // Without this, updateAgentInstructions() creates the file with only the MA-AGENTS block.
+    if (fs.existsSync(sourceDir)) {
+        const compiledAgentDir = path.join(projectRoot, BMAD_DIR, 'bmm', 'agents');
+        await fs.ensureDir(compiledAgentDir);
+        const files = await fs.readdir(sourceDir);
+        for (const file of files) {
+            if (file.endsWith('.md')) {
+                const matchingAgentId = Object.entries(agentMdMap).find(([, mdFile]) => mdFile === file)?.[0];
+                if (!matchingAgentId || selectedAgentIds.length === 0 || selectedAgentIds.includes(matchingAgentId)) {
+                    await fs.copy(path.join(sourceDir, file), path.join(compiledAgentDir, file));
+                    console.log(chalk.cyan(`    + Applied compiled agent: ${file}`));
+                }
+            }
+        }
+    }
+
+    // 6. Register custom workflows in BMAD CSV registries (after recompile)
     if (selectedAgentIds.length === 0 || selectedAgentIds.includes('bmm-mil498')) {
         await registerMilWorkflows(projectRoot);
     }

package/lib/mil498-templates/SDD.md

@@ -0,0 +1,163 @@
+# 1. Scope.
+
+This section shall be divided into the following paragraphs.
+
+## 1.1 Identification.
+
+This paragraph shall contain a full identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).
+
+## 1.2 System overview.
+
+This paragraph shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other relevant documents.
+
+## 1.3 Document overview.
+
+This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.
+
+# 2. Referenced documents.
+
+This section shall list the number, title, revision, and date of all documents referenced in this document. This section shall also identify the source for all documents not available through normal Government stocking activities.
+
+# 3. CSCI-wide design decisions.
+
+This section shall be divided into paragraphs as needed to present CSCI-wide design decisions, that is, decisions about the CSCI's behavioral design (how it will behave, from a user's point of view, in meeting its requirements, ignoring internal implementation) and other decisions affecting the selection and design of the software components (e.g., Computer Software Components (CSCs)) that make up the CSCI. If all such decisions are explicit in the CSCI requirements or are deferred to the design of the CSCI's software components, this section shall so state. Design decisions that respond to requirements designated critical, such as those for safety, security, or privacy, shall be placed in separate subparagraphs. If a design decision depends upon CSCI states or modes, this dependency shall be indicated. Design conventions needed to understand the design shall be presented or referenced. Examples of CSCI-wide design decisions are the following:
+
+a. Design decisions regarding inputs the CSCI will accept and outputs it will produce, including interfaces with other systems, HWCIs, CSCIs, and users (4.3.x of this DID identifies topics to be considered in this description). If part or all of this information is given in Interface Design Descriptions (IDDs), they may be referenced.
+
+b. Design decisions on CSCI behavior in response to each input or condition, including actions the CSCI will perform, response times and other performance characteristics, description of physical systems modeled, selected equations/algorithms/rules, and handling of unallowed inputs or conditions.
+
+c. Design decisions on how databases/data files will appear to the user (4.3.x of this DID identifies topics to be considered in this description). If part or all of this information is given in Database Design Descriptions (DBDDs), they may be referenced.
+
+d. Selected approach to meeting safety, security, and privacy requirements.
+
+e. Other CSCI-wide design decisions made in response to requirements, such as selected approach to providing required flexibility, availability, and maintainability.
+
+# 4. CSCI architectural design.
+
+This section shall be divided into the following paragraphs to describe the CSCI architectural design. If part or all of the design depends upon CSCI states or modes, this dependency shall be indicated. If design information falls into more than one paragraph, it may be presented once and referenced from the other paragraphs. Design conventions needed to understand the design shall be presented or referenced.
+
+## 4.1 CSCI components.
+
+This paragraph shall:
+
+a. Identify the software components of the CSCI (Computer Software Components (CSCs) or other decomposition entities). Each component shall be assigned a project-unique identifier. Note: A database may be treated as a CSC or as part of a CSC.
+
+b. Show the static (such as "consists of") relationship(s) of the components. Multiple relationships may be presented, depending on the selected design methodology.
+
+c. State the purpose of each component and identify the CSCI requirements and CSCI-wide design decisions allocated to it. (Alternatively, the allocation of requirements may be provided in 6.a.)
+
+d. Identify each component's development status/type, if known (such as new development, existing component to be reused as is, existing design to be reused as is, existing design or component to be reengineered, component to be developed for reuse, component planned for Build N, etc.) For existing design or components, the description shall provide identifying information, such as name, version, documentation references, location, etc.
+
+e. Describe the resource utilization of the CSCI, that is, the allocation of computer hardware resources (such as processor capacity, memory capacity, input/output device capacity, auxiliary storage capacity, and communications/network equipment capacity) to the CSCI's software components. The description shall state the conditions under which the resource utilization is to be measured.
+
+f. Describe the CSCI's program library, that is, the contents (computer files, data files, program files, etc.) and any applicable characteristics of the program library used in developing, testing, and integrating the software components and in generating the executable software.
+
+## 4.2 Concept of execution.
+
+This paragraph shall describe the concept of execution among the software components. It shall include diagrams and descriptions showing the dynamic relationship of the components, that is, how they will interact during CSCI operation, including, as applicable, flow of execution control, data flow, dynamically controlled sequencing, state transition diagrams, timing diagrams, priorities among components, handling of interrupts, timing/sequencing relationships, exception handling, concurrent execution, dynamic allocation/deallocation, dynamic creation/deletion of objects, processes, tasks, and other aspects of dynamic behavior.
+
+## 4.3 Interface design.
+
+This paragraph shall be divided into the following subparagraphs to describe the interface characteristics of the CSCI's software components. It shall include both interfaces among the components and their interfaces with external entities such as other systems, HWCIs, CSCIs, and users. Note: There is no requirement for these interfaces to be completely designed at this level; this paragraph is provided to allow the recording of interface design decisions made as part of CSCI architectural design. If part or all of this information is contained in Interface Design Descriptions (IDDs) or elsewhere, these sources may be referenced.
+
+### 4.3.1 Interface identification and diagrams.
+
+This paragraph shall state the project-unique identifier assigned to each interface and shall identify the interfacing entities (systems, configuration items, users, etc.) by name, number, version, and documentation references, as applicable. The identification shall state which entities have fixed interface characteristics (and therefore impose interface requirements on interfacing entities) and which are being developed or modified (thus having interface requirements imposed on them). One or more interface diagrams shall be provided, as appropriate, to depict the interfaces.
+
+### 4.3.x (Project-unique identifier of interface).
+
+This paragraph (beginning with 4.3.2) shall identify an interface by project-unique identifier, shall briefly identify the interfacing entities, and shall be divided into subparagraphs as needed to describe the interface characteristics of one or both of the interfacing entities. If a given interfacing entity is not covered by this SDD (for example, an external system) but its interface characteristics need to be mentioned to describe interfacing entities that are, these characteristics shall be stated as assumptions or as "When [the entity not covered] does this, [the entity that is covered] will ...." This paragraph may reference other documents (such as data dictionaries, standards for protocols, and standards for user interfaces) in place of stating the information here. The design description shall include the following, as applicable, presented in any order suited to the information to be provided, and shall note any differences in these characteristics from the point of view of the interfacing entities (such as different expectations about the size, frequency, or other characteristics of data elements):
+
+a. Priority assigned to the interface by the interfacing entity(ies)
+
+b. Type of interface (such as real-time data transfer, storage-and-retrieval of data, etc.) to be implemented
+
+c. Characteristics of individual data elements that the interfacing entity(ies) will provide, store, send, access, receive, etc., such as:
+
+   1. Names/identifiers
+      a. Project-unique identifier
+      b. Non-technical (natural-language) name
+      c. DoD standard data element name
+      d. Technical name (e.g., variable or field name in code or database)
+      e. Abbreviation or synonymous names
+   2. Data type (alphanumeric, integer, etc.)
+   3. Size and format (such as length and punctuation of a character string)
+   4. Units of measurement (such as meters, dollars, nanoseconds)
+   5. Range or enumeration of possible values (such as 0-99)
+   6. Accuracy (how correct) and precision (number of significant digits)
+   7. Priority, timing, frequency, volume, sequencing, and other constraints, such as whether the data element may be updated and whether business rules apply
+   8. Security and privacy constraints
+   9. Sources (setting/sending entities) and recipients (using/receiving entities)
+
+d. Characteristics of data element assemblies (records, messages, files, arrays, displays, reports, etc.) that the interfacing entity(ies) will provide, store, send, access, receive, etc., such as:
+
+   1. Names/identifiers
+      a. Project-unique identifier to be used for traceability
+      b. Non-technical (natural language) name
+      c. Technical name (e.g., record or data structure name in code or database)
+      d. Abbreviations or synonymous names
+   2. Data elements in the assembly and their structure (number, order, grouping)
+   3. Medium (such as disk) and structure of data elements/assemblies on the medium
+   4. Visual and auditory characteristics of displays and other outputs (such as colors, layouts, fonts, icons and other display elements, beeps, lights)
+   5. Relationships among assemblies, such as sorting/access characteristics
+   6. Priority, timing, frequency, volume, sequencing, and other constraints, such as whether the assembly may be updated and whether business rules apply
+   7. Security and privacy constraints
+   8. Sources (setting/sending entities) and recipients (using/receiving entities)
+
+e. Characteristics of communication methods that the interfacing entity(ies) will use for the interface, such as:
+
+   1. Project-unique identifier(s)
+   2. Communication links/bands/frequencies/media and their characteristics
+   3. Message formatting
+   4. Flow control (such as sequence numbering and buffer allocation)
+   5. Data transfer rate, whether periodic/aperiodic, and interval between transfers
+   6. Routing, addressing, and naming conventions
+   7. Transmission services, including priority and grade
+   8. Safety/security/privacy considerations, such as encryption, user authentication, compartmentalization, and auditing
+
+f. Characteristics of protocols that the interfacing entity(ies) will use for the interface, such as:
+
+   1. Project-unique identifier(s)
+   2. Priority/layer of the protocol
+   3. Packeting, including fragmentation and reassembly, routing, and addressing
+   4. Legality checks, error control, and recovery procedures
+   5. Synchronization, including connection establishment, maintenance, termination
+   6. Status, identification, and any other reporting features
+
+g. Other characteristics, such as physical compatibility of the interfacing entity(ies) (dimensions, tolerances, loads, voltages, plug compatibility, etc.)
+
+# 5. CSCI detailed design.
+
+This section shall be divided into the following paragraphs to describe each software component of the CSCI. If part or all of the design depends upon CSCI states or modes, this dependency shall be indicated. If design information falls into more than one paragraph, it may be presented once and referenced from the other paragraphs. Design conventions needed to understand the design shall be presented or referenced.
+
+## 5.x (Project-unique identifier of a software component, or designator for a group of software components).
+
+This paragraph shall identify a software component by project-unique identifier, state its purpose, and describe its design. If a software component contains other components, this paragraph shall identify them and describe the static (such as "consists of") relationships among them. The design of each software component shall describe, as applicable:
+
+a. The unit design decisions, including the algorithms to be used, the basis for the decisions (such as requirements, CSCI-wide design decisions, design conventions, etc.), and the alternatives considered and rejected, with rationale.
+
+b. Any constraints, limitations, or unusual features in the design of the software component.
+
+c. The programming language to be used and rationale for its use if other than the specified CSCI language.
+
+d. If the design is not expressed in a programming language, the procedure commands, design notations, or other means used to describe the design; for example, flowcharts, pseudocode, decision tables, or a combination of these.
+
+e. If the software component contains a database, data elements, record layouts, and file structures (such as files, data structures, objects, and tables) to be used in the design, along with their relationships.
+
+f. If the software component contains or is affected by constraints, describe any restrictions or limitations on the software component (such as restrictions or limitations on hardware requirements, accuracy, speed, frequency, or reliability).
+
+# 6. Requirements traceability.
+
+This paragraph shall contain:
+
+a. Traceability from each software component identified in this SDD to the CSCI requirements allocated to it. (Alternatively, this traceability may be provided in 4.1.)
+
+b. Traceability from each CSCI requirement to the software components to which it is allocated.
+
+# 7. Notes.
+
+This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall contain an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document.
+
+# A. Appendixes.
+
+Appendixes may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling. Appendixes shall be lettered alphabetically (A, B, etc.).

package/package.json

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