functional-requirements-check

Verify implementations against specification documents and generate remediation reports.

1|Updated Jun 27, 2025
One-click install
npx skills add https://github.com/d-kishi/ubiquitous-lang-mng --skill functional-requirements-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: functional-requirements-check
Source: https://github.com/d-kishi/ubiquitous-lang-mng/tree/main/.claude/skills/spec-compliance-auto/rules/functional-requirements-check.md
Command: npx skills add https://github.com/d-kishi/ubiquitous-lang-mng --skill functional-requirements-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

機能要件が仕様書通りに実装されているかを検証します。

Core Features & Use Cases

  • 実装機能の網羅性チェック
  • 否定的仕様の不実装確認
  • ビジネスルールとバリデーションの正確性確認

Quick Start

仕様書項番と照合し、実装が仕様通りかどうかを検証します。

Frequently Asked Questions about functional-requirements-check

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

FAQPage Schema
How do I verify that code implementations match functional requirements in specification documents?

Functional requirements verification automates checking that implementations conform to specification documents. This Skill traces requirements to code, detects deviations across functional, data integrity, performance, and UI/UX dimensions, and produces actionable remediation reports to achieve 95% conformance.

What does functional requirements validation during development catch?

Validation catches incomplete feature implementations, unintended behaviors violating negative specifications, and accuracy gaps in business rules and validation logic. Applied during feature development, code changes, testing, and audits to ensure specification-to-code traceability.

Can I use requirement verification to audit existing implementations?

Yes. This Skill applies across new feature development, code changes, testing phases, and compliance audits. It detects conformance deviations in mature codebases and generates detailed remediation reports for non-conformant areas.

How does functional requirements verification differ from standard testing?

Requirements verification enforces explicit doc-to-code traceability and checks both positive requirements and negative specifications (what must not be implemented). Standard testing typically validates behavior against implicit expectations, while this approach ties each code path back to specification items.

What output does a functional requirements check produce?

The Skill produces actionable remediation reports detailing which specification items lack corresponding implementations, which implementations violate negative requirements, and areas where business rules or validation logic diverge from documented intent.

When should I run functional requirements validation in the development cycle?

Run validation during feature development to catch deviations early, after code changes to verify conformance, during testing phases to confirm specification coverage, and during audits to assess overall compliance across functional and non-functional dimensions.