requirements_verify

Requirement quality verification is automated across BABOK 7.2 workflows using MCP rules to check User Stories, Functional, Non-Functional, and Business Requirements for atomicity, testability, and consistency. It enforces automatic, completeness, and feasibility checks.

Requirements verification uses three check groups: automatic quality checks (Group A), consistency and completeness checks (Group B), and feasibility and understandability checks (Group C). These cover nine BABOK quality characteristics across repository artifacts.

Generating a requirements verification report involves running the check_req_quality workflow to surface issues across Use Cases and Business Rules. It links to 5.1 and 7.1 artifacts, tracks issues, and outputs a structured verification report.

Requirements verification works with Non-Functional Requirements and User Stories alongside Functional, Business, and Use Case artifacts. It applies MCP rules to ensure all artifact types are unambiguous, complete, and testable across workflows.

Remediation of requirement consistency issues is guided by linking verification problems directly to 5.1 and 7.1 repository artifacts. The workflow surfaces blockers, prioritizes issues, and tracks resolution status through to completion.

Checking requirement testability and completeness is fully automated through MCP rules. The workflow enforces automatic checks for nine BABOK quality characteristics, eliminating manual review for atomicity, ambiguity, and consistency validation.