How does this skill improve software testing?

It ensures every requirement includes specific, measurable acceptance criteria (Given/When/Then) that can be directly converted into automated test cases or manual QA scripts.

Can I use this for agile project management?

Yes, it includes specialized support for Epic, Feature, and User Story levels, specifically following the INVEST framework to ensure stories are ready for sprint planning.

Does it support formal documentation standards?

Yes, it provides the 'Shall' pattern for formal requirements, making it suitable for enterprise-grade documentation and regulatory compliance where mandatory vs. optional features must be clear.

What are 'ambiguity markers' in requirements?

These are subjective terms like 'fast', 'user-friendly', or 'secure' that are difficult to test. This skill identifies these words and prompts you to provide specific metrics instead.

Requirement Writing Patterns

Name: Requirement Writing Patterns
Author: ddunnock

byddunnock

•

Productivity & Workflow

Generates clear, testable, and unambiguous software requirements using industry-standard frameworks like INVEST and Gherkin.

Requirement Writing Patterns equips Claude with a specialized framework for drafting high-quality technical documentation and specifications. It helps users transform vague ideas into actionable user stories, formal 'shall' statements, and Given/When/Then acceptance criteria. By identifying ambiguity markers and enforcing consistent identifiers, this skill reduces implementation cycles and ensures that developers and stakeholders have a shared, measurable understanding of system behavior.

Key Features

011 GitHub stars

02Standardizes formal requirements using the mandatory 'Shall' and 'Should' syntax

03Detects and replaces vague language like 'properly' or 'quickly' with measurable metrics

04Implements INVEST criteria for high-quality, sprint-ready user stories

05Generates BDD-style acceptance criteria using Given/When/Then patterns

06Differentiates between functional requirements and system constraints for better architecture

Use Cases

01Reviewing existing documentation to identify gaps in testability and clarity

02Drafting comprehensive technical specifications for new feature development

03Refining messy product backlogs into clear, testable user stories

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add ddunnock/claude-plugins requirement-patterns

For use in Claude.ai and ChatGPT

Download Skill