ma-agents 2.18.0 → 2.19.1

package/README.md

@@ -61,7 +61,7 @@ skills/code-review/
 | Joseph (MIL-STD-498) | `_bmad/skills/` | `generic` | `_bmad/bmm/agents/mil498.md` |
 | Antigravity | `_bmad/skills/` | `generic` | `_bmad/bmm/agents/antigravity.md` |
 
-## Available Skills (25)
+## Available Skills (27)
 
 | Skill ID | Domain | Description |
 | :--- | :--- | :--- |
@@ -72,6 +72,8 @@ skills/code-review/
 | `test-accompanied-development` | Quality | Enforces "test-alongside" policy for every public method |
 | `code-documentation` | Quality | Enforces PEP 257, Doxygen, JSDoc, and XML standards |
 | `skill-creator` | Meta | Guide for creating new skills to extend agent capabilities |
+| `document-revision-history` | Documentation | Manages revision history tables at the beginning of generated documents |
+| `ai-audit-trail` | Audit | Tracks AI agent session activity, time spent, and token usage |
 | **Security** | | |
 | `python-security-skill` | Python | OWASP Top 10 2025 aligned guardrails for Python |
 | `js-ts-security-skill` | JS/TS | Security verification for JS/TS codebases (OWASP aligned) |

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

@@ -40,6 +40,16 @@ This defines the required DID sections and content expectations for each paragra
 
 Write the document in {document_output_language}, populating each template section. The OCD should be written in language accessible to users and stakeholders, minimizing technical jargon.
 
+### 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 name, version, identifiers from PRD
 - **1.2 System overview**: Summarize the system purpose from the user's perspective

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

@@ -66,6 +66,16 @@ This defines the required DID sections and content expectations for each paragra
 
 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

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

@@ -46,6 +46,16 @@ This defines the required DID sections and content expectations for each paragra
 
 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

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

@@ -56,6 +56,16 @@ This defines the required DID sections and content expectations for each paragra
 
 Write the document in {document_output_language}, populating each template section. Each requirement shall be assigned a project-unique identifier, be stated so that an objective test can be defined for it, and be annotated with qualification method(s) and traceability to system requirements.
 
+### 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 software name, version, CSCI identifiers from the SSDD, PRD, and Architecture
 - **1.2 System overview**: Summarize purpose, nature, development history from PRD. Identify this CSCI's role within the system

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

@@ -88,6 +88,16 @@ Based on {user_name}'s answers:
 
 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**: Extract system name, version, and project-unique identifiers from PRD/Product Brief
 - **1.2 System overview**: Summarize system purpose, history, stakeholders, and operating sites from Product Brief and PRD

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

@@ -45,6 +45,16 @@ This defines the required DID sections and content expectations for each paragra
 
 Write the document in {document_output_language}, populating each template section. Keep requirements at the **system/subsystem level** — avoid low-level software implementation details. Each requirement shall be assigned a project-unique identifier, be stated so that an objective test can be defined for it, and be annotated with qualification method(s).
 
+### 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 name, version, identifiers from PRD/Product Brief
 - **1.2 System overview**: Summarize system purpose, nature, and stakeholders

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

@@ -56,6 +56,16 @@ This defines the required DID sections and content expectations for each paragra
 
 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

package/package.json

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

package/skills/ai-audit-trail/SKILL.md

@@ -0,0 +1,19 @@
+# AI Audit Trail
+
+At the end of every significant agent session, append an entry to `{project_root}/AiAudit.md`. If the file does not exist, create it with a `# AI Audit Trail` header first.
+
+## Entry Format
+
+```markdown
+| Date | Task | Tokens (est.) |
+|------|------|---------------|
+| YYYY-MM-DD | Brief task description | In: ~X / Out: ~Y |
+```
+
+## Rules
+
+- **Append only** — never delete or modify previous entries
+- **One row per session** — combine multiple tasks in the same session into one entry
+- **Estimate tokens** — round to nearest thousand, prefix with `~`. Write `N/A` if unknown
+- Write the entry as the **last action** before presenting results to the user
+- Skip trivial interactions (single-question answers, quick lookups)

package/skills/ai-audit-trail/skill.json

@@ -0,0 +1,20 @@
+{
+    "name": "AI Audit Trail",
+    "description": "Tracks AI agent session activity, time spent, and token usage in a project-level AiAudit.md log file.",
+    "version": "1.0.0",
+    "author": "Antigravity",
+    "tags": [
+        "audit",
+        "logging",
+        "time-tracking",
+        "tokens",
+        "accountability",
+        "project-management"
+    ],
+    "applies_when": [
+        "starting a new agent task or workflow",
+        "completing a document generation session",
+        "finishing any multi-step agent workflow"
+    ],
+    "always_load": true
+}

package/skills/document-revision-history/SKILL.md

@@ -0,0 +1,100 @@
+# Document Revision History
+
+Manage a revision history table at the beginning of every generated or updated document. This ensures traceability of changes across document versions.
+
+## Policy
+
+### 1. Revision History Table Required
+
+Every document generated or updated by the agent MUST include a **Revision History** table immediately after the document title (before the Table of Contents or Section 1).
+
+### 2. Table Format
+
+Use the following markdown table format:
+
+```markdown
+| Version | Date | Author | Changes |
+|---------|------|--------|---------|
+| 1.0 | 2026-03-02 | Agent (Claude) | Initial document generation |
+```
+
+### 3. Column Definitions
+
+| Column | Description |
+|--------|-------------|
+| **Version** | Document version number (e.g., 1.0, 1.1, 2.0). Use semantic versioning: major version for structural changes, minor for content updates |
+| **Date** | Date of the change in `YYYY-MM-DD` format |
+| **Author** | Who made the change — use `Agent (<model>)` for AI-generated content, or the user's name for user-directed changes |
+| **Changes** | Brief summary of ALL changes made in this version. One line per version — consolidate multiple changes into a single descriptive entry |
+
+### 4. Rules for New Documents
+
+When **generating a new document** for the first time:
+- Add the revision history table immediately after the document title
+- Set version to `1.0`
+- Set date to today's date
+- Set author to `Agent (<model>)` where `<model>` is the AI model name
+- Set changes to `Initial document generation`
+
+### 5. Rules for Updated Documents
+
+When **updating an existing document**:
+- Read the existing revision history table
+- Determine the new version number:
+  - **Minor increment** (e.g., 1.0 → 1.1): Content updates, corrections, additions to existing sections
+  - **Major increment** (e.g., 1.1 → 2.0): Structural changes, section reorganization, significant rewrites
+- Add a **single new row** summarizing ALL changes made in this update session
+- Do NOT create multiple rows for changes made in the same session — consolidate them into one line
+- Preserve all previous revision history entries
+
+### 6. Changes Column Guidelines
+
+Write concise but descriptive change summaries:
+
+**Good examples:**
+- `Added Sections 7-8 (impacts, analysis), expanded interface requirements to cover categories a-g`
+- `Updated capability requirements based on user feedback, added 3 new interfaces`
+- `Fixed traceability matrix, corrected section numbering`
+
+**Bad examples:**
+- `Updated document` (too vague)
+- `Changed section 3.2.1 requirement SRS-CAP-001 description from X to Y, then changed 3.2.2...` (too granular — summarize)
+
+### 7. Placement
+
+The revision history table MUST appear in this order within the document:
+
+```markdown
+# Document Title
+
+| Version | Date | Author | Changes |
+|---------|------|--------|---------|
+| 1.0 | 2026-03-02 | Agent (Claude) | Initial document generation |
+
+> MIL-STD-498 or other document metadata...
+
+## Table of Contents (if applicable)
+
+## 1. Scope
+...
+```
+
+### 8. Multi-Author Sessions
+
+If the user provides their name or the changes are user-directed corrections:
+- Use the user's name as author
+- If both the agent and user contribute in the same session, use `{user_name} / Agent (<model>)`
+
+## Example
+
+A document updated twice would have:
+
+```markdown
+# Software Requirements Specification (SRS)
+
+| Version | Date | Author | Changes |
+|---------|------|--------|---------|
+| 1.0 | 2026-03-01 | Agent (Claude) | Initial document generation from SSDD and PRD artifacts |
+| 1.1 | 2026-03-02 | Joseph / Agent (Claude) | Added 4 interface requirements per user feedback, corrected capability traceability to SSDD |
+| 2.0 | 2026-03-15 | Agent (Claude) | Major rewrite: restructured CSCI decomposition after SSDD v2.0, updated all requirement IDs |
+```

package/skills/document-revision-history/skill.json

@@ -0,0 +1,18 @@
+{
+    "name": "Document Revision History",
+    "description": "Manages a revision history table at the beginning of generated documents, tracking changes per version.",
+    "version": "1.0.0",
+    "author": "Antigravity",
+    "tags": [
+        "documentation",
+        "revision-history",
+        "version-tracking",
+        "mil-std-498",
+        "change-management"
+    ],
+    "applies_when": [
+        "generating or updating planning documents",
+        "creating specification or design documents",
+        "modifying existing markdown documents that have a revision history table"
+    ]
+}