requirement

Name: requirement
Availability: InStock
Author: AsiaOstrich

Generate INVEST-compliant user stories with acceptance criteria and quality checklists.

70|13|Updated Dec 24, 2025

Search Tags:#specification #requirements #product management #acceptance criteria #user stories #invest

Ready to run

npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill requirement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirement
Source: https://github.com/AsiaOstrich/universal-dev-standards/tree/main/.gemini/skills/requirement-assistant
Command: npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill requirement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write well-defined user stories and requirements that adhere to the INVEST criteria, ensuring clarity, testability, and value.

Core Features & Use Cases

User Story Generation: Follows the "As a [role], I want [feature], So that [benefit]" format.
INVEST Validation: Ensures requirements are Independent, Negotiable, Valuable, Estimable, Small, and Testable.
Acceptance Criteria: Guides the creation of specific, measurable, and testable conditions.
Use Case: When planning a new feature, use this Skill to draft user stories that clearly communicate the desired outcome and acceptance criteria to the development team.

Quick Start

Use the requirement skill to write a user story for a new user profile editing feature.

Frequently Asked Questions about requirement

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

FAQPage Schema

How do I write user stories that meet INVEST criteria for product management?▼

To write user stories meeting INVEST criteria, define the role, feature, and benefit, then validate that the requirement is Independent, Negotiable, Valuable, Estimable, Small, and Testable. This ensures clarity and testability for the development team.

What is the best way to generate acceptance criteria for a new feature?▼

The best way to generate acceptance criteria is to draft the user story first, then define specific, measurable, and testable conditions that the feature must meet. This ensures the requirements are clearly communicated and verifiable.

How do I format a user story for spec-driven development?▼

Format a user story for spec-driven development using the "As a [role], I want [feature], So that [benefit]" structure. This standard format communicates the desired outcome and value to stakeholders and developers.

Can I create user stories and requirements in multiple languages?▼

Yes, you can create user stories and requirements in multiple languages. The generation process supports multilingual output while adhering to INVEST criteria and integrating with requirement engineering standards.

When do I need to use a quality checklist for requirement engineering?▼

You need to use a quality checklist for requirement engineering when planning a new feature to ensure the generated user stories are testable and adhere to core standards. This prevents ambiguity and aligns expectations.