ma-agents 3.6.2 → 3.8.0

package/lib/bmad-extension-plugin/skills/mil498-sdd/prompts/03-generate-document.md

@@ -0,0 +1,98 @@
+# Step 3 — Generate Document
+
+Write the document in {document_output_language}, populating each template section.
+
+## Revision History
+
+Before writing any content, add a **Revision History table** immediately after the document title. If this is a new document, create the table with version `1.0`. If updating an existing document, read the existing revision history and add a new row with an incremented version number and a summary of all changes made in this session. See the `document-revision-history` skill for full formatting rules.
+
+```markdown
+| Version | Date | Author | Changes |
+|---------|------|--------|---------|
+| 1.0 | {date} | Agent ({model}) | Initial document generation |
+```
+
+## Section 1: Scope
+- **1.1 Identification**: Identify the CSCI by name, version, and project-unique identifier (as assigned in the SSDD)
+- **1.2 System overview**: Summarize the system and this CSCI's role within it, referencing the SSDD
+- **1.3 Document overview**: Describe this SDD document's purpose and contents
+
+## Section 2: Referenced documents
+- List all predecessor MIL-STD-498 documents (SSDD, SRS, SSS) and project artifacts used. Include number, title, revision, and date
+
+## Section 3: CSCI-wide design decisions
+
+**CRITICAL BEHAVIORAL GUIDANCE**: Like the SSDD, this section describes the CSCI's behavioral design — how it will behave from a user's point of view, ignoring internal implementation. Follow these rules:
+
+1. **Requirements-driven**: Every design decision MUST cite the specific SRS requirement(s) it satisfies
+2. **Behavioral, not implementation**: Describe patterns and approaches first, then technology choices parenthetically if essential
+3. **State-dependent decisions**: If a design decision depends on CSCI states or modes, indicate this dependency
+
+Document the following CSCI-wide design decisions (items a through e per the DID):
+
+- **a. CSCI behavioral design**: How the CSCI behaves in response to inputs and conditions — actions, response times, algorithms/rules, error handling. Describe from the user's perspective. Reference SRS capability requirements (3.2.x)
+- **b. Database/data file design**: How databases and data files within this CSCI appear to users and external systems. Reference SRS internal data requirements (3.5). If Database Design Descriptions (DBDDs) exist, they may be referenced
+- **c. Safety, security, privacy**: Selected approaches to meeting safety, security, and privacy requirements for this CSCI. Place in **separate subparagraphs** for critical requirements. Reference SRS sections 3.7, 3.8
+- **d. Other CSCI-wide design decisions**: Flexibility, availability, maintainability approaches. Rationale for architectural patterns selected. Reference SRS quality factors (3.11) and design constraints (3.12)
+- **e. Design and implementation standards**: Standards to be followed for design, coding, testing (reference SDP if available)
+
+## Section 4: CSCI architectural design
+
+- **4.1 CSCI components** (items a through f — all are required):
+
+  **a.** Identify all CSCs (Computer Software Components) within this CSCI — modules, packages, services, libraries. Each CSC shall have a project-unique identifier. Also identify software units within CSCs where applicable.
+
+  **b.** Show static ("consists of") relationships using component/class/package diagrams. Multiple relationship views may be presented.
+
+  **c.** State each CSC's purpose and the SRS requirements allocated to it. (Alternatively, allocation may be provided in Section 6.a.)
+
+  **d.** Identify each CSC's development status: new development, existing reuse as-is, existing design reuse, reengineering, etc. For existing components, provide identifying information.
+
+  **e.** Describe **resource utilization** — allocation of computer hardware resources (processor capacity, memory, I/O, storage) to each CSC. State conditions under which utilization will be measured. (This differs from SSDD 4.1.e which describes hardware; here it's about utilization allocation.)
+
+  **f.** Describe the CSCI's **program library** — contents including computer files, data files, program files, and their relationships.
+
+- **4.2 Concept of execution**:
+  - Describe dynamic relationships between CSCs — how they interact during operation
+  - Include: execution flow, data flow, state transitions, timing/sequencing, priorities, interrupt handling, concurrent execution, dynamic allocation/deallocation, exception handling
+  - Use sequence diagrams, state transition diagrams, or timing diagrams where helpful
+
+- **4.3 Interface design**:
+  - **4.3.1 Interface identification and diagrams**: List all interfaces (between CSCs and with external entities) with project-unique identifiers. Identify fixed vs. developing interfaces. Provide interface diagrams.
+  - **4.3.x (per interface)**: For each interface, document as applicable:
+    - **a.** Priority assigned to the interface
+    - **b.** Type of interface (real-time data transfer, storage-and-retrieval, etc.)
+    - **c.** Data elements: names/identifiers, data types, sizes/formats, units, ranges, accuracy/precision, timing/frequency constraints, security constraints, sources and recipients
+    - **d.** Data element assemblies: records, messages, data structures — names, structure, medium, relationships, constraints
+    - **e.** Communication methods: links/media, message formatting, flow control, data transfer rates, routing
+    - **f.** Protocols: priority/layer, packeting, error control/recovery, synchronization
+    - **g.** Physical compatibility considerations
+
+## Section 5: CSCI detailed design
+
+**This is the most important section of the SDD.** For each software unit identified in Section 4.1, provide a detailed design description. Organize as subsections (5.x per CSC, or 5.x per software unit):
+
+For each software unit (5.x), document the following items (a through f per the DID):
+
+- **a. Unit design decisions**: Design decisions specific to this unit, including algorithms, processing logic, data transformations, and business rules. **Extract from Epics and User Stories** — map Story acceptance criteria to specific processing logic. Reference the SRS requirements this unit satisfies.
+- **b. Design constraints**: Any constraints on the unit's design imposed by the CSCI-wide decisions, standards, or external interfaces
+- **c. Programming language**: If different from the CSCI-wide language specified in Section 3.e
+- **d. Control flow / logic description**: Describe the unit's control logic — how it processes inputs, makes decisions, handles conditions. Use flowcharts, pseudocode, or decision tables where helpful. Map from Story acceptance criteria and business rules.
+- **e. Data elements and structures**: Internal data elements, record layouts, data structures, file formats used by the unit
+- **f. Restrictions and limitations**: Any restrictions on the unit's use, dependencies, known limitations, or assumptions
+
+## Section 6: Requirements traceability
+- **6.a**: Map each CSC/software unit to the SRS requirements it addresses
+- **6.b**: Map each SRS requirement to the CSCs/units that implement it
+- Ensure every SRS requirement allocated to this CSCI is accounted for in both directions
+
+## Section 7: Notes
+- Alphabetical listing of all acronyms, abbreviations, and their meanings
+- Glossary of design terms and definitions
+
+## Appendix A
+- Include any supplementary material (detailed algorithms, data dictionaries, message format specifications) that supports the main body
+
+---
+
+**CONFIRMATION GATE**: Present the generated document to the user for initial review. Wait for the user to confirm the content before proceeding to validation.

package/lib/bmad-extension-plugin/skills/mil498-sdd/prompts/04-validate.md

@@ -0,0 +1,16 @@
+# Step 4 — Validate
+
+Before presenting to the user, verify:
+- All template sections (1-7 and Appendix A) are populated or marked "Not applicable" with justification
+- This SDD covers exactly ONE CSCI as defined in the SSDD
+- Every CSC has a project-unique identifier
+- CSCI-wide design decisions (Section 3) are framed as behavioral responses to SRS requirements
+- Section 5 (detailed design) has entries for every software unit, with algorithms and logic extracted from Epics/Stories
+- Resource utilization (4.1.e) and program library (4.1.f) are documented
+- Interface descriptions (4.3.x) cover all seven aspects (a through g) where applicable
+- Requirements traceability (Section 6) covers all SRS requirements in both directions
+- Document is written in {document_output_language}
+
+---
+
+**CONFIRMATION GATE**: Present the validation results to the user. List any issues found and corrections made. Wait for the user to confirm before proceeding to the review step.

package/lib/bmad-extension-plugin/skills/mil498-sdd/prompts/05-review.md

@@ -0,0 +1,15 @@
+# Step 5 — Review
+
+Present the complete document to {user_name} for review.
+Highlight any sections where information was inferred or assumptions were made.
+Specifically ask about:
+- Is the CSC decomposition correct for this CSCI?
+- Are the algorithms and processing logic in Section 5 accurately extracted from the Stories?
+- Are there design decisions not captured in the Architecture or Epics?
+- Is the resource utilization allocation realistic?
+
+Offer to refine any section based on feedback.
+
+---
+
+**CONFIRMATION GATE**: Wait for the user to approve the document or request changes. If changes are requested, apply them and re-present for approval. Do not proceed to save until the user explicitly approves.

package/lib/bmad-extension-plugin/skills/mil498-sdd/prompts/06-save.md

@@ -0,0 +1,19 @@
+# Step 6 — Save
+
+Write the final document to:
+`{output_folder}/planning-artifacts/SDD.md`
+
+(If this is not the first CSCI's SDD, save as `SDD-{CSCI-identifier}.md`)
+
+Confirm the file was saved and display a summary of:
+- CSCI identifier and name
+- Number of CSCs identified
+- Number of software units with detailed design
+- Number of interfaces documented
+- Number of SRS requirements traced
+- Requirements coverage percentage
+- Any sections marked "Not applicable"
+
+---
+
+**CONFIRMATION GATE**: Confirm to the user that the document has been saved successfully and present the summary. The workflow is now complete.

package/lib/bmad-extension-plugin/skills/mil498-sdd/template.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/lib/bmad-extension-plugin/skills/mil498-sdp/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: mil498-sdp
+description: Generate MIL-STD-498 Software Development Plan (SDP)
+type: complex-workflow
+triggers:
+  - "generate SDP"
+  - "create software development plan"
+---
+
+# MIL-498: Software Development Plan (SDP)
+
+> MIL-STD-498 Data Item Description: DI-IPSC-81427
+
+## Workflow
+
+This workflow generates a MIL-STD-498 SDP document through progressive steps.
+The SDP describes how the software will be developed, including processes, methods, standards, and management plans.
+
+### Steps
+
+1. [Discover Project Artifacts](prompts/01-discover-project-artifacts.md)
+2. [Load Template](prompts/02-load-template.md)
+3. [Generate Document](prompts/03-generate-document.md)
+4. [Validate](prompts/04-validate.md)
+5. [Review](prompts/05-review.md)
+6. [Save](prompts/06-save.md)
+
+### Template
+
+Output template: [template.md](template.md)

package/lib/bmad-extension-plugin/skills/mil498-sdp/bmad-skill-manifest.yaml

@@ -0,0 +1,5 @@
+type: skill
+name: mil498-sdp
+module: ma-skills
+description: Generate MIL-STD-498 Software Development Plan (SDP)
+version: "1.0.0"

package/lib/bmad-extension-plugin/skills/mil498-sdp/prompts/01-discover-project-artifacts.md

@@ -0,0 +1,32 @@
+# 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` |
+| Recommended | Project Context | `**/project-context.md` |
+| Optional | Sprint Status | `**/sprint-status*.yaml`, `**/sprint-status*.md` |
+| Optional | Epics | `**/epics*.md` |
+
+If **required** artifacts are missing, warn the user and ask whether to proceed with available data or stop.
+
+## Document Dependencies
+
+The SDP describes how the software will be developed. It benefits from knowing the system architecture (SSDD) and what documents are planned for each CSCI.
+
+| Predecessor | Relationship | Search Pattern |
+|-------------|-------------|----------------|
+| SSDD (System/Subsystem Design Description) | Recommended — provides system architecture, CSCI decomposition, and specification tree | `**/SSDD.md` |
+| SSS (System/Subsystem Specification) | Optional — provides system requirements context | `**/SSS.md` |
+| OCD (Operational Concept Description) | Optional — provides operational context | `**/OCD.md` |
+
+If the SSDD exists, it MUST be loaded — the SDP should reference the CSCI decomposition when describing plans for CSCI-level activities (Section 5), and the specification tree (SSDD 4.1.f) informs Section 3.b (documentation requirements).
+
+If the SSDD has NOT been generated yet, **inform {user_name}**: "The SSDD has not been generated yet. The SDP benefits from the system architecture and CSCI decomposition in the SSDD. Would you like to proceed without it, or generate the SSDD first?"
+
+---
+
+**CONFIRMATION GATE**: Present the list of discovered artifacts to the user. Wait for the user to confirm before proceeding to the next step.

package/lib/bmad-extension-plugin/skills/mil498-sdp/prompts/02-load-template.md

@@ -0,0 +1,10 @@
+# Step 2 — Load Template
+
+Read the SDP template from:
+[template.md](../template.md)
+
+This defines the required DID sections and content expectations for each paragraph.
+
+---
+
+**CONFIRMATION GATE**: Confirm to the user that the template has been loaded and summarize the major sections. Wait for the user to confirm before proceeding to document generation.

package/lib/bmad-extension-plugin/skills/mil498-sdp/prompts/03-generate-document.md

@@ -0,0 +1,187 @@
+# Step 3 — Generate Document
+
+Write the document in {document_output_language}, populating each template section. **Important**: Each paragraph in Sections 4 and 5 shall identify applicable risks/uncertainties and plans for dealing with them.
+
+## Revision History
+
+Before writing any content, add a **Revision History table** immediately after the document title. If this is a new document, create the table with version `1.0`. If updating an existing document, read the existing revision history and add a new row with an incremented version number and a summary of all changes made in this session. See the `document-revision-history` skill for full formatting rules.
+
+```markdown
+| Version | Date | Author | Changes |
+|---------|------|--------|---------|
+| 1.0 | {date} | Agent ({model}) | Initial document generation |
+```
+
+## Section 1: Scope
+- **1.1 Identification**: Extract project name, version, identifiers from PRD
+- **1.2 System overview**: Summarize from Product Brief and PRD
+- **1.3 Document overview**: Describe this SDP document's purpose
+- **1.4 Relationship to other plans**: Reference any related project plans (quality assurance plans, configuration management plans, test plans)
+
+## Section 2: Referenced documents
+- List all project artifacts, standards, and external references with number, title, revision, and date
+
+## Section 3: Overview of required work
+Provide an overview of the following (items a through f per the DID):
+- **a.** Requirements and constraints on the system and software to be developed
+- **b.** Requirements and constraints on project documentation (reference SSDD specification tree if available)
+- **c.** Position of the project in the system life cycle
+- **d.** The selected program/acquisition strategy or any requirements/constraints on it
+- **e.** Requirements and constraints on project schedules and resources
+- **f.** Other requirements and constraints (security, privacy, methods, standards, interdependencies in hardware and software development)
+
+## Section 4: Plans for general software development activities
+
+**4.1 Software development process**: Describe the software development process to be used. Identify planned builds (if applicable), their objectives, and the software development activities in each build.
+
+**4.2 General plans for software development**:
+
+- **4.2.1 Software development methods**: Describe or reference the methods to be used — manual and automated tools and procedures. Map the project's development methodology to MIL-STD-498 activities.
+- **4.2.2 Standards for software products**: Describe standards for representing requirements, design, code, test cases, test procedures, and test results. For code standards, include:
+  - a. Format standards (indentation, spacing, capitalization, ordering)
+  - b. Header comment standards (name, version, modification history, purpose, requirements/design decisions, processing notes, data notes)
+  - c. Other comment standards (required number and content)
+  - d. Naming conventions (variables, parameters, packages, procedures, files)
+  - e. Restrictions on language constructs or features
+  - f. Restrictions on code complexity
+- **4.2.3 Reusable software products**:
+  - 4.2.3.1 Incorporating reusable software products — approach for identifying, evaluating, and incorporating reuse candidates
+  - 4.2.3.2 Developing reusable software products — approach for identifying and reporting reuse opportunities
+- **4.2.4 Handling of critical requirements**:
+  - 4.2.4.1 Safety assurance
+  - 4.2.4.2 Security assurance
+  - 4.2.4.3 Privacy assurance
+  - 4.2.4.4 Assurance of other critical requirements
+- **4.2.5 Computer hardware resource utilization**: Approach for allocating and monitoring hardware resource utilization
+- **4.2.6 Recording rationale**: Approach for recording rationale for key project decisions
+- **4.2.7 Access for acquirer review**: Approach for providing acquirer access to facilities for review
+
+## Section 5: Plans for performing detailed software development activities
+
+For each subsection below, describe the approach (methods/procedures/tools) for: 1) analysis or technical tasks, 2) recording of results, 3) preparation of deliverables. Identify applicable risks/uncertainties and plans for dealing with them.
+
+- **5.1 Project planning and oversight**:
+  - 5.1.1 Software development planning (updates to this plan)
+  - 5.1.2 CSCI test planning
+  - 5.1.3 System test planning
+  - 5.1.4 Software installation planning
+  - 5.1.5 Software transition planning
+  - 5.1.6 Following and updating plans, including management review intervals
+- **5.2 Establishing a software development environment**:
+  - 5.2.1 Software engineering environment
+  - 5.2.2 Software test environment
+  - 5.2.3 Software development library
+  - 5.2.4 Software development files
+  - 5.2.5 Non-deliverable software
+- **5.3 System requirements analysis**:
+  - 5.3.1 Analysis of user input
+  - 5.3.2 Operational concept
+  - 5.3.3 System requirements
+- **5.4 System design**:
+  - 5.4.1 System-wide design decisions
+  - 5.4.2 System architectural design
+- **5.5 Software requirements analysis**: Approach for deriving CSCI requirements from system requirements
+- **5.6 Software design**:
+  - 5.6.1 CSCI-wide design decisions
+  - 5.6.2 CSCI architectural design
+  - 5.6.3 CSCI detailed design
+- **5.7 Software implementation and unit testing**:
+  - 5.7.1 Software implementation
+  - 5.7.2 Preparing for unit testing
+  - 5.7.3 Performing unit testing
+  - 5.7.4 Revision and retesting
+  - 5.7.5 Analyzing and recording unit test results
+- **5.8 Unit integration and testing**:
+  - 5.8.1 Preparing for unit integration and testing
+  - 5.8.2 Performing unit integration and testing
+  - 5.8.3 Revision and retesting
+  - 5.8.4 Analyzing and recording unit integration and test results
+- **5.9 CSCI qualification testing**:
+  - 5.9.1 Independence in CSCI qualification testing
+  - 5.9.2 Testing on the target computer system
+  - 5.9.3 Preparing for CSCI qualification testing
+  - 5.9.4 Dry run of CSCI qualification testing
+  - 5.9.5 Performing CSCI qualification testing
+  - 5.9.6 Revision and retesting
+  - 5.9.7 Analyzing and recording CSCI qualification test results
+- **5.10 CSCI/HWCI integration and testing**:
+  - 5.10.1 Preparing for CSCI/HWCI integration and testing
+  - 5.10.2 Performing CSCI/HWCI integration and testing
+  - 5.10.3 Revision and retesting
+  - 5.10.4 Analyzing and recording CSCI/HWCI integration and test results
+- **5.11 System qualification testing**:
+  - 5.11.1 Independence in system qualification testing
+  - 5.11.2 Testing on the target computer system
+  - 5.11.3 Preparing for system qualification testing
+  - 5.11.4 Dry run of system qualification testing
+  - 5.11.5 Performing system qualification testing
+  - 5.11.6 Revision and retesting
+  - 5.11.7 Analyzing and recording system qualification test results
+- **5.12 Preparing for software use**:
+  - 5.12.1 Preparing the executable software
+  - 5.12.2 Preparing version descriptions for user sites
+  - 5.12.3 Preparing user manuals
+  - 5.12.4 Installation at user sites
+- **5.13 Preparing for software transition**:
+  - 5.13.1 Preparing the executable software
+  - 5.13.2 Preparing source files
+  - 5.13.3 Preparing version descriptions for the support site
+  - 5.13.4 Preparing the "as built" CSCI design and other support information
+  - 5.13.5 Updating the system design description
+  - 5.13.6 Preparing support manuals
+  - 5.13.7 Transition to the designated support site
+- **5.14 Software configuration management**:
+  - 5.14.1 Configuration identification
+  - 5.14.2 Configuration control
+  - 5.14.3 Configuration status accounting
+  - 5.14.4 Configuration audits
+  - 5.14.5 Packaging, storage, handling, and delivery
+- **5.15 Software product evaluation**:
+  - 5.15.1 In-process and final software product evaluations
+  - 5.15.2 Software product evaluation records, including items to be recorded
+  - 5.15.3 Independence in software product evaluation
+- **5.16 Software quality assurance**:
+  - 5.16.1 Software quality assurance evaluations
+  - 5.16.2 Software quality assurance records, including items to be recorded
+  - 5.16.3 Independence in software quality assurance
+- **5.17 Corrective action**:
+  - 5.17.1 Problem/change reports (including items to be recorded: project name, originator, problem number/name, affected element, dates, category/priority, description, analyst, recommended solution, impacts, status, correction details)
+  - 5.17.2 Corrective action system
+- **5.18 Joint technical and management reviews**:
+  - 5.18.1 Joint technical reviews, including a proposed set of reviews
+  - 5.18.2 Joint management reviews, including a proposed set of reviews
+- **5.19 Other software development activities**:
+  - 5.19.1 Risk management, including known risks and corresponding strategies
+  - 5.19.2 Software management indicators, including indicators to be used
+  - 5.19.3 Security and privacy
+  - 5.19.4 Subcontractor management
+  - 5.19.5 Interface with software IV&V agents
+  - 5.19.6 Coordination with associate developers
+  - 5.19.7 Improvement of project processes
+  - 5.19.8 Other activities not covered elsewhere
+
+For subsections that are not applicable to the project, state "Not applicable" with brief justification.
+
+## Section 6: Schedules and activity network
+- **a.** Schedule(s) identifying activities in each build, showing initiation of each activity, availability of draft and final deliverables and milestones, and completion of each activity
+- **b.** An activity network depicting sequential relationships and dependencies among activities, identifying those that impose the greatest time restrictions
+
+## Section 7: Project organization and resources
+- **7.1 Project organization**: Organizational structure, organizations involved, relationships, and authority/responsibility for carrying out activities
+- **7.2 Project resources**:
+  - **a.** Personnel resources: estimated staff-loading, breakdown by responsibility, skill levels, geographic locations, and security clearances
+  - **b.** Developer facilities: geographic locations, facilities, secure areas
+  - **c.** Acquirer-furnished items: equipment, software, services, documentation, data, facilities with schedule of when needed
+  - **d.** Other required resources with plan for obtaining them, dates needed, and availability
+
+## Section 8: Notes
+- Alphabetical listing of all acronyms, abbreviations, and their meanings
+- Glossary of terms and definitions
+- Background information to aid understanding
+
+## Appendix A
+- Include any supplementary material (charts, detailed schedules, classified data) that supports the main body
+
+---
+
+**CONFIRMATION GATE**: Present the generated document to the user for initial review. Wait for the user to confirm the content before proceeding to validation.

package/lib/bmad-extension-plugin/skills/mil498-sdp/prompts/04-validate.md

@@ -0,0 +1,13 @@
+# Step 4 — Validate
+
+Before presenting to the user, verify:
+- All template sections (1-8 and Appendix A) are populated or marked "Not applicable" with justification
+- Each paragraph in Sections 4-5 identifies applicable risks/uncertainties
+- All 19 subsections of Section 5 (5.1-5.19) are addressed
+- Schedule information is consistent with available Sprint/Epic data
+- Development process accurately reflects the actual methodology
+- Document is written in {document_output_language}
+
+---
+
+**CONFIRMATION GATE**: Present the validation results to the user. List any issues found and corrections made. Wait for the user to confirm before proceeding to the review step.

package/lib/bmad-extension-plugin/skills/mil498-sdp/prompts/05-review.md

@@ -0,0 +1,15 @@
+# Step 5 — Review
+
+Present the complete document to {user_name} for review.
+Highlight any sections where information was inferred or assumptions were made.
+Specifically ask about:
+- Is the development process description accurate?
+- Are the identified risks and mitigation strategies complete?
+- Is the schedule realistic?
+- Are there additional activities or reviews not captured?
+
+Offer to refine any section based on feedback.
+
+---
+
+**CONFIRMATION GATE**: Wait for the user to approve the document or request changes. If changes are requested, apply them and re-present for approval. Do not proceed to save until the user explicitly approves.

package/lib/bmad-extension-plugin/skills/mil498-sdp/prompts/06-save.md

@@ -0,0 +1,14 @@
+# Step 6 — Save
+
+Write the final document to:
+`{output_folder}/planning-artifacts/SDP.md`
+
+Confirm the file was saved and display a summary of:
+- Development phases and builds identified
+- Key milestones documented
+- Number of risks identified
+- Any sections marked "Not applicable"
+
+---
+
+**CONFIRMATION GATE**: Confirm to the user that the document has been saved successfully and present the summary. The workflow is now complete.