create-requirements

Draft structured requirements documents from feature briefs or issue descriptions.

5|Updated Jul 25, 2025

Search Tags:#documentation #specification #requirements #feature #sdlc #acceptance-criteria #brief

Ready to run

npx skills add https://github.com/tomzx/agents --skill create-requirements-tomzx

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts a structured requirements document from a feature brief or issue description, capturing functional and non-functional requirements, constraints, and acceptance criteria.

Core Features & Use Cases

Automatically identifies the goal and scope from the brief or issue
Produces a complete requirements document with FRs, NFRs, constraints, and acceptance criteria
Generates a versioned target directory and frontmatter linkage for traceability

Quick Start

Provide a feature brief or issue description in context to draft a formal requirements document.

Frequently Asked Questions about create-requirements

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

FAQPage Schema

How do I generate a requirements document from a feature brief?▼

To generate a requirements document from a feature brief, provide the brief or issue description as context. The tool drafts a structured document capturing functional and non-functional requirements, constraints, and acceptance criteria.

What is the best way to write acceptance criteria from a user story?▼

The best way to write acceptance criteria from a user story is using a testable, scenario-based style. This approach formats criteria to clearly validate specific scenarios derived from the story's scope and constraints.

Can I draft functional and non-functional requirements directly from GitHub issues?▼

Yes, you can draft functional and non-functional requirements directly from GitHub issues. The tool processes issue descriptions to identify goals, scope, and constraints, producing a formal requirements document.

How do you structure a requirements document for traceability in the SDLC?▼

To structure a requirements document for traceability in the SDLC, use a frontmatter-driven output with issue linkage. This ensures a clear connection between the source issue and the generated versioned target directory.

What are the limitations of automatically generating specifications from briefs?▼

A limitation of automatically generating specifications from briefs is that the output quality depends heavily on the initial brief's detail. It identifies goals and scope automatically but cannot infer unstated constraints or missing functional requirements.