skills.rest
s3nex-com
s3nex-comCOMMUNITY
Explore all skills by this author →
GitHub

requirements-tracer

Decompose business goals into user stories with acceptance criteria and traceability links.

Updated Apr 8, 2026
Search Tags:#requirements#traceability#bdd#user-stories#acceptance-criteria#orphan-detection#scope-change
One-click install
npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill requirements-tracer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-tracer
Source: https://github.com/s3nex-com/sdlc-skills-library/tree/main/skills/phase1/requirements-tracer
Command: npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill requirements-tracer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts business goals into testable, traceable requirements and keeps them linked to everything built from them. It also enforces scope discipline: every feature must trace back to an agreed requirement, and every requirement must have a clear acceptance criterion before work begins.

Core Features & Use Cases

  • Decomposition: convert a high-level business goal into user stories with Given/When/Then acceptance criteria.
  • Traceability: maintain a live matrix linking requirements to code and tests and detect orphaned code or unlinked requirements.
  • Scope assessment: perform impact analysis for scope changes and ensure independent delivery of requirements.

Quick Start

Decompose a high-level business goal into user stories with acceptance criteria and link them to the traceability matrix.

Frequently Asked Questions about requirements-tracer

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

FAQPage Schema
How do I decompose business goals into testable user stories with acceptance criteria?▼

To trace requirements, you maintain a live traceability matrix linking user stories, acceptance criteria, tests, and code, which automatically detects orphaned code or unlinked requirements throughout the lifecycle.

What is the best way to perform impact analysis for scope changes in requirements?▼

Scope-change impact analysis assesses proposed changes against the traceability matrix to ensure every feature traces back to an agreed requirement, verifying independent delivery and preventing scope creep.

How do I detect orphaned code or unlinked requirements in my project?▼

Orphan detection works by continuously cross-referencing the live traceability matrix to identify any code lacking a linked requirement or any requirement missing connected tests and implementation.

Can I enforce that every requirement has clear acceptance criteria before work begins?▼

Yes, scope discipline enforcement ensures every requirement must have a defined Given/When/Then acceptance criterion established and validated before any development work on that requirement can begin.

Does BDD traceability work for linking user stories directly to code and tests?▼

BDD traceability works by mapping Given/When/Then acceptance criteria directly to test cases and code modules, maintaining a live matrix that validates full coverage from requirement to implementation.

Related Skills

Explore More Product & Management Skills→
hfadhlullahhfadhlullah

PRD Generator

Generate Product Requirements Documents through an interview process.

Community
Advanced
beekeeper-labbeekeeper-lab

Build Traceability

Generate traceability matrices mapping user stories and acceptance criteria to test cases.

Community
Advanced
Imad-OuteImad-Oute
2

mh-cto-sdlc-acceptance-test-suite

Design BDD-style acceptance test suites from user-defined criteria.

Community
Advanced
AminAlamAminAlam
26

Requirements Traceability

Enforce bidirectional traceability across medical device software artifacts.

Community
Intermediate