artifact-metadata

Manage artifact metadata with versioning, ownership, and history tracking in JSON files.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/robit-man/transcribe-cli --skill artifact-metadata-robit-man
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: artifact-metadata
Source: https://github.com/robit-man/transcribe-cli/tree/main/.claude/skills/artifact-metadata
Command: npx skills add https://github.com/robit-man/transcribe-cli --skill artifact-metadata-robit-man

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management of all Software Development Lifecycle (SDLC) and marketing artifacts by providing a consistent way to track their metadata, versioning, ownership, and historical changes.

Core Features & Use Cases

  • Metadata Management: Creates and updates essential metadata like version, status, owner, and timestamps for any artifact.
  • History Tracking: Records changes to artifacts, including version bumps and review outcomes.
  • Use Case: Ensure that your critical architecture documents are always up-to-date, properly owned, and have a clear audit trail of all reviews and approvals.

Quick Start

Create metadata for the Software Architecture Document artifact.

Frequently Asked Questions about artifact-metadata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track version history and ownership for SDLC artifacts?

Artifact metadata tracking records version, status, owner, and timestamps in JSON files validated against a defined schema. It logs historical changes like version bumps and review outcomes, providing a consistent audit trail for SDLC and marketing artifacts.

What is the best way to manage artifact metadata for software architecture documents?

The best way to manage artifact metadata is by creating and updating JSON files validated against a defined schema. This tracks essential properties like version, status, and owner, ensuring critical architecture documents remain up-to-date with a clear audit trail.

Does this artifact versioning approach support querying historical review outcomes?

Yes, artifact versioning supports querying historical review outcomes by storing metadata in structured JSON files. You can query these validated records to retrieve past changes, ownership details, and approval histories for your SDLC artifacts.

How do I create and update artifact metadata using JSON?

To create and update artifact metadata using JSON, you define properties like version, status, and timestamps in structured files. The system validates these updates against a defined schema to ensure consistency before recording the changes in the artifact's history.

Can I integrate artifact metadata tracking with other SDLC orchestration tools?

Yes, artifact metadata tracking integrates with other skills for artifact orchestration and gate evaluation. This allows your JSON-based metadata management process to connect directly into broader software development lifecycle automation workflows.