Requirement Assistant

Name: Requirement Assistant
Availability: InStock
Author: AsiaOstrich

Write structured user stories and requirement documents with INVEST criteria and acceptance criteria.

70|13|Updated Dec 24, 2025

Search Tags:#documentation #requirements #product management #acceptance criteria #INVEST #user story

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write well-structured user stories and requirement documents, ensuring clarity and adherence to quality standards like INVEST.

Core Features & Use Cases

User Story Generation: Follows the "As a [role], I want [feature], So that [benefit]" format.
Acceptance Criteria Definition: Helps define specific, testable conditions for completion.
INVEST Guideline Adherence: Ensures stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable.
Use Case: When starting a new feature, use this Skill to draft the initial user story and its acceptance criteria, ensuring all stakeholders have a shared understanding of the requirements.

Quick Start

Use the requirement assistant to write a user story for a new login feature.

Frequently Asked Questions about Requirement Assistant

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

FAQPage Schema

How do I write a user story using the INVEST criteria?▼

Acceptance criteria define specific, testable conditions for a user story's completion. They are created using standardized templates to ensure all stakeholders share a clear understanding of functional requirements.

What is the best way to document non-functional requirements for product management?▼

The best way to document non-functional requirements is using standardized templates and best practices. This ensures clarity and tracks quality attributes alongside functional requirements and bug reports.

Does this requirement assistant write structured bug reports?▼

Yes, the requirement assistant writes structured bug reports. It uses standardized templates and best practices alongside functional and non-functional requirements to maintain clear documentation.

How to define testable conditions for feature completion?▼

To define testable conditions for feature completion, establish clear acceptance criteria. This practice ensures user stories remain testable and provides a shared understanding of when the feature is done.