skills.rest
eburairu
eburairuCOMMUNITY
Explore all skills by this author →
GitHub

sdd-requirements

Generate structured requirements.md files from feature concepts and steering documents.

1|Updated Jan 5, 2026
Search Tags:#documentation#specification#requirements#sdd#user-stories#acceptance-criteria#requirements.md
One-click install
npx skills add https://github.com/eburairu/Squat-Tracker --skill sdd-requirements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-requirements
Source: https://github.com/eburairu/Squat-Tracker/tree/main/.agent/skills/sdd-requirements
Command: npx skills add https://github.com/eburairu/Squat-Tracker --skill sdd-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams transform vague feature ideas into formal, testable requirements, enabling consistent implementation and verification.

Core Features & Use Cases

  • Specification drafting: Convert ideas into concrete requirements and acceptance criteria.
  • Structured requirements generation: Create a complete requirements.md under .sdd/specs/[spec-name]/requirements.md with sections such as Function Overview, User Stories, Functional Requirements, and Non-Functional Requirements.
  • Steering-driven validation: Read and validate inputs against .sdd/description.md and .sdd/steering/ documents before finalizing the spec.

Quick Start

Provide a feature concept prompt, and the skill will generate a ready-to-use requirements.md in the appropriate .sdd/specs/[spec-name]/ directory.

Frequently Asked Questions about sdd-requirements

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

FAQPage Schema
How do I generate a requirements document from a vague feature idea?▼

You can generate formal requirements by providing a feature concept prompt, which produces a structured requirements.md file containing user stories, functional requirements, and acceptance criteria.

What is the best way to write testable user stories and acceptance criteria for a new app?▼

Creating testable user stories and acceptance criteria involves validating the feature concept against steering documents and structuring the specification with distinct functional and non-functional requirement sections.

How do I structure a specification with functional and non-functional requirements?▼

To structure a specification, organize the generated document into sections like Function Overview, User Stories, Functional Requirements, and Non-Functional Requirements within an .sdd/specs directory.

Do I need steering documents to draft a specification?▼

Steering documents are required to draft a specification, as the process reads and validates the feature concept against the .sdd/steering directory before finalizing the requirements.

Can I convert a description.md file into a complete requirements.md for my system?▼

You can convert a description.md file into a requirements.md by reading the feature concept from .sdd/description.md and generating a structured specification under .sdd/specs/[spec-name]/.

What are the limitations of using automated requirements generation for feature specs?▼

A limitation of automated requirements generation is that it depends on a provided feature concept and valid .sdd/steering documents to produce an accurate and testable specification.

Related Skills

Explore More Product & Management Skills→
yi-john-huangyi-john-huang
48

sdd-requirements

Generate EARS-formatted requirements documents with FRs, NFRs, and acceptance criteria.

Community
Advanced
jota-batutajota-batuta

sdd-design

Generate design.md documents and ADRs from proposals and delta specs.

Community
Advanced
shdaifatshdaifat

Design Versioning Skill

Track and manage CAD design iterations using Git version control principles.

Community
Intermediate
dundasdundas

user-story-generator

Generate user stories with acceptance criteria in Markdown format.

Community
Intermediate