skills.rest
orekyuu
orekyuuCOMMUNITY
Explore all skills by this author →
Website𝕏@orekyuuGitHub

sdd-spec

Guide code investigation, requirement elicitation, and specification document creation.

Updated Feb 28, 2026
Search Tags:#design#development#documentation#specification#requirements#sdd
One-click install
npx skills add https://github.com/orekyuu/orekyuu-claude-plugins --skill sdd-spec-orekyuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/orekyuu/orekyuu-claude-plugins/tree/main/plugins/sdd/skills/sdd-spec
Command: npx skills add https://github.com/orekyuu/orekyuu-claude-plugins --skill sdd-spec-orekyuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the development process by ensuring that specifications are thoroughly defined before implementation, reducing ambiguity and rework.

Core Features & Use Cases

  • Specification-Driven Development: Guides users through defining requirements, designing tests, and implementing features in a structured manner.
  • Phased Development: Breaks down development into distinct phases: code investigation, requirement gathering, and specification creation.
  • Use Case: When starting a new feature, use this Skill to first understand the existing codebase, then meticulously gather user requirements through a guided conversation, and finally generate a comprehensive design specification document.

Quick Start

Use the sdd-spec skill to begin defining specifications for a new feature.

Frequently Asked Questions about sdd-spec

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

FAQPage Schema
What is specification-driven development and when should I use it?▼

Specification-driven development is defining comprehensive requirements and technical designs before implementing code. Use it when starting new features to reduce ambiguity, ensure clear functional behavior understanding, and minimize downstream rework.

How do I create a specification document for a new software feature?▼

To create a specification document, you first investigate the existing codebase, then gather requirements through a guided conversation, and finally generate a structured design specification detailing functional behaviors and technical designs.

How do I gather software requirements before writing any code?▼

You gather software requirements by using a guided interactive process that elicits functional needs and design specifications from users, ensuring a thorough understanding of expected behaviors prior to actual implementation.

Does specification-driven development work for analyzing an existing codebase?▼

Yes, specification-driven development supports code investigation as its initial phase. It analyzes existing files and structures to understand the current technical design before eliciting new requirements and generating updated specification documents.

What is the best way to structure technical design documents for development?▼

The best way to structure technical design documents is through a phased approach: starting with codebase analysis, moving to requirement elicitation, and culminating in a detailed specification document that captures both functional behavior and technical design.

Related Skills

Explore More Software Engineering Skills→
mayurpisemayurpise
39

init

Generate architecture diagrams and context files for brownfield codebases.

Community
Advanced
AutisticAFAutisticAF
4

testing-test-contract

Generate reusable contract test suites for Swift protocols.

Community
Intermediate
OpenWaggleOpenWaggle
4

to-prd

Analyzes code repositories to generate structured project requirement documents.

Official
Advanced
Nir-BhayNir-Bhay
19

backlog-refinement-guide

Guide backlog refinement sessions using the DEEP framework and Planning Poker.

Community
Intermediate