review-requirements

Audit SDLC requirements documents and generate categorized findings reports.

5|Updated Jul 25, 2025

Search Tags:#documentation #requirements #analysis #review #conflicts #sdLC

Ready to run

npx skills add https://github.com/tomzx/agents --skill review-requirements-tomzx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-requirements
Source: https://github.com/tomzx/agents/tree/main/skills/review-requirements
Command: npx skills add https://github.com/tomzx/agents --skill review-requirements-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits a requirements document and reports findings across five categories: clarity, completeness, testability, feasibility, and conflicts.

Core Features & Use Cases

Prerequisites and file context: reads a requirements document from .sdlc/features/FEAT-NNNN-<slug>/requirements.md or from provided context; analyzes and records findings.
Structured output: produces a categorized findings report and flags unresolved questions for collaboration via .sdlc/features/FEAT-NNNN-<slug>/questions.md.
Review workflow: guides stakeholders through resolving conflicts and approving the requirements.

Quick Start

Analyze a requirements document and generate a categorized findings report ready for review.

Frequently Asked Questions about review-requirements

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

FAQPage Schema

What is requirements analysis in SDLC and how does an audit work?▼

Requirements analysis in SDLC audits feature documents to surface issues across clarity, completeness, testability, feasibility, and conflicts. The audit mechanism reads requirements.md files and evaluates them against context artifacts to generate a structured findings report.

How do I review a requirements document for conflicts and testability?▼

To review a requirements document, provide a requirements.md file within the .sdlc/features directory. The analysis cross-references context artifacts to identify conflicts and testability gaps, outputting a categorized findings report with unresolved questions for stakeholder collaboration.

Do I need specific folder structures to audit requirements documents?▼

Yes, auditing requirements documents requires a specific SDLC folder structure. You must place files under .sdlc/features/FEAT-NNNN-slug/requirements.md and supply guiding artifacts under .sdlc/context to enable proper style checks and conflict resolution.

What is the best way to track unresolved questions during requirements review?▼

The best way to track unresolved questions during requirements review is generating a questions.md file. The audit process automatically flags collaboration points and outputs them to .sdlc/features/FEAT-NNNN-slug/questions.md to guide stakeholder resolution.

What categories does a requirements audit report cover?▼

A requirements audit report covers five categories: clarity, completeness, testability, feasibility, and conflicts. Each category surfaces specific document issues and generates status updates to guide the stakeholder review workflow.