skills.rest
samcdavid
samcdavidCOMMUNITY
Explore all skills by this author →
𝕏@sammy_fix_itGitHub

requirements-audit

Map acceptance criteria to code and document coverage gaps.

4|1|Updated May 31, 2015
Search Tags:#specification#requirements#audit#traceability#edge-cases#code-review#project-management
One-click install
npx skills add https://github.com/samcdavid/dotfiles --skill requirements-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-audit
Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/requirements-audit
Command: npx skills add https://github.com/samcdavid/dotfiles --skill requirements-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual requirements reviews are time-consuming and error-prone. This guide provides a structured approach to verify that what was built matches the spec by tracing each acceptance criterion to code and surfacing gaps, edge cases, and unintended scope changes.

Core Features & Use Cases

  • Structured requirements map: captures acceptance criteria, sources, and edge cases for traceability.
  • End-to-end traceability: links spec to code and tests to validate coverage.
  • Scope and risk analysis: detects scope creep and drift across changes.
  • Applicable to PRs, tickets, or feature specifications to ensure completeness.

Quick Start

Describe the target PR or feature and run the audit to generate the requirements map.

Frequently Asked Questions about requirements-audit

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

FAQPage Schema
How do I verify that my code matches the project specification?▼

A requirements audit maps acceptance criteria to code changes to verify feature completeness. This structured approach traces specifications to uncover gaps, edge cases, and unintended scope drift in pull requests or feature tickets.

What is the best way to trace acceptance criteria to code in a pull request?▼

The best way to trace acceptance criteria to code is by generating a traceability matrix. This matrix documents spec-to-code coverage, links tests to requirements, and highlights any unverified edge cases or missing functionality within the pull request.

How do I detect scope creep and unintended changes in a feature ticket?▼

Detect scope creep and unintended changes by applying scope and risk analysis during a requirements audit. Mapping the feature ticket against the original requirements map reveals drift and unrequested modifications introduced during development.

Can I use a requirements audit on existing feature descriptions without a formal spec?▼

Yes, you can audit existing feature descriptions by generating a requirements map from the provided text. The audit captures acceptance criteria, sources, and edge cases to establish traceability and validate code coverage without a formal specification document.

What documents do I need to create a traceability matrix for my project?▼

You need the feature description, pull request, or ticket, along with the code changes to create a traceability matrix. The audit uses these inputs to construct a requirements map and document the spec-to-code coverage and gaps.

Related Skills

Explore More Product & Management Skills→
williabywilliaby
2

pr-prepare

Generate Markdown pull request descriptions from git status, log, and diffs.

Community
Basic
AcidicSoilAcidicSoil
1

trace-requirements

Generate bidirectional traceability matrices linking acceptance criteria to implementations and tests.

Community
Advanced
prof-danielcprof-danielc

speckit.validate

Validate code implementations against specification requirements and acceptance criteria.

Community
Intermediate
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced