/artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle
Claude Code
$ npx -y skills add jmagly/aiwg --skill artifact-metadata --agent claude-code
Codex
$ npx skills add jmagly/aiwg --skill artifact-metadata -a codex -y
Cursor
$ npx skills add jmagly/aiwg --skill artifact-metadata -a cursor -y
Gemini CLI
$ npx skills add jmagly/aiwg --skill artifact-metadata -a gemini-cli -y
GitHub Copilot
$ npx skills add jmagly/aiwg --skill artifact-metadata -a github-copilot -y
OpenCode
$ npx skills add jmagly/aiwg --skill artifact-metadata -a opencode -y
Windsurf
$ npx skills add jmagly/aiwg --skill artifact-metadata -a windsurf -y
SKILL.md
artifact-metadata.SKILL.mdnamespace: aiwg
name: artifact-metadata
platforms: [all]
description: Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle
artifact-metadata
Manage artifact metadata, versioning, ownership, and history tracking.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "tag this artifact" → metadata tagging
- "classify [artifact]" → artifact metadata assignment
Purpose
This skill provides consistent metadata management for all SDLC and marketing artifacts. It tracks ownership, versioning, review history, and status across the artifact lifecycle.
Behavior
When triggered, this skill:
1. **Locates or creates metadata**:
- Check for existing `metadata.json` alongside artifact
- Create new metadata if none exists
- Validate against metadata schema
2. **Updates metadata fields**:
- Version (semantic versioning)
- Status (draft, review, baselined, deprecated)
- Owner (agent or user)
- Reviewers (list of reviewing agents)
- Timestamps (created, modified, baselined)
3. **Tracks history**:
- Version history with change summaries
- Review records with reviewer and outcome
- Approval records
4. **Validates relationships**:
- Parent/child artifact links
- Requirement traceability links
- Cross-references to related artifacts
Metadata Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"required": ["artifact_id", "name", "type", "version", "status", "owner"],
"properties": {
"artifact_id": {
"type": "string",
"description": "Unique identifier (e.g., SAD-001, UC-003)"
},
"name": {
"type": "string",
"description": "Human-readable artifact name"
},
"type": {
"type": "string",
"enum": ["requirements", "architecture", "test", "security", "deployment", "marketing", "report"]
},
"version": {
"type": "string",
"pattern": "^\\d+\\.\\d+\\.\\d+$",
"description": "Semantic version"
},
"status": {
"type": "string",
"enum": ["draft", "review", "approved", "baselined", "deprecated"]
},
"owner": {
"type": "string",
"description": "Primary owner (agent name or user)"
},
"created": {
"type": "string",
"format": "date-time"
},
"modified": {
"type": "string",
"format": "date-time"
},
"baselined": {
"type": "string",
"format": "date-time"
},
"reviewers": {
"type": "array",
"items": {"type": "string"}
},
"history": {
"type": "array",
"items": {
"type": "object",
"properties": {
"version": {"type": "string"},
"date": {"type": "string", "format": "date-time"},
"author": {"type": "string"},
"summary": {"type": "string"}
}
}
},
"reviews": {
"type": "array",
"items": {
"type": "object",
"properties": {
"reviewer": {"type": "string"},
"date": {"type": "string", "format": "date-time"},
"outcome": {"type": "string", "enum": ["approved", "conditional", "rejected"]},
"comments": {"type": "string"}
}
}
},
"traceability": {
"type": "object",
"properties": {
"requirements": {"type": "array", "items": {"type": "string"}},
"parent": {"type": "string"},
"children": {"type": "array", "items": {"type": "string"}}
}
},
"tags": {
"type": "array",
"items": {"type": "string"}
}
}
}Usage Examples
Create New Metadata
User: "Create metadata for the SAD"
Skill creates:
.aiwg/architecture/sad/metadata.json
{
"artifact_id": "SAD-001",
"name": "Software Architecture Document",
"type": "architecture",
"version": "0.1.0",
"status": "draft",
"owner": "architecture-designer",
"created": "2025-12-08T14:30:00Z",
"modified": "2025-12-08T14:30:00Z",
"reviewers": [],
"history": [],
"reviews": []
}Update Version After Changes
User: "Version the SAD to 1.0.0 with summary 'Initial baseline'"
Skill updates:
- version: "1.0.0"
- status: "baselined"
- baselined: "2025-12-08T16:45:00Z"
- history: [adds entry with version, date, summary]
Record Review
User: "Record security-architect review as approved"
Skill updates:
- reviews: [adds review record]
- reviewers: [adds "security-architect" if not present]
- modified: [updates timestamp]
Query Ownership
User: "Who owns the test plan?"
Skill responds:
"Test Plan (TP-001) is owned by test-architect.
Status: review
Version: 0.3.0
Last modified: 2025-12-07
Reviewers: security-auditor, requirements-analyst"
Status Lifecycle
draft → review → approved → baselined
↑ ↓
└── rejected (returns to draft)
baselined → deprecated (end of life)
Status Transitions
| From | To | Triggered By | |------|-----|-------------| | draft | review | Submit for review | | review | approved | All reviewers approve | | review | draft | Any reviewer rejects | | approved | baselined | Formal baseline action | | baselined | deprecated | Superseded or retired |
Version Conventions
- **0.x.x**: Draft versions (not baselined)
- **1.0.0**: First baseline
- **x.y.0**: Minor changes (compatible)
- **x.0.0**: Major changes (may break traceability)
Auto-Version Rules
| Change Type | Version Bump | |-------------|-------------| | Typo fix | patch (0.0.x) | | Section update | minor (0.x.0) | | Structure change | major (x.0.0) | | Initial baseline | 1.0.0 |
Artifact Type Conventions
| Type | ID Prefix | Location | |------|-----------|----------| | requirements | UC-, REQ-, NFR- | .aiwg/requirements/ | | architecture | SAD-, ADR-, API- | .aiwg/architecture/ | | test | TP-, TC-, TS- | .aiwg/testing/ | | security | TM-, SEC- | .aiwg/security/ |
Read more
namespace: aiwg name: artifact-metadata platforms: [all] description: Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle
artifact-metadata
Manage artifact metadata, versioning, ownership, and history tracking.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "tag this artifact" → metadata tagging
- "classify [artifact]" → artifact metadata assignment
Purpose
This skill provides consistent metadata management for all SDLC and marketing artifacts. It tracks ownership, versioning, review history, and status across the artifact lifecycle.
Behavior
When triggered, this skill:
1. **Locates or creates metadata**:
- Check for existing `metadata.json` alongside artifact
- Create new metadata if none exists
- Validate against metadata schema
2. **Updates metadata fields**:
- Version (semantic versioning)
- Status (draft, review, baselined, deprecated)
- Owner (agent or user)
- Reviewers (list of reviewing agents)
- Timestamps (created, modified, baselined)
3. **Tracks history**:
- Version history with change summaries
- Review records with reviewer and outcome
- Approval records
4. **Validates relationships**:
- Parent/child artifact links
- Requirement traceability links
- Cross-references to related artifacts
Metadata Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"required": ["artifact_id", "name", "type", "version", "status", "owner"],
"properties": {
"artifact_id": {
"type": "string",
"description": "Unique identifier (e.g., SAD-001, UC-003)"
},
"name": {
"type": "string",
"description": "Human-readable artifact name"
},
"type": {
"type": "string",
"enum": ["requirements", "architecture", "test", "security", "deployment", "marketing", "report"]
},
"version": {
"type": "string",
"pattern": "^\\d+\\.\\d+\\.\\d+$",
"description": "Semantic version"
},
"status": {
"type": "string",
"enum": ["draft", "review", "approved", "baselined", "deprecated"]
},
"owner": {
"type": "string",
"description": "Primary owner (agent name or user)"
},
"created": {
"type": "string",
"format": "date-time"
},
"modified": {
"type": "string",
"format": "date-time"
},
"baselined": {
"type": "string",
"format": "date-time"
},
"reviewers": {
"type": "array",
"items": {"type": "string"}
},
"history": {
"type": "array",
"items": {
"type": "object",
"properties": {
"version": {"type": "string"},
"date": {"type": "string", "format": "date-time"},
"author": {"type": "string"},
"summary": {"type": "string"}
}
}
},
"reviews": {
"type": "array",
"items": {
"type": "object",
"properties": {
"reviewer": {"type": "string"},
"date": {"type": "string", "format": "date-time"},
"outcome": {"type": "string", "enum": ["approved", "conditional", "rejected"]},
"comments": {"type": "string"}
}
}
},
"traceability": {
"type": "object",
"properties": {
"requirements": {"type": "array", "items": {"type": "string"}},
"parent": {"type": "string"},
"children": {"type": "array", "items": {"type": "string"}}
}
},
"tags": {
"type": "array",
"items": {"type": "string"}
}
}
}Usage Examples
Create New Metadata
User: "Create metadata for the SAD"
Skill creates:
.aiwg/architecture/sad/metadata.json
{
"artifact_id": "SAD-001",
"name": "Software Architecture Document",
"type": "architecture",
"version": "0.1.0",
"status": "draft",
"owner": "architecture-designer",
"created": "2025-12-08T14:30:00Z",
"modified": "2025-12-08T14:30:00Z",
"reviewers": [],
"history": [],
"reviews": []
}Update Version After Changes
User: "Version the SAD to 1.0.0 with summary 'Initial baseline'" Skill updates: - version: "1.0.0" - status: "baselined" - baselined: "2025-12-08T16:45:00Z" - history: [adds entry with version, date, summary]
Record Review
User: "Record security-architect review as approved" Skill updates: - reviews: [adds review record] - reviewers: [adds "security-architect" if not present] - modified: [updates timestamp]
Query Ownership
User: "Who owns the test plan?" Skill responds: "Test Plan (TP-001) is owned by test-architect. Status: review Version: 0.3.0 Last modified: 2025-12-07 Reviewers: security-auditor, requirements-analyst"
Status Lifecycle
draft → review → approved → baselined ↑ ↓ └── rejected (returns to draft) baselined → deprecated (end of life)
Status Transitions
| From | To | Triggered By | |------|-----|-------------| | draft | review | Submit for review | | review | approved | All reviewers approve | | review | draft | Any reviewer rejects | | approved | baselined | Formal baseline action | | baselined | deprecated | Superseded or retired |
Version Conventions
- **0.x.x**: Draft versions (not baselined)
- **1.0.0**: First baseline
- **x.y.0**: Minor changes (compatible)
- **x.0.0**: Major changes (may break traceability)
Auto-Version Rules
| Change Type | Version Bump | |-------------|-------------| | Typo fix | patch (0.0.x) | | Section update | minor (0.x.0) | | Structure change | major (x.0.0) | | Initial baseline | 1.0.0 |
Artifact Type Conventions
| Type | ID Prefix | Location | |------|-----------|----------| | requirements | UC-, REQ-, NFR- | .aiwg/requirements/ | | architecture | SAD-, ADR-, API- | .aiwg/architecture/ | | test | TP-, TC-, TS- | .aiwg/testing/ | | security | TM-, SEC- | .aiwg/security/ |
Reusable project context and specialist workflows for the AI tools you already use. Plan software, coordinate specialist reviews, prepare campaigns, investigate incidents, organize research, curate media, and maintain operational knowledge.
Other skills on aiwg.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about artifact-metadata.
- Which coding agents can use artifact-metadata?
- artifact-metadata installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

