requirements-traceability
Installation
SKILL.md
Requirements Traceability — Under 100 People
Purpose
At under-100 people, a full enterprise Requirements Traceability Matrix (RTM) with 20-column rigor is overkill. This is the trim version: a simple table that shows, for every business requirement, what was built + how it was tested + who signed off. It's the answer when someone asks "wait, did we ever actually build the invoice-export feature?" three months after go-live.
Use when:
- Implementing a new SaaS platform with material configuration work
- Custom-building an internal tool or workflow
- Making a material process change requiring cross-team agreement
- Any scope where "did we ship what we said?" matters
Don't use when:
- Buying + configuring a SaaS tool with minimal customization
- Small iterative product changes
- Anything where the scope is trivial (< 1 week effort)
Template Structure
A spreadsheet or Notion table. 5–8 columns max. Goal: one row per requirement, trackable through lifecycle.