ma-agents 2.22.2 → 3.0.0

package/lib/bmad-extension/skills/mil498-sss/template.md

@@ -0,0 +1,225 @@
+# 1. Scope.
+
+This section shall be divided into the following paragraphs.
+
+## 1.1 Identification.
+
+This paragraph shall contain a full identification of the system 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 to which this document applies. It shall describe the general nature of the system; 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 specification. This section shall also identify the source for all documents not available through normal Government stocking activities.
+
+# 3. Requirements.
+
+This section shall be divided into the following paragraphs to specify the system requirements, that is, those characteristics of the system that are conditions for its acceptance. Each requirement shall be assigned a project-unique identifier to support testing and traceability and shall be stated in such a way that an objective test can be defined for it. Each requirement shall be annotated with associated qualification method(s) (see section 4) and, for subsystems, traceability to system requirements (see section 5.a), if not provided in those sections. The degree of detail to be provided shall be guided by the following rule: Include those characteristics of the system that are conditions for system acceptance; defer to design descriptions those characteristics that the acquirer is willing to leave up to the developer. If there are no requirements in a given paragraph, the paragraph shall so state. If a given requirement fits into more than one paragraph, it may be stated once and referenced from the other paragraphs.
+
+## 3.1 Required states and modes.
+
+If the system is required to operate in more than one state or mode having requirements distinct from other states or modes, this paragraph shall identify and define each state and mode. Examples of states and modes include: idle, ready, active, post-use analysis, training, degraded, emergency, backup, wartime, peacetime. The distinction between states and modes is arbitrary. A system may be described in terms of states only, modes only, states within modes, modes within states, or any other scheme that is useful. If no states or modes are required, this paragraph shall so state, without the need to create artificial distinctions. If states and/or modes are required, each requirement or group of requirements in this specification shall be correlated to the states and modes. The correlation may be indicated by a table or other method in this paragraph, in an appendix referenced from this paragraph, or by annotation of the requirements in the paragraphs where they appear.
+
+## 3.2 System capability requirements.
+
+This paragraph shall be divided into subparagraphs to itemize the requirements associated with each capability of the system. A "capability" is defined as a group of related requirements. The word "capability" may be replaced with "function," "subject," "object," or other term useful for presenting the requirements.
+
+### 3.2.x (System capability).
+
+This paragraph shall identify a required system capability and shall itemize the requirements associated with the capability. If the capability can be more clearly specified by dividing it into constituent capabilities, the constituent capabilities shall be specified in subparagraphs. The requirements shall specify required behavior of the system and shall include applicable parameters, such as response times, throughput times, other timing constraints, sequencing, accuracy, capacities (how much/how many), priorities, continuous operation requirements, and allowable deviations based on operating conditions. The requirements shall include, as applicable, required behavior under unexpected, unallowed, or "out of bounds" conditions, requirements for error handling, and any provisions to be incorporated into the system to provide continuity of operations in the event of emergencies. Paragraph 3.3.x of this DID provides a list of topics to be considered when specifying requirements regarding inputs the system must accept and outputs it must produce.
+
+## 3.3 System external interface requirements.
+
+This paragraph shall be divided into subparagraphs to specify the requirements, if any, for the system's external interfaces. This paragraph may reference one or more Interface Requirements Specifications (IRSs) or other documents containing these requirements.
+
+### 3.3.1 Interface identification and diagrams.
+
+This paragraph shall identify the required external interfaces of the system. The identification of each interface shall include a project-unique identifier and shall designate 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 to depict the interfaces.
+
+### 3.3.x (Project-unique identifier of interface).
+
+This paragraph (beginning with 3.3.2) shall identify a system external interface by project-unique identifier, shall briefly identify the interfacing entities, and shall be divided into subparagraphs as needed to state the requirements imposed on the system to achieve the interface. Interface characteristics of the other entities involved in the interface shall be stated as assumptions or as "When [the entity not covered] does this, the system shall...," not as requirements on the other entities. This paragraph may reference other documents (such as data dictionaries, standards for communication protocols, and standards for user interfaces) in place of stating the information here. The requirements shall include the following, as applicable, presented in any order suited to the requirements, 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 that the system must assign the interface
+
+b. Requirements on the type of interface (such as real-time data transfer, storage-and-retrieval of data, etc.) to be implemented
+
+c. Required characteristics of individual data elements that the system must 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. Required characteristics of data element assemblies (records, messages, files, arrays, displays, reports, etc.) that the system must provide, store, send, access, receive, etc., such as:
+
+   1. Names/identifiers
+      a. Project-unique identifier
+      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. Required characteristics of communication methods that the system must 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. Required characteristics of protocols the system must 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 required characteristics, such as physical compatibility of the interfacing entities (dimensions, tolerances, loads, plug compatibility, etc.), voltages, etc.
+
+## 3.4 System internal interface requirements.
+
+This paragraph shall specify the requirements, if any, imposed on interfaces internal to the system. If all internal interfaces are left to the design or to requirement specifications for system components, this fact shall be so stated. If such requirements are to be imposed, paragraph 3.3 of this DID provides a list of topics to be considered.
+
+## 3.5 System internal data requirements.
+
+This paragraph shall specify the requirements, if any, imposed on data internal to the system. Included shall be requirements, if any, on databases and data files to be included in the system. If all decisions about internal data are left to the design or to requirements specifications for system components, this fact shall be so stated. If such requirements are to be imposed, paragraphs 3.3.x.c and 3.3.x.d of this DID provide a list of topics to be considered.
+
+## 3.6 Adaptation requirements.
+
+This paragraph shall specify the requirements, if any, concerning installation-dependent data that the system is required to provide (such as site-dependent latitude and longitude or site-dependent state tax codes) and operational parameters that the system is required to use that may vary according to operational needs (such as parameters indicating operation-dependent targeting constants or data recording).
+
+## 3.7 Safety requirements.
+
+This paragraph shall specify the system requirements, if any, concerned with preventing or minimizing unintended hazards to personnel, property, and the physical environment. Examples include restricting the use of dangerous materials; classifying explosives for purposes of shipping, handling, and storing; abort/escape provisions from enclosures; gas detection and warning devices; grounding of electrical systems; decontamination; and explosion proofing. This paragraph shall include the system requirements, if any, for nuclear components, including, as applicable, requirements for component design, prevention of inadvertent detonation, and compliance with nuclear safety rules.
+
+## 3.8 Security and privacy requirements.
+
+This paragraph shall specify the system requirements, if any, concerned with maintaining security and privacy. The requirements shall include, as applicable, the security/privacy environment in which the system must operate, the type and degree of security or privacy to be provided, the security/privacy risks the system must withstand, required safeguards to reduce those risks, the security/privacy policy that must be met, the security/privacy accountability the system must provide, and the criteria that must be met for security/privacy certification/accreditation.
+
+## 3.9 System environment requirements.
+
+This paragraph shall specify the requirements, if any, regarding the environment in which the system must operate. Examples for a software system are the computer hardware and operating system on which the software must run. (Additional requirements concerning computer resources are given in the next paragraph). Examples for a hardware-software system include the environmental conditions that the system must withstand during transportation, storage, and operation, such as conditions in the natural environment (wind, rain, temperature, geographic location), the induced environment (motion, shock, noise, electromagnetic radiation), and environments due to enemy action (explosions, radiation).
+
+## 3.10 Computer resource requirements.
+
+This paragraph shall be divided into the following subparagraphs. Depending upon the nature of the system, the computer resources covered in these subparagraphs may constitute the environment of the system (as for a software system) or components of the system (as for a hardware-software system).
+
+### 3.10.1 Computer hardware requirements.
+
+This paragraph shall specify the requirements, if any, regarding computer hardware that must be used by, or incorporated into, the system. The requirements shall include, as applicable, number of each type of equipment, type, size, capacity, and other required characteristics of processors, memory, input/output devices, auxiliary storage, communications/network equipment, and other required equipment.
+
+### 3.10.2 Computer hardware resource utilization requirements.
+
+This paragraph shall specify the requirements, if any, on the system's computer hardware resource utilization, such as maximum allowable use of processor capacity, memory capacity, input/output device capacity, auxiliary storage device capacity, and communications/network equipment capacity. The requirements (stated, for example, as percentages of the capacity of each computer hardware resource) shall include the conditions, if any, under which the resource utilization is to be measured.
+
+### 3.10.3 Computer software requirements.
+
+This paragraph shall specify the requirements, if any, regarding computer software that must be used by, or incorporated into, the system. Examples include operating systems, database management systems, communications/ network software, utility software, input and equipment simulators, test software, and manufacturing software. The correct nomenclature, version, and documentation references of each such software item shall be provided.
+
+### 3.10.4 Computer communications requirements.
+
+This paragraph shall specify the additional requirements, if any, concerning the computer communications that must be used by, or incorporated into, the system. Examples include geographic locations to be linked; configuration and network topology; transmission techniques; data transfer rates; gateways; required system use times; type and volume of data to be transmitted/received; time boundaries for transmission/reception/response; peak volumes of data; and diagnostic features.
+
+## 3.11 System quality factors.
+
+This paragraph shall specify the requirements, if any, pertaining to system quality factors. Examples include quantitative requirements concerning system functionality (the ability to perform all required functions), reliability (the ability to perform with correct, consistent results -- such as mean time between failure for equipment), maintainability (the ability to be easily serviced, repaired, or corrected), availability (the ability to be accessed and operated when needed), flexibility (the ability to be easily adapted to changing requirements), portability of software (the ability to be easily modified for a new environment), reusability (the ability to be used in multiple applications), testability (the ability to be easily and thoroughly tested), usability (the ability to be easily learned and used), and other attributes.
+
+## 3.12 Design and construction constraints.
+
+This paragraph shall specify the requirements, if any, that constrain the design and construction of the system. For hardware-software systems, this paragraph shall include the physical requirements imposed on the system. These requirements may be specified by reference to appropriate commercial or military standards and specifications. Examples include requirements concerning:
+
+a. Use of a particular system architecture or requirements on the architecture, such as required subsystems; use of standard, military, or existing components; or use of Government/acquirer-furnished property (equipment, information, or software)
+
+b. Use of particular design or construction standards; use of particular data standards; use of a particular programming language; workmanship requirements and production techniques
+
+c. Physical characteristics of the system (such as weight limits, dimensional limits, color, protective coatings); interchangeability of parts; ability to be transported from one location to another; ability to be carried or set up by one, or a given number of, persons
+
+d. Materials that can and cannot be used; requirements on the handling of toxic materials; limits on the electromagnetic radiation that the system is permitted to generate
+
+e. Use of nameplates, part marking, serial and lot number marking, and other identifying markings
+
+f. Flexibility and expandability that must be provided to support anticipated areas of growth or changes in technology, threat, or mission
+
+## 3.13 Personnel-related requirements.
+
+This paragraph shall specify the system requirements, if any, included to accommodate the number, skill levels, duty cycles, training needs, or other information about the personnel who will use or support the system. Examples include requirements for the number of work stations to be provided and for built-in help and training features. Also included shall be the human factors engineering requirements, if any, imposed on the system. These requirements shall include, as applicable, considerations for the capabilities and limitations of humans, foreseeable human errors under both normal and extreme conditions, and specific areas where the effects of human error would be particularly serious. Examples include requirements for adjustable-height work stations, color and duration of error messages, physical placement of critical indicators or buttons, and use of auditory signals.
+
+## 3.14 Training-related requirements.
+
+This paragraph shall specify the system requirements, if any, pertaining to training. Examples include training devices and training materials to be included in the system.
+
+## 3.15 Logistics-related requirements.
+
+This paragraph shall specify the system requirements, if any, concerned with logistics considerations. These considerations may include: system maintenance, software support, system transportation modes, supply-system requirements, impact on existing facilities, and impact on existing equipment.
+
+## 3.16 Other requirements.
+
+This paragraph shall specify additional system requirements, if any, not covered in the previous paragraphs. Examples include requirements for system documentation, such as specifications, drawings, technical manuals, test plans and procedures, and installation instruction data, if not covered in other contractual documents.
+
+## 3.17 Packaging requirements.
+
+This section shall specify the requirements, if any, for packaging, labeling, and handling the system and its components for delivery. Applicable military specifications and standards may be referenced if appropriate.
+
+## 3.18 Precedence and criticality of requirements.
+
+This paragraph shall specify, if applicable, the order of precedence, criticality, or assigned weights indicating the relative importance of the requirements in this specification. Examples include identifying those requirements deemed critical to safety, to security, or to privacy for purposes of singling them out for special treatment. If all requirements have equal weight, this paragraph shall so state.
+
+# 4. Qualification provisions.
+
+This section shall define a set of qualification methods and shall specify for each requirement in Section 3 the method(s) to be used to ensure that the requirement has been met. A table may be used to present this information, or each requirement in Section 3 may be annotated with the method(s) to be used. Qualification methods may include:
+
+a. Demonstration: The operation of the system, or a part of the system, that relies on observable functional operation not requiring the use of instrumentation, special test equipment, or subsequent analysis.
+
+b. Test: The operation of the system, or a part of the system, using instrumentation or other special test equipment to collect data for later analysis.
+
+c. Analysis: The processing of accumulated data obtained from other qualification methods. Examples are reduction, interpolation, or extrapolation of test results.
+
+d. Inspection: The visual examination of system components, documentation, etc.
+
+e. Special qualification methods. Any special qualification methods for the system, such as special tools, techniques, procedures, facilities, acceptance limits, use of standard samples, preproduction or periodic production samples, pilot models, or pilot lots.
+
+# 5. Requirements traceability.
+
+For system-level specifications, this paragraph does not apply. For subsystem-level specifications, this paragraph shall contain:
+
+a. Traceability from each subsystem requirement in this specification to the system requirements it addresses. (Alternatively, this traceability may be provided by annotating each requirement in Section 3.)
+
+   Note: Each level of system refinement may result in requirements not directly traceable to higher-level requirements. For example, a system architectural design that creates two subsystems may result in requirements about how the subsystems will interface, even though these interfaces are not covered in system requirements. Such requirements may be traced to a general requirement such as "system implementation" or to the system design decisions that resulted in their generation.
+
+b. Traceability from each system requirement that has been allocated to the subsystem covered by this specification to the subsystem requirements that address it. All system requirements allocated to the subsystem shall be accounted for. Those that trace to subsystem requirements contained in Interface Requirements Specifications (IRSs) shall reference those IRSs.
+
+# 6. 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/skills/mil498-std/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: mil498-std
+description: Generate MIL-STD-498 Software Test Description (STD)
+type: complex-workflow
+triggers:
+  - "generate STD"
+  - "create software test description"
+---
+
+# MIL-498: Software Test Description (STD)
+
+> MIL-STD-498 Data Item Description: DI-IPSC-81439
+
+## Workflow
+
+This workflow generates a MIL-STD-498 STD document through progressive steps.
+The STD defines the test preparations, test cases, and test procedures for software qualification testing.
+
+### 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/skills/mil498-std/bmad-skill-manifest.yaml

@@ -0,0 +1,5 @@
+type: skill
+name: mil498-std
+module: ma-skills
+description: Generate MIL-STD-498 Software Test Description (STD)
+version: "1.0.0"

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

@@ -0,0 +1,42 @@
+# 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.
+
+## Document Dependencies
+
+The STD defines test descriptions that verify requirements specified in the SRS. It should be generated after both the SSDD and the SRS for the CSCI being tested.
+
+| Predecessor | Relationship | Search Pattern |
+|-------------|-------------|----------------|
+| SRS (Software Requirements Specification) | **Required** — provides the requirements that tests must verify | `**/SRS.md`, `**/SRS-*.md` |
+| SSDD (System/Subsystem Design Description) | **Required** — provides system context and CSCI decomposition | `**/SSDD.md` |
+| SDD (Software Design Description) | Recommended — provides design details useful for test planning | `**/SDD.md`, `**/SDD-*.md` |
+
+If the SRS has NOT been generated yet, **alert {user_name}**: "The SRS has not been generated yet. The STD needs the SRS to know which requirements must be verified by tests. Would you like to proceed without the SRS, or generate the SRS first?"
+
+If the SSDD has NOT been generated yet, **alert {user_name}**: "The SSDD has not been generated yet. The STD benefits from the system design context in the SSDD. Would you like to proceed without it, or generate the SSDD first?"
+
+If predecessor documents exist, they MUST be loaded and used as primary inputs. Test cases MUST trace back to specific SRS requirements.
+
+## CSCI/System Scoping
+
+Ask {user_name}: **"Is this STD for CSCI-level testing or system-level testing? If CSCI-level, which CSCI?"**
+
+- For CSCI-level testing: requirements come from the CSCI's SRS
+- For system-level testing: requirements come from the SSS
+
+If the SSDD exists, present the list of CSCIs and ask the user to select scope.
+
+---
+
+**CONFIRMATION GATE**: Present the list of discovered artifacts and the selected test scope to the user. Wait for the user to confirm before proceeding to the next step.

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

@@ -0,0 +1,10 @@
+# Step 2 — Load Template
+
+Read the STD 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/skills/mil498-std/prompts/03-generate-document.md

@@ -0,0 +1,117 @@
+# Step 3 — Generate Document
+
+Write the document in {document_output_language}, populating each template section. **Important**: Safety precautions (marked by WARNING or CAUTION) and security/privacy considerations shall be included as applicable throughout Sections 3 and 4.
+
+## 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 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 with number, title, revision, and date
+
+## Section 3: Test preparations
+
+Organize as 3.x subsections, one per test. For each test (3.x), provide a brief description and the following:
+
+- **3.x.1 Hardware preparation**: Procedures to prepare hardware for the test:
+  - **a.** Specific hardware to be used, identified by name and number
+  - **b.** Switch settings and cabling necessary to connect the hardware
+  - **c.** Diagrams showing hardware, interconnecting control, and data paths
+  - **d.** Step-by-step instructions for placing hardware in a state of readiness
+- **3.x.2 Software preparation**: Procedures to prepare software for the test:
+  - **a.** Specific software to be used in the test
+  - **b.** Storage medium of the item(s) under test
+  - **c.** Storage medium of related software (simulators, test drivers, databases)
+  - **d.** Instructions for loading software, including required sequence
+  - **e.** Instructions for software initialization common to more than one test case
+- **3.x.3 Other pre-test preparations**: Any other personnel actions, preparations, or procedures necessary (test data setup, user accounts, external service mocks, environment variables)
+
+When information duplicates another test's preparation, reference it rather than repeating it.
+
+## Section 4: Test descriptions
+
+Organize as a **two-level hierarchy**: 4.x per test, then 4.x.y per test case within each test. Group test cases by capability/feature (mapping to Epics) for clarity.
+
+For each test (4.x), identify the test by project-unique identifier. Then for each test case (4.x.y), provide:
+
+- **4.x.y.1 Requirements addressed**: Identify the CSCI or system requirements addressed by this test case. Reference specific SRS requirement IDs (e.g., SRS-CAP-001). (Alternatively, this traceability may be provided in Section 5.a.)
+
+- **4.x.y.2 Prerequisite conditions**: Conditions that must be established prior to the test case:
+  - **a.** Hardware and software configuration
+  - **b.** Flags, initial breakpoints, pointers, control parameters, or initial data to be set/reset
+  - **c.** Preset hardware conditions or electrical states
+  - **d.** Initial conditions for timing measurements
+  - **e.** Conditioning of the simulated environment
+  - **f.** Other special conditions peculiar to the test case
+
+- **4.x.y.3 Test inputs**: Test inputs necessary for the test case:
+  - **a.** Name, purpose, and description (range of values, accuracy) of each test input
+  - **b.** Source of the test input and method for selecting it
+  - **c.** Whether the test input is real or simulated
+  - **d.** Time or event sequence of test input
+  - **e.** How input data will be controlled to:
+    1. Test with minimum/reasonable number of data types and values
+    2. Exercise with a range of valid data (overload, saturation, worst-case)
+    3. Exercise with invalid data types and values (error handling)
+    4. Permit retesting if necessary
+
+- **4.x.y.4 Expected test results**: All expected results — both intermediate and final results
+
+- **4.x.y.5 Criteria for evaluating results**: Criteria for intermediate and final results:
+  - **a.** Range or accuracy over which output can vary and still be acceptable
+  - **b.** Minimum number of input/output combinations that constitute acceptable results
+  - **c.** Maximum/minimum allowable test duration (time or number of events)
+  - **d.** Maximum number of interrupts, halts, or system breaks that may occur
+  - **e.** Allowable severity of processing errors
+  - **f.** Conditions under which the result is inconclusive and retesting is needed
+  - **g.** Conditions indicating irregularities in input data, test database, or procedures
+  - **h.** Allowable indications of control, status, and results readiness for next test case
+  - **i.** Additional criteria not covered above
+
+- **4.x.y.6 Test procedure**: Defined as individually numbered steps in sequential order:
+  - **a.** Test operator actions and equipment operation for each step, including commands to:
+    1. Initiate the test case and apply test inputs
+    2. Inspect test conditions
+    3. Perform interim evaluations of test results
+    4. Record data
+    5. Halt or interrupt the test case
+    6. Request data dumps or other aids
+    7. Modify the database/data files
+    8. Repeat the test case if unsuccessful
+    9. Apply alternate modes as required
+    10. Terminate the test case
+  - **b.** Expected result and evaluation criteria for each step
+  - **c.** If addressing multiple requirements, which steps address which requirements
+  - **d.** Actions to follow in event of program stop or error (recording critical data, halting time-sensitive software, collecting records)
+  - **e.** Procedures for reducing and analyzing test results (detect output, identify media/location, evaluate for continuation, evaluate against required output)
+
+- **4.x.y.7 Assumptions and constraints**: Assumptions made and constraints imposed (limitations on timing, interfaces, equipment, personnel, database). If waivers/exceptions to limits are approved, address their effects.
+
+## Section 5: Requirements traceability
+- **5.a**: Map each test case to the system or CSCI requirements it addresses. If a test case addresses multiple requirements, indicate which test procedure steps address which requirements.
+- **5.b**: Map each requirement covered by this STD to the test case(s) that address it. For CSCI testing, trace from each SRS requirement. For system testing, trace from each SSS requirement. Indicate specific test procedure steps where applicable.
+- Ensure every requirement has at least one associated test case. Identify any requirements that cannot be tested and explain why.
+
+## Section 6: Notes
+- Alphabetical listing of all acronyms, abbreviations, and their meanings
+- Glossary of test terminology
+- References to test automation frameworks or tools used
+
+## Appendix A
+- Test procedures may be included as an appendix for convenience in document maintenance
+- Include any supplementary material (test data sets, detailed configurations)
+
+---
+
+**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/skills/mil498-std/prompts/04-validate.md

@@ -0,0 +1,15 @@
+# Step 4 — Validate
+
+Before presenting to the user, verify:
+- All template sections (1-6 and Appendix A) are populated or marked "Not applicable" with justification
+- Test hierarchy is preserved: 4.x (test) -> 4.x.y (test case) -> 4.x.y.1-7 (details)
+- Every test case has all seven sub-items (4.x.y.1 through 4.x.y.7)
+- Every test case has a unique identifier and clear pass/fail criteria
+- Requirements traceability is complete — every SRS/SSS requirement has at least one test case
+- Test procedures are detailed enough to be repeatable
+- Safety precautions and security considerations are included where applicable
+- 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/skills/mil498-std/prompts/05-review.md

@@ -0,0 +1,15 @@
+# Step 5 — Review
+
+Present the complete document to {user_name} for review.
+Highlight any requirements without test coverage.
+Specifically ask about:
+- Are the test preparations complete for the target environment?
+- Are the evaluation criteria (4.x.y.5) realistic and measurable?
+- Are there additional test cases needed for edge cases or error scenarios?
+- Are the test procedures detailed enough to be executed by someone unfamiliar with the system?
+
+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/skills/mil498-std/prompts/06-save.md

@@ -0,0 +1,15 @@
+# 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 tests (4.x level)
+- Total number of test cases (4.x.y level)
+- Requirements coverage percentage
+- Any untestable requirements 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.