re-tool-selection
Installation
SKILL.md
Purpose
Guide requirements engineers through selecting and adopting tools for requirements development and management. Use this to make tool decisions based on actual workflow needs and project context rather than vendor demos and feature checklists.
This is not a product comparison chart. Tools change faster than any guide can track. It is a decision framework that helps you evaluate any tool against your real needs.
Key Concepts
RD Tools vs. RM Tools
| Category | Purpose | Examples | Key Capabilities |
|---|---|---|---|
| Requirements Development (RD) | Creating and specifying requirements | Word processors, modeling tools, prototyping tools, diagramming tools | Document authoring, visual modeling, UI mockups |
| Requirements Management (RM) | Tracking, tracing, and controlling requirements | Dedicated RM tools, ALM platforms | Unique IDs, attributes, traceability, baselines, change history, status tracking |
Most teams need both, but the pain points differ. If your problem is "we cannot write good requirements," an RM tool will not help. If your problem is "we cannot track changes and trace requirements," a word processor will not help.