Generate a structured requirements document from task context via guided questions.
npx skills add https://github.com/IKatsuba/skills --skill spec-requirements
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
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.
Provide the spec name and context, and I will generate a structured requirements document.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
ranvirsinghConvert natural language feature ideas into GitHub Issue-backed specs.
IKatsubaGenerate a structured design document from requirements and research files.
bearbinaryConverts Markdown PRDs into structured JSON task files with progress tracking.
edwifiguyPrompt for one clarifying question before acting on ambiguous requirements.
