requirements_verify

Automate BABOK 7.2 requirement quality checks and generate verification reports.

40|15|Updated Apr 7, 2026

Search Tags:#checklist #requirements #verification #mcp #quality #ba #babok

Ready to run

npx skills add https://github.com/chaussky/ainalyst --skill requirements-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements_verify
Source: https://github.com/chaussky/ainalyst/tree/main/skills/requirements_verify
Command: npx skills add https://github.com/chaussky/ainalyst --skill requirements-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Verification of requirements quality is essential to ensure that artifacts are atomic, unambiguous, testable, complete, and consistent across BABOK 7.2 workflows.

Core Features & Use Cases

Automatic quality checks for nine BABOK quality characteristics across 7.2 workflows, using MCP rules.
Guided remediation: opens verification issues, links to 5.1 and 7.1 artifacts, and surfaces blockers.
Use Case: BA runs the skill on a project to identify and prioritize issues and generate a verification report.

Quick Start

Run the check_req_quality workflow for your project to surface issues and prepare a verification report.

Frequently Asked Questions about requirements_verify

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

FAQPage Schema

How do I verify requirements quality across BABOK 7.2 workflows?▼

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.

What checks are used for requirements verification in a business analysis project?▼

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.

How do I generate a requirements verification report for use cases and business rules?▼

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.

Does requirements verification work with non-functional requirements and user stories?▼

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.

What is the best way to remediate requirement consistency issues found during verification?▼

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.

Can I check requirement testability and completeness without manual review?▼

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.