sdd

Convert vague ideas into EARS-based requirements, designs, and task plans.

598|128|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/meleantonio/awesome-econ-ai-stuff --skill sdd-meleantonio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd
Source: https://github.com/meleantonio/awesome-econ-ai-stuff/tree/main/_skills/engineering/sdd
Command: npx skills add https://github.com/meleantonio/awesome-econ-ai-stuff --skill sdd-meleantonio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This section describes how the SDD skill helps convert vague research ideas into explicit, testable requirements and designs, enabling predictable collaboration and faster delivery.

Core Features & Use Cases

  • Generates EARS-style requirements from intent and steering documents to create a clear planning baseline.
  • Produces technical design content, data models, interfaces, and risk considerations to guide implementation.
  • Generates sequential task plans (two-level) linked to requirements and aligned with steering documents to enable iterative development.

Quick Start

Run the init command at your project root to scaffold the spec/ and steering/ directories.

Frequently Asked Questions about sdd

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

FAQPage Schema
How do I turn vague feature ideas into testable requirements?

Spec-driven development transforms vague ideas into explicit, testable requirements by generating EARS-style documents from intent and steering files, creating a clear planning baseline for feature implementation.

What is the best way to structure feature design and task planning documents?

Feature design and task planning are structured using living, versioned specifications including spec/intent.md, spec/requirements.md, spec/design.md, and spec/tasks.md, plus steering guidance to coordinate development end-to-end.

How do I scaffold a spec-driven development directory at my project root?

Run the init command at your project root to scaffold the spec/ and steering/ directories, establishing the foundational structure for generating EARS-based requirements and sequential task plans.

Can I generate sequential task plans linked to my technical design and requirements?

Yes, you can generate two-level sequential task plans linked to requirements and aligned with steering documents, enabling iterative development directly from your technical design content and data models.

Does spec-driven development work without external dependencies or components?

Spec-driven development operates with no external dependencies or components, relying solely on generating EARS-based documents and structured plans from your project intent and steering guidance.