spec:requirements

Generate a structured requirements document from task context via guided questions.

1|Updated Jan 21, 2026

Search Tags:#planning #documentation #specification #requirements #user-stories #acceptance-criteria

Ready to run

npx skills add https://github.com/IKatsuba/skills --skill spec-requirements

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning vague task descriptions into actionable requirements is error-prone and slow; this skill guides you through targeted clarifying questions to produce a crisp, reusable requirements document.

Core Features & Use Cases

Guided questions to elicit essential context and reduce ambiguity before writing requirements.
Structured document generation that outputs a standard .specs/<spec-name>/requirements.md with Introduction, Glossary, and Acceptance Criteria.
Inline scope handling to capture scope boundaries and edge cases without breaking the current flow.

Quick Start

Provide the spec name and context, and I will generate a structured requirements document.

Frequently Asked Questions about spec:requirements

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

FAQPage Schema

How do I write structured requirements from vague task descriptions?▼

To write structured requirements, provide the task context and answer targeted clarifying questions to produce a crisp requirements document with Introduction, Glossary, and Acceptance Criteria sections.

What is the best way to define acceptance criteria and scope boundaries for feature planning?▼

The best way to define acceptance criteria and scope boundaries is through guided inline scope handling during requirement generation, capturing edge cases without breaking your current planning flow.

How do I generate a standardized requirements document for project scoping?▼

You generate a standardized requirements document by transforming task context into a reusable file saved at .specs/<spec-name>/requirements.md, ensuring consistent structure across product, design, and engineering teams.

Can I use this requirements generation process for user stories and task briefs?▼

Yes, you can use this requirements generation process for user stories and task briefs, as the guided questions apply directly to feature planning and project scoping across multiple disciplines.

Why does my requirements document lack a glossary and standardized frontmatter?▼

Your requirements document lacks a glossary and frontmatter because it was not generated using a standardized template that enforces these specific sections to reduce ambiguity and ensure consistency.