What are non-functional requirements in this context?

It helps you identify and document critical system attributes like performance targets, security compliance, scalability needs, and usability standards.

How does it help with scope creep?

It provides templates to explicitly define in-scope and out-of-scope items, along with strategies for documenting scope boundaries and evaluating change requests.

When should I use the Requirements Patterns skill?

Use it during the initial phase of feature development or when transforming a vague idea into actionable technical specifications for your development team.

Does this skill support Gherkin syntax?

Yes, it provides Given-When-Then patterns for writing clear, scenario-based acceptance criteria that are easy to translate into automated tests.

Software Requirements Patterns

Name: Software Requirements Patterns
Author: Zate

byZate

Productividad y Flujo de Trabajo

Standardizes software requirements gathering using user story formats, acceptance criteria templates, and scope management frameworks.

Acerca de

This skill equips Claude with specialized patterns and templates for effective software requirements documentation and validation. It implements industry-standard frameworks like INVEST for user stories and Gherkin (Given-When-Then) for acceptance criteria, helping developers move from vague ideas to actionable, testable specifications. By incorporating functional and non-functional requirement checklists and scope management strategies, it ensures project boundaries are clear and technical debt is minimized during the planning phase.

Características Principales

Enhanced User Story generation using the INVEST criteria
Scope management tools for defining in-scope vs. out-of-scope boundaries
Comprehensive non-functional requirements checklists for performance, security, and scalability
Scenario-based acceptance criteria patterns including Gherkin and Checklist formats
Detailed edge case analysis for data, user behavior, and system failures
0 GitHub stars

Casos de Uso

Transforming high-level feature requests into detailed, developer-ready tasks
Validating existing project requirements against the INVEST quality framework
Defining precise 'Definition of Done' criteria and acceptance tests for new features

Acerca de

Características Principales

Enhanced User Story generation using the INVEST criteria
Scope management tools for defining in-scope vs. out-of-scope boundaries
Comprehensive non-functional requirements checklists for performance, security, and scalability
Scenario-based acceptance criteria patterns including Gherkin and Checklist formats
Detailed edge case analysis for data, user behavior, and system failures
0 GitHub stars

Casos de Uso

Transforming high-level feature requests into detailed, developer-ready tasks
Validating existing project requirements against the INVEST quality framework
Defining precise 'Definition of Done' criteria and acceptance tests for new features