requirement-quality

Evaluate feature specs for well-formed problem statements, scenarios, and acceptance criteria.

176|13|Updated Mar 2, 2026

Search Tags:#specification #validation #quality #feature #bdd #acceptance-criteria #requirement

Ready to run

npx skills add https://github.com/techygarg/lattice --skill requirement-quality

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirement-quality
Source: https://github.com/techygarg/lattice/tree/main/plugins/lattice/skills/requirement-quality
Command: npx skills add https://github.com/techygarg/lattice --skill requirement-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The skill helps product teams ensure feature specifications are complete, unambiguous, and ready for design-blueprint by enforcing standard structure and quality checks.

Core Features & Use Cases

Self-checks for problem statement clarity and scope boundaries
Structure validation to ensure scenarios, ACs, and independence
Use Case: Draft or audit feature specs across epics to guarantee coherence and testability

Quick Start

Draft a complete feature spec that passes the requirement-quality checks.

Frequently Asked Questions about requirement-quality

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

FAQPage Schema

How do I validate feature specification quality and acceptance criteria?▼

Feature specification validation checks problem statement clarity, scenario independence, and Given/When/Then acceptance criteria formatting to ensure requirements are complete and testable. It audits epics and features to guarantee coherent user value and scope boundaries.

What makes a well-formed feature spec ready for design-blueprint?▼

A well-formed feature spec requires clear problem statements, complete scope boundaries, enforced epic/feature/scenario conventions, proper frontmatter, and Given/When/Then acceptance criteria. It must demonstrate scenario independence and coherent user value to pass quality validation.

How do I audit existing requirements across epics for testability?▼

Auditing existing requirements evaluates problem statements, scenarios, and acceptance criteria for independence and complete scope. It applies standard structure validation across epics and features, producing a validation status and actionable guidelines to fix any coherence or testability gaps.

Does requirement validation enforce BDD Given/When/Then format?▼

Yes, requirement validation enforces the Given/When/Then acceptance criteria format by default. It checks that scenarios follow standard BDD conventions, ensuring every feature specification produces a clear validation status and actionable guidelines for unstructured or incomplete acceptance criteria.

Can I use automated checks to ensure feature spec independence and scope?▼

Automated checks evaluate feature specs to ensure scenario independence and complete scope boundaries. By applying default epic/feature/scenario conventions and frontmatter requirements, the validation process confirms coherent user value and outputs actionable guidelines for any failing specifications.

What are the limitations of automated specification quality checks?▼

Automated specification quality checks are limited to enforcing structural conventions, frontmatter requirements, and Given/When/Then acceptance criteria formatting. They validate problem statement clarity and scenario independence but cannot assess subjective business logic or replace human review of feature scope.