ma-agents 2.16.1 → 2.16.3

package/.agent/workflows/bmad-bmm-quick-spec.md

@@ -1,6 +0,0 @@
----
-name: 'quick-spec'
-description: 'Very quick process to create implementation-ready quick specs for small changes or features. Use when the user says "create a quick spec" or "generate a quick tech spec"'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md, READ its entire contents and follow its directions exactly!

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

@@ -1,14 +0,0 @@
----
-name: 'retrospective'
-description: 'Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"'
----
-
-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/retrospective/workflow.yaml
-3. Pass the yaml path {project-root}/_bmad/bmm/workflows/4-implementation/retrospective/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-sprint-planning.md

@@ -1,14 +0,0 @@
----
-name: 'sprint-planning'
-description: 'Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"'
----
-
-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/sprint-planning/workflow.yaml
-3. Pass the yaml path {project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/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-sprint-status.md

@@ -1,14 +0,0 @@
----
-name: 'sprint-status'
-description: 'Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"'
----
-
-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/sprint-status/workflow.yaml
-3. Pass the yaml path {project-root}/_bmad/bmm/workflows/4-implementation/sprint-status/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-technical-research.md

@@ -1,6 +0,0 @@
----
-name: 'technical-research'
-description: 'Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md, READ its entire contents and follow its directions exactly!

package/.agent/workflows/bmad-bmm-validate-prd.md

@@ -1,6 +0,0 @@
----
-name: 'validate-prd'
-description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md, READ its entire contents and follow its directions exactly!

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

@@ -1,6 +0,0 @@
----
-name: 'brainstorming'
-description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/core/workflows/brainstorming/workflow.md, READ its entire contents and follow its directions exactly!

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

@@ -1,14 +0,0 @@
----
-name: 'design-thinking'
-description: 'Guide human-centered design processes using empathy-driven methodologies. Use when the user says "lets run design thinking" or "I want to apply design thinking"'
----
-
-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/cis/workflows/design-thinking/workflow.yaml
-3. Pass the yaml path {project-root}/_bmad/cis/workflows/design-thinking/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-cis-innovation-strategy.md

@@ -1,14 +0,0 @@
----
-name: 'innovation-strategy'
-description: 'Identify disruption opportunities and architect business model innovation. Use when the user says "lets create an innovation strategy" or "I want to find disruption opportunities"'
----
-
-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/cis/workflows/innovation-strategy/workflow.yaml
-3. Pass the yaml path {project-root}/_bmad/cis/workflows/innovation-strategy/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-cis-problem-solving.md

@@ -1,14 +0,0 @@
----
-name: 'problem-solving'
-description: 'Apply systematic problem-solving methodologies to complex challenges. Use when the user says "guide me through structured problem solving" or "I want to crack this challenge with guided problem solving techniques"'
----
-
-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/cis/workflows/problem-solving/workflow.yaml
-3. Pass the yaml path {project-root}/_bmad/cis/workflows/problem-solving/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-cis-storytelling.md

@@ -1,14 +0,0 @@
----
-name: 'storytelling'
-description: 'Craft compelling narratives using story frameworks. Use when the user says "help me with storytelling" or "I want to create a narrative through storytelling"'
----
-
-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/cis/workflows/storytelling/workflow.yaml
-3. Pass the yaml path {project-root}/_bmad/cis/workflows/storytelling/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-editorial-review-prose.md

@@ -1,10 +0,0 @@
----
-name: 'editorial-review-prose'
-description: 'Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose'
----
-
-# editorial-review-prose
-
-Read the entire task file at: {project-root}/_bmad/core/tasks/editorial-review-prose.xml
-
-Follow all instructions in the task file exactly as written.

package/.agent/workflows/bmad-editorial-review-structure.md

@@ -1,10 +0,0 @@
----
-name: 'editorial-review-structure'
-description: 'Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure'
----
-
-# editorial-review-structure
-
-Read the entire task file at: {project-root}/_bmad/core/tasks/editorial-review-structure.xml
-
-Follow all instructions in the task file exactly as written.

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

@@ -1,10 +0,0 @@
----
-name: 'help'
-description: 'Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now'
----
-
-# help
-
-Read the entire task file at: {project-root}/_bmad/core/tasks/help.md
-
-Follow all instructions in the task file exactly as written.

package/.agent/workflows/bmad-index-docs.md

@@ -1,10 +0,0 @@
----
-name: 'index-docs'
-description: 'Generates or updates an index.md to reference all docs in the folder. Use if user requests to create or update an index of all files in a specific folder'
----
-
-# index-docs
-
-Read the entire task file at: {project-root}/_bmad/core/tasks/index-docs.xml
-
-Follow all instructions in the task file exactly as written.

package/.agent/workflows/bmad-party-mode.md

@@ -1,6 +0,0 @@
----
-name: 'party-mode'
-description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations. Use when user requests party mode.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/core/workflows/party-mode/workflow.md, READ its entire contents and follow its directions exactly!

package/.agent/workflows/bmad-review-adversarial-general.md

@@ -1,10 +0,0 @@
----
-name: 'review-adversarial-general'
-description: 'Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something'
----
-
-# review-adversarial-general
-
-Read the entire task file at: {project-root}/_bmad/core/tasks/review-adversarial-general.xml
-
-Follow all instructions in the task file exactly as written.

package/.agent/workflows/bmad-review-edge-case-hunter.md

@@ -1,10 +0,0 @@
----
-name: 'review-edge-case-hunter'
-description: 'Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven.'
----
-
-# review-edge-case-hunter
-
-Read the entire task file at: {project-root}/_bmad/core/tasks/review-edge-case-hunter.xml
-
-Follow all instructions in the task file exactly as written.

package/.agent/workflows/bmad-shard-doc.md

@@ -1,10 +0,0 @@
----
-name: 'shard-doc'
-description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document'
----
-
-# shard-doc
-
-Read the entire task file at: {project-root}/_bmad/core/tasks/shard-doc.xml
-
-Follow all instructions in the task file exactly as written.

package/.antigravity/antigravity.md

@@ -1,14 +0,0 @@
-
-<!-- MA-AGENTS-START -->
-# AI Agent Skills - Planning Instruction
-
-You have access to a library of skills in your skills directory. Before starting any task:
-
-1. Read the skill manifest at skills/MANIFEST.yaml
-2. Based on the task description, select which skills are relevant
-3. Read only the selected skill files
-4. Then proceed with the task
-
-Always load skills marked with always_load: true.
-Do not load skills that are not relevant to the current task.
-<!-- MA-AGENTS-END -->

package/.antigravity/skills/.ma-agents.json

@@ -1,14 +0,0 @@
-{
-  "manifestVersion": "1.0.0",
-  "agent": "antigravity",
-  "scope": "project",
-  "skills": {
-    "docker-image-signing": {
-      "version": "1.0.0",
-      "installedAt": "2026-03-01T10:05:53.821Z",
-      "updatedAt": "2026-03-01T10:05:53.821Z",
-      "installerVersion": "2.10.0",
-      "agentVersion": "1.0.0"
-    }
-  }
-}

package/.antigravity/skills/MANIFEST.yaml

@@ -1,7 +0,0 @@
-# skills/MANIFEST.yaml
-
-skills:
-  - id: docker-image-signing
-    file: skills/docker-image-signing/SKILL.md
-    description: Automates the signing of Docker images using certificates and Cosign/Notary.
-

package/.antigravity/skills/docker-image-signing/SKILL.md

@@ -1,28 +0,0 @@
----
-name: Docker Image Signing
-description: Automates the signing of Docker images using certificates and Cosign/Notary.
----
-# Docker Image Signing
-
-## Purpose
-Ensure the integrity and authenticity of Docker images by signing them with a cryptographic key/certificate. This prevents unauthorized image substitution and ensures only trusted images are deployed.
-
-## Instructions
-1.  **Tool Selection**: Use `cosign` (recommended) or `notary`.
-2.  **Environment Check**: Verify that the signing tool and Docker/Podman are installed.
-3.  **Signing Process**:
-    - Load the provided certificate/key.
-    - Run the signing command against the target image (using its SHA256 digest for immutability).
-4.  **Verification**: Always run a verification check immediately after signing.
-
-## Rules
-- NEVER sign images by tag alone; use the immutable digest (e.g., `image@sha256:...`).
-- Private keys must be handled as secrets and never stored in the clear.
-- Ensure the certificate provided is valid and not expired.
-
-## Usage
-Run the provided script in `scripts/sign-image.sh` with:
-- `IMAGE`: The image reference with digest.
-- `CERT`: Path to the certificate file.
-- `KEY`: Path to the private key file.
-- `PASSPHRASE`: (Optional) Key passphrase.

package/.antigravity/skills/docker-image-signing/scripts/sign-image.sh

@@ -1,33 +0,0 @@
-#!/bin/bash
-# sign-image.sh - Part of ma-agents docker-image-signing skill
-
-IMAGE=$1
-CERT=$2
-KEY=$3
-PASSPHRASE=$4
-
-if [ -z "$IMAGE" ] || [ -z "$CERT" ] || [ -z "$KEY" ]; then
-    echo "Usage: $0 <image_digest> <cert_file> <key_file> [passphrase]"
-    exit 1
-fi
-
-echo "Signing image: $IMAGE"
-
-# Check for cosign
-if command -v cosign &> /dev/null; then
-    echo "Using Cosign for signing..."
-    if [ -n "$PASSPHRASE" ]; then
-        export COSIGN_PASSWORD=$PASSPHRASE
-    fi
-    cosign sign --key "$KEY" --cert "$CERT" "$IMAGE"
-else
-    echo "Error: cosign not found. Please install cosign to use this skill."
-    exit 1
-fi
-
-if [ $? -eq 0 ]; then
-    echo "Successfully signed $IMAGE"
-else
-    echo "Failed to sign $IMAGE"
-    exit 1
-fi

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

@@ -1,17 +0,0 @@
-# bmad-mil-generate-ocd.md
-# Generate Operational Concept Description (OCD)
-
-This workflow generates a MIL-STD-498 OCD document to describe the system from a user's perspective.
-
-## Instructions
-1.  **Load Template**: Read the OCD template from `{project-root}/_bmad/bmm/templates/mil498/OCD.md`.
-2.  **Gather Context**:
-    - Load the **PRD** for user needs and business goals.
-    - Load the **Architecture** for system context.
-    - Load **UX Designs** for user workflows and interactions.
-3.  **Map Concept**:
-    - **Section 3 (Current system or situation)**: Describe the problem being solved (from PRD).
-    - **Section 4 (Nature of proposed changes)**: Overview of the solution.
-    - **Section 5 (Operational concept)**: Describe user roles, operational scenarios, and key workflows (from UX/Stories).
-4.  **Clarity**: Ensure the document is written in a way that is easily understood by system users and stakeholders.
-5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `OCD.md`.

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

@@ -1,18 +0,0 @@
-# bmad-mil-generate-sdd.md
-# Generate Software Design Description (SDD)
-
-This workflow generates a MIL-STD-498 SDD document (using the SSDD template) based on the system design and implementation details.
-
-## Instructions
-1.  **Load Template**: Read the SSDD template from `{project-root}/_bmad/bmm/templates/mil498/SSDD.md`.
-2.  **Gather Context**:
-    - Load the **Architecture** document for high-level design and component structure.
-    - Load **UX Designs** for detailed user interface design.
-    - Load **Epics and Stories** to understand detailed behavior and logic.
-    - Load the **PRD** for design constraints.
-3.  **Map Design**:
-    - **Section 3 (CSCI-wide design decisions)**: Describe the architectural patterns and technology stack.
-    - **Section 4 (CSCI architectural design)**: Define components, their interfaces, and data flow.
-    - **Section 5 (CSCI detailed design)**: Map Stories to detailed logic and internal data structures.
-4.  **Consistency**: Ensure the design matches the requirements specified in the SRS.
-5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SDD.md`.

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

@@ -1,17 +0,0 @@
-# bmad-mil-generate-sdp.md
-# Generate Software Development Plan (SDP)
-
-This workflow generates a MIL-STD-498 SDP document to outline the development approach and project management artifacts.
-
-## Instructions
-1.  **Load Template**: Read the SDP template from `{project-root}/_bmad/bmm/templates/mil498/SDP.md`.
-2.  **Gather Context**:
-    - Load the **Product Brief** for project vision and objectives.
-    - Load the **PRD** for scope and constraints.
-    - Identify any **Planning Documents** or schedules.
-3.  **Map Plan**:
-    - **Section 3 (Project organization and resources)**: Define roles and resources based on the Product Brief.
-    - **Section 4 (Software development process)**: Describe the BMAD-METHOD lifecycle used.
-    - **Section 5 (Software development activities)**: Detail the tasks, schedules, and milestones.
-4.  **Consistency**: Ensure the plan reflects the actual development methodology being followed.
-5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SDP.md`.

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

@@ -1,19 +0,0 @@
-# bmad-mil-generate-srs.md
-# Generate Software Requirements Specification (SRS)
-
-This workflow generates a MIL-STD-498 SRS document by extracting requirements from BMAD-METHOD records.
-
-## Instructions
-1.  **Load Template**: Read the SRS template from `{project-root}/_bmad/bmm/templates/mil498/SRS.md`.
-2.  **Gather Context**:
-    - Load the **PRD** to identify functional and non-functional requirements.
-    - Load the **Architecture** document to understand system boundaries and external interfaces.
-    - Load **UX Designs** to define user interface requirements.
-    - Load **Epics** to group related requirements into capabilities (Section 3.2).
-3.  **Map Requirements**:
-    - **Section 3.1 (States and Modes)**: Identify any operational modes from the PRD/Architecture.
-    - **Section 3.2 (CSCI Capability Requirements)**: Map Epics and leur related requirements to this section.
-    - **Section 3.3 (External Interface Requirements)**: Map Architecture interface definitions here.
-    - **Section 3.10 (Computer Resource Requirements)**: Extract hardware/software constraints from the Architecture document.
-4.  **Traceability**: Ensure each requirement has a unique CID and is traced to the original PRD entry.
-5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SRS.md`.

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

@@ -1,16 +0,0 @@
-# bmad-mil-generate-sss.md
-# Generate System/Subsystem Specification (SSS)
-
-This workflow generates a MIL-STD-498 SSS document for high-level system requirements.
-
-## Instructions
-1.  **Load Template**: Read the SSS template from `{project-root}/_bmad/bmm/templates/mil498/SSS.md`.
-2.  **Gather Context**:
-    - Load the **Product Brief** for high-level system identification and goals.
-    - Load the **PRD** for primary system requirements.
-3.  **Map Requirements**:
-    - **Section 3.2 (System capability requirements)**: Map high-level PRD features to system capabilities.
-    - **Section 3.3 (System external interface requirements)**: Map top-level interfaces.
-    - **Section 3.4 (System internal interface requirements)**: Map interfaces between major subsystems.
-4.  **High-Level Focus**: Keep requirements at the system/subsystem level, avoiding low-level software details.
-5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SSS.md`.

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

@@ -1,17 +0,0 @@
-# bmad-mil-generate-std.md
-# Generate Software Test Description (STD)
-
-This workflow generates a MIL-STD-498 STD document to define the test cases and procedures for software qualification.
-
-## Instructions
-1.  **Load Template**: Read the STD template from `{project-root}/_bmad/bmm/templates/mil498/STD.md`.
-2.  **Gather Context**:
-    - Load the **Architecture** for test environment details.
-    - Load **Epics and Stories** to identify test objectives and acceptance criteria.
-    - Load the **SRS** to link test cases to requirements (Traceability).
-3.  **Map Tests**:
-    - **Section 3 (Test preparations)**: Describe hardware/software needed for testing (from Architecture).
-    - **Section 4 (Test descriptions)**: Map Story acceptance criteria to specific test cases and procedures.
-    - **Section 5 (Requirements traceability)**: Link each test case to one or more SRS requirements.
-4.  **Verification**: Ensure all requirements in the SRS have at least one test case.
-5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `STD.md`.

package/mil498/OCD.md

@@ -1,169 +0,0 @@
-# 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 document. This section shall also identify the source for all documents not available through normal Government stocking activities.
-
-# 3. Current system or situation.
-
-This section shall be divided into the following paragraphs to describe the system or situation as it currently exists.
-
-## 3.1 Background, objectives, and scope.
-
-This paragraph shall describe the background, mission or objectives, and scope of the current system or situation.
-
-## 3.2 Operational policies and constraints.
-
-This paragraph shall describe any operational policies and constraints that apply to the current system or situation.
-
-## 3.3 Description of current system or situation.
-
-This paragraph shall provide a description of the current system or situation, identifying differences associated with different states or modes of operation (for example, regular, maintenance, training, degraded, emergency, alternative-site, 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 the system operates without states or modes, this paragraph shall so state, without the need to create artificial distinctions. The description shall include, as applicable:
-
-a. The operational environment and its characteristics
-
-b. Major system components and the interconnections among these components
-
-c. Interfaces to external systems or procedures
-
-d. Capabilities/functions of the current system
-
-e. Charts and accompanying descriptions depicting inputs, outputs, data flow, and manual and automated processes sufficient to understand the current system or situation from the user's point of view
-
-f. Performance characteristics, such as speed, throughput, volume, frequency
-
-g. Quality attributes, such as reliability, maintainability, availability, flexibility, portability, usability, efficiency
-
-h. Provisions for safety, security, privacy, and continuity of operations in emergencies
-
-## 3.4 Users or involved personnel.
-
-This paragraph shall describe the types of users of the system, or personnel involved in the current situation, including, as applicable, organizational structures, training/skills, responsibilities, activities, and interactions with one another.
-
-## 3.5 Support concept.
-
-This paragraph shall provide an overview of the support concept for the current system, including, as applicable to this document, support agency(ies); facilities; equipment; support software; repair/replacement criteria; maintenance levels and cycles; and storage, distribution, and supply methods.
-
-# 4. Justification for and nature of changes.
-
-This section shall be divided into the following paragraphs.
-
-## 4.1 Justification for change.
-
-This paragraph shall:
-
-a. Describe new or modified aspects of user needs, threats, missions, objectives, environments, interfaces, personnel or other factors that require a new or modified system
-
-b. Summarize deficiencies or limitations in the current system or situation that make it unable to respond to these factors
-
-## 4.2 Description of needed changes.
-
-This paragraph shall summarize new or modified capabilities/functions, processes, interfaces, or other changes needed to respond to the factors identified in 4.1.
-
-## 4.3 Priorities among the changes.
-
-This paragraph shall identify priorities among the needed changes. It shall, for example, identify each change as essential, desirable, or optional, and prioritize the desirable and optional changes.
-
-## 4.4 Changes considered but not included.
-
-This paragraph shall identify changes considered but not included in 4.2, and rationale for not including them.
-
-## 4.5 Assumptions and constraints.
-
-This paragraph shall identify any assumptions and constraints applicable to the changes identified in this section.
-
-# 5. Concept for a new or modified system.
-
-This section shall be divided into the following paragraphs to describe a new or modified system.
-
-## 5.1 Background, objectives, and scope.
-
-This paragraph shall describe the background, mission or objectives, and scope of the new or modified system.
-
-## 5.2 Operational policies and constraints.
-
-This paragraph shall describe any operational policies and constraints that apply to the new or modified system.
-
-## 5.3 Description of the new or modified system.
-
-This paragraph shall provide a description of the new or modified system, identifying differences associated with different states or modes of operation (for example, regular, maintenance, training, degraded, emergency, alternative-site, 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 the system operates without states or modes, this paragraph shall so state, without the need to create artificial distinctions. The description shall include, as applicable:
-
-a. The operational environment and its characteristics
-
-b. Major system components and the interconnections among these components
-
-c. Interfaces to external systems or procedures
-
-d. Capabilities/functions of the new or modified system
-
-e. Charts and accompanying descriptions depicting inputs, outputs, data flow, and manual and automated processes sufficient to understand the new or modified system or situation from the user's point of view
-
-f. Performance characteristics, such as speed, throughput, volume, frequency
-
-g. Quality attributes, such as reliability, maintainability, availability, flexibility, portability, usability, efficiency
-
-h. Provisions for safety, security, privacy, and continuity of operations in emergencies
-
-## 5.4 Users/affected personnel.
-
-This paragraph shall describe the types of users of the new or modified system, including, as applicable, organizational structures, training/skills, responsibilities, and interactions with one another.
-
-## 5.5 Support concept.
-
-This paragraph shall provide an overview of the support concept for the new or modified system, including, as applicable, support agency(ies); facilities; equipment; support software; repair/replacement criteria; maintenance levels and cycles; and storage, distribution, and supply methods.
-
-# 6. Operational scenarios.
-
-This section shall describe one or more operational scenarios that illustrate the role of the new or modified system, its interaction with users, its interface to other systems, and all states or modes identified for the system. The scenarios shall include events, actions, stimuli, information, interactions, etc., as applicable. Reference may be made to other media, such as videos, to provide part or all of this information.
-
-# 7. Summary of impacts.
-
-This section shall be divided into the following paragraphs.
-
-## 7.1 Operational impacts.
-
-This paragraph shall describe anticipated operational impacts on the user, acquirer, developer, and support agency(ies). These impacts may include changes in interfaces with computer operating centers; change in procedures; use of new data sources; changes in quantity, type, and timing of data to be input to the system; changes in data retention requirements; and new modes of operation based on peacetime, alert, wartime, or emergency conditions.
-
-## 7.2 Organizational impacts.
-
-This paragraph shall describe anticipated organizational impacts on the user, acquirer, developer, and support agency(ies). These impacts may include modification of responsibilities; addition or elimination of responsibilities or positions; need for training or retraining; and changes in number, skill levels, position identifiers, or location of personnel in various modes of operation.
-
-## 7.3 Impacts during development.
-
-This paragraph shall describe anticipated impacts on the user, acquirer, developer, and support agency(ies) during the development effort. These impacts may include meetings/discussions regarding the new system; development or modification of databases; training; parallel operation of the new and existing systems; impacts during testing of the new system; and other activities needed to aid or monitor development.
-
-# 8. Analysis of the proposed system.
-
-## 8.1 Summary of advantages.
-
-This paragraph shall provide a qualitative and quantitative summary of the advantages to be obtained from the new or modified system. This summary shall include new capabilities, enhanced capabilities, and improved performance, as applicable, and their relationship to deficiencies identified in 4.1.
-
-## 8.2 Summary of disadvantages/limitations.
-
-This paragraph shall provide a qualitative and quantitative summary of disadvantages or limitations of the new or modified system. These disadvantages and limitations shall include, as applicable, degraded or missing capabilities, degraded or less-than-desired performance, greater-than-desired use of computer hardware resources, undesirable operational impacts, conflicts with user assumptions, and other constraints.
-
-## 8.3 Alternatives and trade-offs considered.
-
-This paragraph shall identify and describe major alternatives considered to the system or its characteristics, the trade-offs among them, and rationale for the decisions reached.
-
-# 9. Notes.
-
-This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include 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/mil498/README.md

@@ -1,4 +0,0 @@
-MIL-STD-498 DIDs converted to HTML.
-
-For more information (what is it, why do you need it), see the article at [http://kkovacs.eu/free-project-management-template-mil-std-498]!
-