requirements-reviewer_skill

This skill helps perform systematic requirements reviews using Fagan inspection and Perspective-Based Reading to identify defects and improve clarity.
  • HTML

22

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill nahisaho/musubi --skill requirements-reviewer

  • SKILL.md46.1 KB

Overview

This skill is a Requirements Reviewer AI that applies formal inspection techniques to ensure high-quality requirements and SRS documents. It combines Fagan Inspection structure with Perspective-Based Reading (PBR) to find defects, ambiguities, inconsistencies, and untestable statements early. The goal is to improve specification quality, enforce testability and traceability, and support quality gate decisions before design and implementation.

How this skill works

The skill inspects requirements by following the Fagan Inspection phases: planning, overview, individual preparation, inspection meeting, rework, and follow-up. It assigns reviewer perspectives (user, developer, tester, architect, security) and uses checklists to classify defects (missing, ambiguous, conflicting, untestable). It reports defect density, coverage, and distribution, and verifies EARS format and standards compliance where applicable.

When to use it

  • Before design handoff to catch defects early and reduce rework costs
  • When preparing for a formal quality gate or milestone review
  • To validate testability, traceability, and standards compliance of an SRS
  • When multiple stakeholders must review requirements from different viewpoints
  • To produce objective defect metrics and inspection artifacts for audits

Best practices

  • Plan inspections with clear scope, roles (moderator, author, reader, recorder), and timeboxes
  • Use PBR to assign specific perspectives so each reviewer has focused checklists
  • Record defects without debating solutions during the inspection meeting
  • Classify defects by severity and type, and track rework until follow-up verifies closure
  • Verify EARS patterns, acceptance criteria, and traceability IDs for every requirement

Example use cases

  • Conduct a Stage 1.5 requirements review to decide readiness for design
  • Run a two-hour inspection meeting with distributed reviewers using PBR checklists
  • Analyze an SRS for testability and automatically generate acceptance criteria gaps
  • Produce defect density and coverage metrics for a regulatory audit
  • Validate that security and architecture constraints are explicitly specified

FAQ

It focuses on requirements artifacts such as SRS, feature specs, user stories, and acceptance criteria.

How are defects prioritized?

Defects are classified by severity (critical, major, minor) and by type (missing, ambiguous, conflicting, untestable) to drive rework priorities.

Can it enforce standards like IEEE 830 or ISO/IEC/IEEE 29148?

Yes. It checks for common standards compliance items such as completeness, clarity, traceability, and format guidelines.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational