nw-shared-artifact-tracking

Identify and manage shared artifacts across journey steps with source-of-truth tracking.

Updated Apr 15, 2026

Search Tags:#validation #data-governance #source-of-truth #artifact-registry #shared-artifacts #journey-integration

Ready to run

npx skills add https://github.com/StudentCristian/nWave-github --skill nw-shared-artifact-tracking

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nw-shared-artifact-tracking
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-shared-artifact-tracking
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-shared-artifact-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared artifacts are data values appearing in multiple places across a journey. Every ${variable} must have a single source of truth and documented consumers. Untracked artifacts are the primary cause of horizontal integration failures.

Core Features & Use Cases

Artifact Registry Schema: centralizes definition of shared artifacts with source_of_truth, consumers, owner, integration_risk, validation
Integration Validation: ensures sources exist and consumers reference sources, enabling consistency checks
Governance Patterns: establishes patterns for common artifacts (version, install path, repository URL, configuration values, command names)

Quick Start

Define a shared artifact, specify its source of truth, and list its consumers to begin tracking across journey steps.

Frequently Asked Questions about nw-shared-artifact-tracking

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

FAQPage Schema

How do I manage shared artifacts appearing across multiple journey steps?▼

Shared artifact tracking identifies data values appearing in multiple journey steps and centralizes their definitions in an artifact registry schema. This ensures a single source of truth and documented consumers, preventing horizontal integration failures caused by untracked variables.

How do I validate integration consistency for shared variables in journey design?▼

Integration validation for shared artifacts works by applying validation checks that verify artifact sources exist and consumers correctly reference them. This ensures consistency by confirming every shared variable in the journey design points back to a defined source of truth.

What governance patterns should I apply for shared artifacts like repository URLs and configuration values?▼

Governance patterns for shared artifacts establish standardized definitions for common values like versions, install paths, repository URLs, configuration values, and command names. This enforces a single source of truth and clear ownership across journey integration scenarios.

Do I need an artifact registry schema before tracking shared journey data?▼

Yes, an artifact registry schema is required before tracking shared journey data. You must define the schema with clear owners, specified sources of truth, listed consumers, and defined validation checks to verify sources and consumers across steps.

Why do untracked shared artifacts cause horizontal integration failures?▼

Untracked shared artifacts cause horizontal integration failures because data values appearing in multiple journey steps lack a single source of truth and documented consumers. When variables are not centralized in an artifact registry, integration validation cannot verify consistency across steps.