skills.rest
friedbotstudio
friedbotstudioOFFICIAL
Explore all skills by this author →
GitHub

spec-traceability-review

Verify acceptance-criterion traceability between specs and upstream intake and BRD sources.

5|Updated Apr 29, 2026
Search Tags:#requirements#acceptance criteria#traceability#spec review#intake#brd
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill spec-traceability-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-traceability-review
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/spec-traceability-review
Command: npx skills add https://github.com/friedbotstudio/baseline --skill spec-traceability-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents acceptance criteria from being approved unless every requirement in a spec can be traced back to a real upstream source and every upstream requirement is accounted for.

Core Features & Use Cases

  • Forward trace validation: Checks each spec acceptance criterion against its referenced intake or BRD requirement.
  • Reverse trace validation: Confirms that no upstream acceptance criterion is silently dropped during spec writing.
  • Gap reporting: Flags missing upstream references, unresolved links, split coverage without notes, and in-scope BRD items with no spec coverage.
  • Use Case: A reviewer can compare a design or product spec with the intake and BRD before approval and quickly spot broken traceability.

Quick Start

Use this skill to review the spec for a slug against its intake and optional BRD, then report any missing, unresolved, or silently dropped acceptance-criterion links.

Frequently Asked Questions about spec-traceability-review

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

FAQPage Schema
How do I verify spec requirements are fully traceable to upstream intake and BRD sources?▼

Spec traceability verification checks forward and reverse linkage between spec acceptance criteria and upstream intake or BRD requirements. It flags silently dropped criteria, unresolved references, and split criteria lacking explanatory notes before spec approval to ensure full bidirectional coverage.

What happens when an upstream acceptance criterion is silently dropped during spec writing?▼

When an upstream acceptance criterion is silently dropped, reverse trace validation flags the missing spec coverage as a gap. The review process identifies these silent drops alongside unresolved links and in-scope BRD items lacking corresponding spec requirements to prevent unapproved omissions.

How do I review a spec for broken traceability before approval?▼

Reviewing a spec for broken traceability involves checking forward linkage from each spec acceptance criterion to its referenced intake or BRD requirement, then validating reverse linkage to confirm no upstream criteria are missing, generating a gap report for any broken links.

Does spec traceability review require both intake and BRD documents to work?▼

Spec traceability review requires matching intake coverage for every spec requirement, while BRD linkage is optional. The validation checks forward and reverse integrity against available upstream sources, flagging in-scope BRD items with no spec coverage only when a BRD is provided.

Why does spec review flag split criteria that lack explanatory notes?▼

Spec review flags split criteria lacking explanatory notes because traceability integrity requires clear context when a single upstream requirement is divided into multiple spec acceptance criteria. Without notes, the forward linkage becomes ambiguous and difficult to validate against the original intake or BRD source.

Can I use spec traceability validation for documents outside the docs/specs directory?▼

Spec traceability validation applies specifically to spec reviews for documents located at docs/specs/<slug>.md. It requires matching intake coverage and optional BRD linkage structured to align with this specific file path convention to execute forward and reverse linkage checks properly.

Related Skills

Explore More Product & Management Skills→
dmmulroydmmulroy
232

overseer-plan

Convert Markdown planning documents into hierarchical Overseer tasks via MCP codemode.

Community
Advanced
alistairsteadalistairstead

gh-pr-comments

List unresolved GitHub PR review comments and resolve threads by thread_id.

Community
Advanced
nikhil02032022nikhil02032022

brd-traceability

Map implemented code to MEETCS-BRD-CRM-001 v1.0 requirements and identify coverage gaps.

Community
Advanced
samcdavidsamcdavid
4

requirements-audit

Map acceptance criteria to code and document coverage gaps.

Community
Advanced