req-reviewer

Score requirement definition documents on a 10-point quality scale.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/takemo101/compose-workflow --skill req-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: req-reviewer
Source: https://github.com/takemo101/compose-workflow/tree/main/.pi/skills/req-reviewer
Command: npx skills add https://github.com/takemo101/compose-workflow --skill req-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the review of requirement definition documents, ensuring they meet quality standards for completeness, clarity, and feasibility.

Core Features & Use Cases

  • Automated Quality Scoring: Evaluates requirement documents against predefined criteria and assigns a score out of 10.
  • Detailed Feedback: Provides specific feedback on missing sections, unclear statements, and potential inconsistencies.
  • Use Case: Before starting development, use this Skill to quickly assess a new set of requirements, identify potential issues early, and ensure a high-quality foundation for the project.

Quick Start

Review the attached requirement document 'project-requirements.md' for quality.

Frequently Asked Questions about req-reviewer

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

FAQPage Schema
How do I review requirement definition documents for quality and completeness?

Reviewing requirement definition documents involves checking completeness, clarity, consistency, and feasibility, scoring quality on a 10-point scale. It validates mandatory sections, requirement coverage, non-functional aspects, scope definition, and acceptance criteria.

What is automated requirement validation and how does it work?

Automated requirement validation evaluates requirement documents against predefined criteria to assign a quality score out of 10. It checks mandatory sections, non-functional aspects, acceptance criteria, terminology consistency, and inter-requirement coherence.

Can I check if my software requirements have clear objectives and acceptance criteria?

Checking software requirements for clear objectives and acceptance criteria is possible by validating the document against predefined quality standards. It identifies missing sections, unclear statements, and potential inconsistencies, providing detailed feedback.

What's the best way to ensure requirement feasibility and technical validation before development?

Ensuring requirement feasibility and technical validation before development is best achieved by scoring the requirement document on a 10-point scale. It focuses on feasibility, inter-requirement coherence, and technical validation through references.

Why does my requirement review fail to identify inconsistencies in terminology?

Requirement review identifies inconsistencies in terminology by checking for terminology consistency and inter-requirement coherence. If failures occur, the document may lack explicit scope definition or contain ambiguous statements that prevent accurate validation.