ma-agents 2.16.2 → 2.17.0

package/lib/bmad-workflows/mil498/sss/instructions.md

@@ -0,0 +1,96 @@
+# Generate System/Subsystem Specification (SSS)
+
+> MIL-STD-498 Data Item Description: DI-IPSC-81431
+
+## Objective
+
+Generate a compliant SSS document by extracting and organizing system-level requirements from existing project artifacts into the MIL-STD-498 SSS template structure. The SSS specifies requirements at the system or subsystem level, not at the software (CSCI) level.
+
+## Step 1 — Discover Project Artifacts
+
+Search the project for the following artifacts. Communicate in {communication_language}. Inform {user_name} which artifacts were found and which are missing.
+
+| Priority | Artifact | Search Pattern |
+|----------|----------|----------------|
+| Required | Product Brief | `**/product-brief*.md` |
+| Required | PRD | `**/prd.md`, `**/prd-*.md` |
+| Recommended | Architecture | `**/architecture.md`, `**/architecture-*.md` |
+| Optional | OCD | `**/OCD.md` |
+| Optional | UX Designs | `**/ux-design*.md` |
+
+If **required** artifacts are missing, warn the user and ask whether to proceed with available data or stop.
+
+## Step 2 — Load Template
+
+Read the SSS template from:
+`{template}`
+
+This defines the required DID sections and content expectations for each paragraph.
+
+## Step 3 — Generate Document
+
+Write the document in {document_output_language}, populating each template section. Keep requirements at the **system/subsystem level** — avoid low-level software implementation details.
+
+### Section 1: Scope
+- **1.1 Identification**: Extract system name, version, identifiers from PRD/Product Brief
+- **1.2 System overview**: Summarize system purpose, nature, and stakeholders
+- **1.3 Document overview**: Describe this SSS document's purpose and contents
+
+### Section 2: Referenced documents
+- List all project artifacts and external standards used
+
+### Section 3: Requirements
+
+- **3.1 Required states and modes**: Identify system-level operational states from Architecture/PRD (e.g., operational, maintenance, degraded, emergency). If none, state so explicitly
+- **3.2 System capability requirements**: Map high-level PRD features and Product Brief goals to system capabilities. Each capability requirement (3.2.1, 3.2.2, etc.) must have:
+  - A unique identifier (SSS-CAP-001 format)
+  - Clear, testable statement
+  - Performance parameters where applicable
+  - Behavior under error conditions
+- **3.3 System external interface requirements**: Map top-level external interfaces from Architecture — other systems, hardware, users, networks
+- **3.4 System internal interface requirements**: Map interfaces between major subsystems or components
+- **3.5 System internal data requirements**: System-level data stores, data flows between subsystems
+- **3.6 Adaptation requirements**: Installation and site-specific configuration needs
+- **3.7 Safety requirements**: System-level safety requirements
+- **3.8 Security and privacy requirements**: System-level security requirements from PRD
+- **3.9 System environment requirements**: Physical, regulatory, and operational environment constraints
+- **3.10 Computer resource requirements**: System-level hardware and infrastructure requirements
+- **3.11 System quality factors**: Reliability, availability, maintainability, portability requirements
+- **3.12 Design and implementation constraints**: Technology and methodology constraints
+- **3.13-3.18**: Additional requirement categories as defined in the template
+
+### Section 4: Qualification provisions
+- For each requirement in Section 3, specify the qualification method: Demonstration, Test, Analysis, or Inspection
+
+### Section 5: Requirements traceability
+- **5.a**: For subsystem specs, map each requirement to parent system requirements
+- **5.b**: Map parent requirements to subsystem requirements that address them
+
+### Section 6: Notes
+- Glossary of terms, acronyms, and abbreviations
+
+## Step 4 — Validate
+
+Before presenting to the user, verify:
+- All template sections are populated or marked "Not applicable" with justification
+- Requirements are at the system level (not CSCI/software level)
+- Every requirement has a unique identifier and is testable
+- Qualification methods are specified for all requirements
+- Document is written in {document_output_language}
+
+## Step 5 — Review
+
+Present the complete document to {user_name} for review.
+Highlight any sections where information was inferred or assumptions were made.
+Offer to refine any section based on feedback.
+
+## Step 6 — Save
+
+Write the final document to:
+`{output_folder}/planning-artifacts/SSS.md`
+
+Confirm the file was saved and display a summary of:
+- Total system requirements identified
+- Number of capabilities documented
+- Qualification methods assigned
+- Any sections marked "Not applicable"

package/lib/bmad-workflows/mil498/sss/workflow.yaml

@@ -0,0 +1,15 @@
+name: "bmad-mil-generate-sss"
+version: "1.0.0"
+description: "Generate a MIL-STD-498 System/Subsystem Specification (SSS). Use when the user says 'generate SSS' or 'generate system specification'"
+
+config_source: "{project-root}/_bmad/bmm/config.yaml"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+output_folder: "{config_source}:output_folder"
+date: system-generated
+
+installed_path: "{project-root}/_bmad/bmm/workflows/mil498/sss"
+instructions: "{installed_path}/instructions.md"
+
+template: "{project-root}/_bmad/bmm/templates/mil498/SSS.md"

package/lib/bmad-workflows/mil498/std/instructions.md

@@ -0,0 +1,97 @@
+# Generate Software Test Description (STD)
+
+> MIL-STD-498 Data Item Description: DI-IPSC-81439
+
+## Objective
+
+Generate a compliant STD document by mapping test cases and procedures from project artifacts to the MIL-STD-498 STD template structure. The STD defines the test preparations, test cases, and test procedures for software qualification testing.
+
+## Step 1 — Discover Project Artifacts
+
+Search the project for the following artifacts. Communicate in {communication_language}. Inform {user_name} which artifacts were found and which are missing.
+
+| Priority | Artifact | Search Pattern |
+|----------|----------|----------------|
+| Required | Epics & Stories | `**/epics*.md`, `**/epic-*.md`, `**/stories/*.md` |
+| Required | Architecture | `**/architecture.md`, `**/architecture-*.md` |
+| Recommended | SRS | `**/SRS.md` |
+| Recommended | PRD | `**/prd.md`, `**/prd-*.md` |
+| Optional | Existing test files | `**/test/**`, `**/tests/**`, `**/__tests__/**`, `**/*.test.*`, `**/*.spec.*` |
+
+If **required** artifacts are missing, warn the user and ask whether to proceed with available data or stop.
+
+## Step 2 — Load Template
+
+Read the STD template from:
+`{template}`
+
+This defines the required DID sections and content expectations for each paragraph.
+
+## Step 3 — Generate Document
+
+Write the document in {document_output_language}, populating each template section:
+
+### Section 1: Scope
+- **1.1 Identification**: Extract system and software identifiers from PRD/Architecture
+- **1.2 System overview**: Summarize the system and the CSCI(s) being tested
+- **1.3 Document overview**: Describe this STD document's purpose and contents
+
+### Section 2: Referenced documents
+- List all project artifacts, test standards, and other references used
+
+### Section 3: Test preparations
+
+For each test identified, provide (organized as 3.x subsections):
+
+- **3.x.1 Hardware preparation**: Test environment hardware requirements from Architecture — servers, devices, network configuration. Include setup procedures
+- **3.x.2 Software preparation**: Test environment software requirements — OS, databases, dependencies, test frameworks. Include installation and configuration steps
+- **3.x.3 Other pre-test preparations**: Test data setup, user accounts, external service mocks, environment variables. Include any prerequisites that must be satisfied
+
+### Section 4: Test descriptions
+
+For each test case (organized as 4.x subsections), derive from Story acceptance criteria and SRS requirements:
+
+- **4.x.1 Test identifier**: Unique identifier (STD-TEST-001 format)
+- **4.x.2 Test objective**: What requirement(s) this test verifies. Reference SRS requirement IDs if available
+- **4.x.3 Input data**: Specific test inputs, preconditions, and initial state
+- **4.x.4 Expected results**: Precise expected outputs, state changes, and behaviors
+- **4.x.5 Criteria for evaluating results**: Pass/fail criteria
+- **4.x.6 Test procedure**: Step-by-step procedure to execute the test
+- **4.x.7 Assumptions and constraints**: Any assumptions about the test environment
+
+Group test cases by capability/feature (mapping to Epics) for clarity.
+
+### Section 5: Requirements traceability
+- Map each test case to the SRS requirement(s) it verifies
+- Ensure every SRS requirement has at least one associated test case
+- Identify any requirements that cannot be tested and explain why
+
+### Section 6: Notes
+- Glossary of test terminology and abbreviations
+- References to test automation frameworks or tools used
+
+## Step 4 — Validate
+
+Before presenting to the user, verify:
+- All template sections are populated or marked "Not applicable" with justification
+- Every test case has a unique identifier and clear pass/fail criteria
+- Requirements traceability is complete (all requirements covered)
+- Test procedures are detailed enough to be repeatable
+- Document is written in {document_output_language}
+
+## Step 5 — Review
+
+Present the complete document to {user_name} for review.
+Highlight any requirements without test coverage.
+Offer to refine any section based on feedback.
+
+## Step 6 — Save
+
+Write the final document to:
+`{output_folder}/planning-artifacts/STD.md`
+
+Confirm the file was saved and display a summary of:
+- Total number of test cases defined
+- Requirements coverage percentage
+- Any untestable requirements identified
+- Any sections marked "Not applicable"

package/lib/bmad-workflows/mil498/std/workflow.yaml

@@ -0,0 +1,15 @@
+name: "bmad-mil-generate-std"
+version: "1.0.0"
+description: "Generate a MIL-STD-498 Software Test Description (STD). Use when the user says 'generate STD' or 'generate software test description'"
+
+config_source: "{project-root}/_bmad/bmm/config.yaml"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+output_folder: "{config_source}:output_folder"
+date: system-generated
+
+installed_path: "{project-root}/_bmad/bmm/workflows/mil498/std"
+instructions: "{installed_path}/instructions.md"
+
+template: "{project-root}/_bmad/bmm/templates/mil498/STD.md"

package/lib/bmad.js

@@ -149,65 +149,71 @@ async function registerMilWorkflows(projectRoot) {
     const milEntries = [
         {
             name: 'Generate SRS', code: 'GS',
-            file: '_bmad/bmm/workflows/mil498/bmad-mil-generate-srs.md',
+            file: '_bmad/bmm/workflows/mil498/srs/workflow.yaml',
             command: 'bmad-mil-generate-srs',
             description: 'Generate a MIL-STD-498 Software Requirements Specification from BMAD project artifacts'
         },
         {
             name: 'Generate SDD', code: 'GD',
-            file: '_bmad/bmm/workflows/mil498/bmad-mil-generate-sdd.md',
+            file: '_bmad/bmm/workflows/mil498/sdd/workflow.yaml',
             command: 'bmad-mil-generate-sdd',
             description: 'Generate a MIL-STD-498 Software Design Description from architecture and design docs'
         },
         {
             name: 'Generate SDP', code: 'GP',
-            file: '_bmad/bmm/workflows/mil498/bmad-mil-generate-sdp.md',
+            file: '_bmad/bmm/workflows/mil498/sdp/workflow.yaml',
             command: 'bmad-mil-generate-sdp',
             description: 'Generate a MIL-STD-498 Software Development Plan from project planning artifacts'
         },
         {
             name: 'Generate OCD', code: 'GO',
-            file: '_bmad/bmm/workflows/mil498/bmad-mil-generate-ocd.md',
+            file: '_bmad/bmm/workflows/mil498/ocd/workflow.yaml',
             command: 'bmad-mil-generate-ocd',
             description: 'Generate a MIL-STD-498 Operational Concept Description from PRD and architecture'
         },
         {
             name: 'Generate SSS', code: 'SS',
-            file: '_bmad/bmm/workflows/mil498/bmad-mil-generate-sss.md',
+            file: '_bmad/bmm/workflows/mil498/sss/workflow.yaml',
             command: 'bmad-mil-generate-sss',
             description: 'Generate a MIL-STD-498 System/Subsystem Specification from project requirements'
         },
         {
             name: 'Generate STD', code: 'GT',
-            file: '_bmad/bmm/workflows/mil498/bmad-mil-generate-std.md',
+            file: '_bmad/bmm/workflows/mil498/std/workflow.yaml',
             command: 'bmad-mil-generate-std',
             description: 'Generate a MIL-STD-498 Software Test Description from epics stories and architecture'
+        },
+        {
+            name: 'Generate SSDD', code: 'SD',
+            file: '_bmad/bmm/workflows/mil498/ssdd/workflow.yaml',
+            command: 'bmad-mil-generate-ssdd',
+            description: 'Generate a MIL-STD-498 System/Subsystem Design Description from architecture and PRD'
         }
     ];
 
-    // Append to module-help.csv
+    // Append or update entries in module-help.csv
     const moduleHelpPath = path.join(projectRoot, BMAD_DIR, 'bmm', 'module-help.csv');
     if (fs.existsSync(moduleHelpPath)) {
         let content = await fs.readFile(moduleHelpPath, 'utf-8');
         for (const entry of milEntries) {
-            if (!content.includes(entry.command)) {
-                const row = `bmm,anytime,${entry.name},${entry.code},,${entry.file},${entry.command},false,mil498,Create Mode,${entry.description},planning_artifacts,document,`;
-                content = content.trimEnd() + '\n' + row + '\n';
-            }
+            const row = `bmm,anytime,${entry.name},${entry.code},,${entry.file},${entry.command},false,mil498,Create Mode,${entry.description},planning_artifacts,document,`;
+            // Remove any existing line for this command, then append the current one
+            const lines = content.split('\n').filter(line => !line.includes(entry.command));
+            content = lines.join('\n').trimEnd() + '\n' + row + '\n';
         }
         await fs.writeFile(moduleHelpPath, content, 'utf-8');
         console.log(chalk.cyan(`    + Registered MIL-STD-498 workflows in module-help.csv`));
     }
 
-    // Append to bmad-help.csv
+    // Append or update entries in bmad-help.csv
     const bmadHelpPath = path.join(projectRoot, BMAD_DIR, '_config', 'bmad-help.csv');
     if (fs.existsSync(bmadHelpPath)) {
         let content = await fs.readFile(bmadHelpPath, 'utf-8');
         for (const entry of milEntries) {
-            if (!content.includes(entry.command)) {
-                const row = `bmm,anytime,${entry.name},${entry.code},,${entry.file},${entry.command},false,mil498,bmad:MIL-STD-498 compliance:agent:mil498,Joseph,📜 MIL-STD-498 Expert,Create Mode,${entry.description},planning_artifacts,document`;
-                content = content.trimEnd() + '\n' + row + '\n';
-            }
+            const row = `bmm,anytime,${entry.name},${entry.code},,${entry.file},${entry.command},false,mil498,bmad:MIL-STD-498 compliance:agent:mil498,Joseph,📜 MIL-STD-498 Expert,Create Mode,${entry.description},planning_artifacts,document`;
+            // Remove any existing line for this command, then append the current one
+            const lines = content.split('\n').filter(line => !line.includes(entry.command));
+            content = lines.join('\n').trimEnd() + '\n' + row + '\n';
         }
         await fs.writeFile(bmadHelpPath, content, 'utf-8');
         console.log(chalk.cyan(`    + Registered MIL-STD-498 workflows in bmad-help.csv`));

package/package.json

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

package/.agent/workflows/bmad-agent-bmad-master.md

@@ -1,15 +0,0 @@
----
-name: 'bmad-master'
-description: 'bmad-master agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/core/agents/bmad-master.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-bmm-analyst.md

@@ -1,15 +0,0 @@
----
-name: 'analyst'
-description: 'analyst agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/bmm/agents/analyst.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-bmm-architect.md

@@ -1,15 +0,0 @@
----
-name: 'architect'
-description: 'architect agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/bmm/agents/architect.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-bmm-dev.md

@@ -1,15 +0,0 @@
----
-name: 'dev'
-description: 'dev agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/bmm/agents/dev.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-bmm-pm.md

@@ -1,15 +0,0 @@
----
-name: 'pm'
-description: 'pm agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/bmm/agents/pm.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-bmm-qa.md

@@ -1,15 +0,0 @@
----
-name: 'qa'
-description: 'qa agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/bmm/agents/qa.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-bmm-quick-flow-solo-dev.md

@@ -1,15 +0,0 @@
----
-name: 'quick-flow-solo-dev'
-description: 'quick-flow-solo-dev agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/bmm/agents/quick-flow-solo-dev.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-bmm-sm.md

@@ -1,15 +0,0 @@
----
-name: 'sm'
-description: 'sm agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/bmm/agents/sm.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-bmm-tech-writer.md

@@ -1,15 +0,0 @@
----
-name: 'tech-writer'
-description: 'tech-writer agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/bmm/agents/tech-writer/tech-writer.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-bmm-ux-designer.md

@@ -1,15 +0,0 @@
----
-name: 'ux-designer'
-description: 'ux-designer agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/bmm/agents/ux-designer.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-cis-brainstorming-coach.md

@@ -1,15 +0,0 @@
----
-name: 'brainstorming-coach'
-description: 'brainstorming-coach agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/cis/agents/brainstorming-coach.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-cis-creative-problem-solver.md

@@ -1,15 +0,0 @@
----
-name: 'creative-problem-solver'
-description: 'creative-problem-solver agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/cis/agents/creative-problem-solver.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-cis-design-thinking-coach.md

@@ -1,15 +0,0 @@
----
-name: 'design-thinking-coach'
-description: 'design-thinking-coach agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/cis/agents/design-thinking-coach.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-cis-innovation-strategist.md

@@ -1,15 +0,0 @@
----
-name: 'innovation-strategist'
-description: 'innovation-strategist agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/cis/agents/innovation-strategist.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-cis-presentation-master.md

@@ -1,15 +0,0 @@
----
-name: 'presentation-master'
-description: 'presentation-master agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/cis/agents/presentation-master.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-agent-cis-storyteller.md

@@ -1,15 +0,0 @@
----
-name: 'storyteller'
-description: 'storyteller agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/_bmad/cis/agents/storyteller/storyteller.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

package/.agent/workflows/bmad-bmm-check-implementation-readiness.md

@@ -1,6 +0,0 @@
----
-name: 'check-implementation-readiness'
-description: 'Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md, READ its entire contents and follow its directions exactly!

package/.agent/workflows/bmad-bmm-code-review.md

@@ -1,14 +0,0 @@
----
-name: 'code-review'
-description: 'Perform adversarial code review finding specific issues. Use when the user says "run code review" or "review this code"'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml
-3. Pass the yaml path {project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.agent/workflows/bmad-bmm-correct-course.md

@@ -1,14 +0,0 @@
----
-name: 'correct-course'
-description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
-3. Pass the yaml path {project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.agent/workflows/bmad-bmm-create-architecture.md

@@ -1,6 +0,0 @@
----
-name: 'create-architecture'
-description: 'Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md, READ its entire contents and follow its directions exactly!