Auto-Provenance

To generate W3C PROV-compliant provenance records automatically, this Skill tracks artifacts created or modified by AI agents and saves the validated records to a designated location. It ensures an auditable chain of origin from requirements to implementation.

You can track derivation relationships by using @-mentions in your content. This Skill parses tags like @implements, @tests, @extends, and @depends to automatically establish and record the connections between your requirements and implementation.

Artifact provenance tracking records the origin and derivation history of files. You need it to maintain traceability and prevent the loss of development history when AI agents create or modify code, ensuring a clear auditable chain.

Yes, provenance tracking requires schema validation. This Skill validates generated provenance records against a defined schema before saving them, ensuring your artifact tracking data remains structurally accurate and compliant with W3C PROV standards.

Yes, you can establish an auditable chain automatically. When a new feature is coded, this Skill generates a provenance record linking the code to the requirement it implements and the associated tests through parsed @-mentions.

A limitation of using @-mentions for artifact derivation tracking is that relationships depend entirely on manual tagging within the content. If @implements, @tests, or @depends tags are omitted, the provenance record will not capture those derivation links.