Audit SDLC requirements documents and generate categorized findings reports.
npx skills add https://github.com/tomzx/agents --skill review-requirements-tomzx
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
Audits a requirements document and reports findings across five categories: clarity, completeness, testability, feasibility, and conflicts.
Analyze a requirements document and generate a categorized findings report ready for review.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
tomzxAudit telemetry plans for completeness, consistency, and actionable metrics.
tomzxAudits needs assessments for evidence, stakeholder coverage, and verdict soundness.
tomzxStandardize GitHub labels to match SDLC conventions across repositories.
EdanStarfireValidate task requirements for clarity, completeness, specificity, testability, and feasibility.
