sdd-dev

Enforce an sdd/ folder hierarchy with planning-first gates for software projects.

13|6|Updated Apr 14, 2026

Search Tags:#workflow #planning #development #spec-driven #artifacts #sdd #gates

Ready to run

npx skills add https://github.com/baekenough/second-brain --skill sdd-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-dev
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/sdd-dev
Command: npx skills add https://github.com/baekenough/second-brain --skill sdd-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-Driven Development (SDD) enforces a consistent folder structure and gating workflow to reduce rework and ensure current-state artifacts are produced and validated before proceeding.

Core Features & Use Cases

Enforced sdd/ folder structure: sdd/01_planning/, 02_plan/, 03_build/, 04_verify/, 05_operate/, 99_toolchain/
Gate-based execution: planning review, plan creation, build state, verification evidence, and optional operate state
Current-state artifacts: artifacts living in place to reflect the current state of work
Guided activation: interactive prompts and checks to ensure requirements are understood before proceeding

Quick Start

Create the sdd/ folder if missing, then run /sdd-dev with your task description to start the guided planning workflow.

Frequently Asked Questions about sdd-dev

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

FAQPage Schema

What is spec-driven development and how does it prevent ad-hoc coding?▼

Spec-driven development prevents ad-hoc coding by enforcing a standard sdd/ folder hierarchy and planning-first gates, ensuring current-state artifacts like planning and execution plans are validated before any build execution proceeds.

How do I set up a planning-first workflow for software projects?▼

To set up a planning-first workflow, create an sdd/ folder structure with 01_planning, 02_plan, 03_build, 04_verify, and 05_operate directories, then run guided activation to enforce gate-based execution and traceable progress.

What's the best way to enforce a planning gate before coding starts?▼

The best way to enforce a planning gate is using a guided activation workflow that requires current-state artifacts in 01_planning and 02_plan directories to pass review before allowing 03_build state execution to begin.

Does spec-driven development work without strict folder structure enforcement?▼

Spec-driven development relies on a strict sdd/ folder structure to maintain current-state artifacts and gate-based execution, meaning without this enforced hierarchy, traceable progress and planning-first gates cannot be guaranteed.

When do I need to produce verification evidence in a gated workflow?▼

You need to produce verification evidence in the 04_verify directory during a gated workflow after the 03_build state completes, ensuring that execution plans and build states are validated before proceeding to optional operate artifacts.