trace

Traces missing links in project management workflows.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill trace-heymishy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/heymishy/2x2-v3-28-03-20216/tree/main/.github/skills/trace
Command: npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill trace-heymishy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates the full traceability chain across all pipeline artefacts for a feature. Surfaces broken links, orphaned artefacts, scope deviations, and metric gaps. Read-only — reports findings for humans to action, does not fix anything.

Core Features & Use Cases

  • On-demand trace checks (e.g., "trace this feature", "chain check", "traceability report") to verify end-to-end linkage.
  • CI-triggered validation: automatically run on PR open to surface trace issues before review.
  • Read-only reports: present findings to humans for remediation without modifying artefacts.

Quick Start

Trace a feature to validate end-to-end traceability and surface gaps for remediation.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I check pipeline traceability gaps for a feature?

Pipeline traceability validation works by applying chain structure checks, upstream and downstream validations, and documentation consistency checks across all artefacts. It surfaces broken links, orphaned artefacts, scope deviations, and metric gaps.

Can I automatically validate artefact traceability in CI-CD pipelines?

Yes, you can validate artefact traceability in CI-CD pipelines by running it as a PR-triggered CI check. This automatically surfaces broken links, orphaned artefacts, and scope deviations before review.

What is the best way to find orphaned artefacts and broken links across a pipeline?

The best way to find orphaned artefacts and broken links is to run a read-only traceability report. It validates the full chain by enforcing detections via chain structure checks and upstream and downstream validations without modifying artefacts.

Does the traceability report automatically fix broken links and scope deviations?

No, the traceability report does not fix broken links and scope deviations. It is strictly read-only, surfacing findings for humans to action without modifying any underlying pipeline artefacts.

When should I run a traceability chain check during software development?

You should run a traceability chain check during any pipeline stage or as a PR-triggered CI check. This verifies end-to-end linkage and surfaces metric gaps before review without altering artefacts.