hf-traceability-review

Verify end-to-end evidence links from requirements to verified implementation.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hujianbest/garage-agent --skill hf-traceability-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf-traceability-review
Source: https://github.com/hujianbest/garage-agent/tree/main/packs/coding/skills/hf-traceability-review
Command: npx skills add https://github.com/hujianbest/garage-agent --skill hf-traceability-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

After code reviews, teams often validate that requirements, design decisions, tasks, implementation, and verification records are coherently linked. This skill ensures a complete evidence chain and flags drift or missing artifacts before gate transitions.

Core Features & Use Cases

  • End-to-end traceability checks across spec → design → tasks → implementation → verification.
  • Precheck gating and resolution guidance when evidence is incomplete or inconsistent.
  • Formal, checklist-driven reviews mediated by a standard references document, with clear verdicts (through, modify, block).
  • Supports explicit traceability requests from stakeholders to ensure compliance and auditability.

Quick Start

Run a traceability review on the latest merged feature branch to verify the complete evidence chain.

Frequently Asked Questions about hf-traceability-review

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

FAQPage Schema
How do I verify end-to-end traceability from requirements to implementation after a code review?

Traceability verification links requirements to implementation by assessing completeness across spec, design, tasks, and verification records. It applies after code reviews to confirm the evidence chain and flag missing artifacts before gate transitions.

What is the best way to audit evidence chains for missing artifacts before a release gate?

Auditing evidence chains uses a strict verification workflow with a link matrix and precheck blockers. This flags drift or incomplete artifacts across the spec to verification stages, providing a formal verdict to guide next automation steps.

How do I confirm that spec, design, and task artifacts are coherently linked during a code review?

Confirming coherent links requires a checklist-driven review mediated by a standard references document. This validates the end-to-end evidence chain across spec, design, tasks, and implementation to ensure compliance and auditability.

Can I use a traceability review for explicit compliance requests from stakeholders?

Traceability reviews support explicit compliance requests from stakeholders by verifying the complete evidence chain. It assesses completeness across all project artifacts and delivers a formal verdict of through, modify, or block.

What happens when precheck gating finds incomplete or inconsistent traceability evidence?

When precheck gating finds incomplete evidence, it triggers blockers and provides resolution guidance. This prevents gate transitions until the drift is resolved and the evidence chain is complete across all required artifacts.

Why do I need a formal verdict after checking traceability across my feature branch?

A formal verdict after checking traceability guides next automation steps by clearly indicating whether to proceed, modify, or block. It ensures the complete evidence chain is validated before merging or releasing the feature branch.