Verified:GitHub

requirements

Generate user stories and acceptance criteria from an active spec.

4|Updated Apr 26, 2026

Search Tags:#requirements #delegation #acceptance criteria #user stories #spec #non-functional requirements #approval workflow

Ready to run

npx skills add https://github.com/curdx/curdx-flow --skill requirements-curdx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements
Source: https://github.com/curdx/curdx-flow/tree/main/plugins/curdx-flow/skills/requirements
Command: npx skills add https://github.com/curdx/curdx-flow --skill requirements-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts an active spec’s goal and research context into structured, testable requirements that prevent vague scope, missing success criteria, and unverified “done” claims.

Core Features & Use Cases

Coordinator-driven requirements phase that gathers repo/spec context, runs an interview, and delegates creation to the product-manager subagent.
User story and requirement generation including acceptance criteria, functional requirements (FR-), non-functional requirements (NFR-), glossary, out-of-scope, and dependencies.
Walkthrough and explicit approval gate that stops the workflow after producing an artifact at specs/$spec/requirements.md.

Quick Start

Use the requirements skill to generate requirements for your active spec by running /curdx-flow:requirements [spec-name] from within Claude Code.

Frequently Asked Questions about requirements

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

FAQPage Schema

How do I generate user stories and acceptance criteria from a project spec?▼

Yes, structured requirements generation covers both functional requirements (FR-*) and non-functional requirements (NFR-*), along with glossary terms, dependencies, and explicit out-of-scope boundaries to prevent vague scope.

How does the approval workflow work for requirements generation?▼

The requirements workflow captures context by using snapshot data from your active spec and can optionally run an interview to gather missing details before delegating artifact creation to a product-manager subagent.

Can I include non-functional requirements and out-of-scope boundaries in my spec?▼

What is the best way to capture measurable requirements for scoped delivery planning?▼

The best way to capture measurable requirements for scoped delivery planning is to transform spec goals into testable user stories with explicit acceptance criteria, preventing missing success criteria and unverified done claims.