requirement-patterns

Write testable requirements and user stories with INVEST and REQ-XXX identifiers.

10|5|Updated Jan 2, 2026

Search Tags:#requirements #specifications #patterns #acceptance criteria #user stories #INVEST

Ready to run

npx skills add https://github.com/ddunnock/claude-plugins --skill requirement-patterns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirement-patterns
Source: https://github.com/ddunnock/claude-plugins/tree/main/skills/speckit-generator/skills/requirement-patterns
Command: npx skills add https://github.com/ddunnock/claude-plugins --skill requirement-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams write clear, testable, and unambiguous requirements and user stories, reducing rework and miscommunication during product development.

Core Features & Use Cases

Templates & Patterns provide INVEST criteria, acceptance criteria formats, and structured identifiers (REQ-XXX) to enable traceability.
Anti-pattern Guidance illustrates common requirement mistakes with concrete fixes to improve clarity and testability.
Domain Examples includes ready-to-use templates for common areas such as authentication, APIs, and data processing to accelerate documentation.

Quick Start

Propose a complete set of requirements for a sample feature using INVEST principles, and reference the included anti-patterns and examples to refine them.

Frequently Asked Questions about requirement-patterns

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

FAQPage Schema

How do I write clear and testable user stories for software features?▼

To write clear and testable user stories, apply the INVEST pattern to ensure each story is independent and verifiable. You must pair every story with explicit acceptance criteria to reduce ambiguity and rework during development.

What are common anti-patterns when writing requirements and acceptance criteria?▼

Common anti-patterns in requirements include vague language, untestable conditions, and missing traceability. Avoid these mistakes by using structured identifiers like REQ-XXX and formalizing acceptance criteria formats to ensure clarity.

How do I create formal requirement identifiers for traceability?▼

Create formal requirement identifiers by assigning structured labels such as REQ-XXX to each specification. This pattern enforces traceability across product development domains like APIs and business processes.

Can I use INVEST criteria for non-software business process requirements?▼

Yes, INVEST criteria can be applied to business process requirements. The skill provides domain examples for APIs and data processing, guiding the creation of well-formed requirements beyond standard software features.

What is the best way to structure acceptance criteria for API specifications?▼

The best way to structure acceptance criteria for API specifications is to use explicit, testable conditions. The skill provides ready-to-use domain templates for API requirements to accelerate documentation and enforce testability.

Why do my requirements keep causing miscommunication during development?▼

Requirements cause miscommunication when they are ambiguous and lack testable acceptance criteria. Using structured patterns like INVEST and formal identifiers eliminates common anti-patterns and aligns team understanding.