auto-provenance

Generate W3C PROV-compliant provenance records for AIWG agent artifacts.

175|26|Updated Aug 14, 2025
One-click install
npx skills add https://github.com/jmagly/aiwg --skill auto-provenance-jmagly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-provenance
Source: https://github.com/jmagly/aiwg/tree/main/plugins/sdlc/skills/auto-provenance
Command: npx skills add https://github.com/jmagly/aiwg --skill auto-provenance-jmagly

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that every artifact created or modified by AIWG agents has a verifiable and auditable provenance record, preventing data loss and maintaining a clear chain of derivation.

Core Features & Use Cases

  • Automatic Record Generation: Creates W3C PROV-compliant provenance records for new or modified artifacts without manual agent intervention.
  • Derivation Tracking: Parses @-mentions in content to automatically establish relationships like @implements, @tests, and @depends.
  • Use Case: When an agent writes new code in src/, this skill automatically generates a provenance record detailing the agent, the code's content hash, and its derivation from previous artifacts, ensuring a complete audit trail.

Quick Start

Use the auto-provenance skill to track artifact creation and modification.

Frequently Asked Questions about auto-provenance

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

FAQPage Schema
How do I automatically generate W3C PROV-compliant provenance records for artifacts?

You can automatically generate W3C PROV-compliant provenance records by using a skill that tracks artifact creation and modification. It automatically outputs auditable provenance records detailing the agent, content hash, and derivation relationships.

What is the best way to track artifact derivation relationships without manual intervention?

The best way to track derivation relationships without manual intervention is by parsing @-mentions within content. This automatically establishes derivation links like @implements, @tests, and @depends between artifacts.

How does provenance tracking satisfy FAIR Principles and OAIS archival lifecycles?

Provenance tracking satisfies FAIR Principles and OAIS archival lifecycles by automatically generating verifiable W3C PROV-compliant records. This ensures a clear, auditable chain of derivation from requirements to implementation, preventing data loss.

Can I establish an auditable chain from requirements to implementation automatically?

Yes, you can establish an auditable chain from requirements to implementation automatically. By parsing @-mentions in content, the system tracks derivation relationships and generates provenance records detailing the agent and content hash.

When do I need automated provenance tracking for artifact modification?

You need automated provenance tracking for artifact modification when maintaining a verifiable audit trail in version control systems. It prevents data loss by ensuring every modified artifact has a provenance record detailing its derivation and content hash.