What is the primary output of the sdd-requirements skill?

The skill generates a structured requirements.md file located within a specific specification directory, containing feature overviews, user stories, and acceptance criteria.

What documents are required before running this skill?

It requires a description.md file and three steering documents: product.md, tech.md, and structure.md to ensure the generated requirements align with project standards.

How does it help with the development lifecycle?

It ensures that the 'What' and 'Why' are fully defined before the 'How' (Design) and 'Execution' (Implementation), reducing scope creep and technical debt.

Can I use this for existing features?

Yes, the skill can identify existing specification directories and update or create requirements within them based on new descriptions.

SDD Requirement Architect

Name: SDD Requirement Architect
Author: eburairu

byeburairu

•

Productivity & Workflow

Generates structured software requirement documents and acceptance criteria using a standardized development workflow.

About

SDD Requirement Architect is a specialized Claude Code skill designed to bridge the gap between initial feature ideas and technical implementation. By following the Structured Design & Development (SDD) methodology, this skill automates the creation of comprehensive requirements.md files. It analyzes functional descriptions and project steering documents to produce clear user stories, detailed functional requirements, and actionable acceptance criteria, ensuring a solid foundation for the subsequent design and coding phases.

Key Features

Automated requirements.md generation with standardized sections
Integrated workflow handoff for design and implementation steps
Context-aware user story creation with clear motivations
1 GitHub stars
Checkbox-style acceptance criteria for precise testing
Prerequisite validation for steering and product documentation

Use Cases

Standardizing the requirement gathering process across complex software projects
Transforming rough feature descriptions into formal technical specifications
Defining clear success criteria and acceptance tests before writing code

About

Key Features

Automated requirements.md generation with standardized sections
Integrated workflow handoff for design and implementation steps
Context-aware user story creation with clear motivations
1 GitHub stars
Checkbox-style acceptance criteria for precise testing
Prerequisite validation for steering and product documentation

Use Cases

Standardizing the requirement gathering process across complex software projects
Transforming rough feature descriptions into formal technical specifications
Defining clear success criteria and acceptance tests before writing code