skills.rest
hiddink-ai
hiddink-aiOFFICIAL
Explore all skills by this author →
GitHub

sdd-dev

Enforce a Spec-Driven Development workflow with a standardized sdd/ folder hierarchy.

1|Updated May 21, 2026
Search Tags:#workflow#development#documentation#spec-driven#verification#sdd
One-click install
npx skills add https://github.com/hiddink-ai/hiddink-harness --skill sdd-dev-hiddink-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-dev
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/sdd-dev
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill sdd-dev-hiddink-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of inconsistent development workflows and missing documentation by enforcing a strict, artifact-based Spec-Driven Development (SDD) process.

Core Features & Use Cases

  • Structured Hierarchy: Automatically manages project requirements, plans, build states, and verification evidence within a standardized sdd/ folder structure.
  • Gate-Based Workflow: Ensures that no code is written without a plan and no task is marked complete without passing verification tests.
  • Use Case: Use this skill when starting a new feature to ensure that requirements are documented, an execution plan is approved, and verification evidence is generated before deployment.

Quick Start

Invoke the sdd-dev skill to begin a new development task by providing a brief description of the feature you wish to implement.

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 enforce software traceability?▼

Spec-driven development enforces software traceability by mandating a strict folder hierarchy for planning, building, and verifying tasks, ensuring requirements and decision records are documented before code implementation.

How do I enforce acceptance criteria and verification gates during a development cycle?▼

You can enforce acceptance criteria by applying gate-based workflow checks that prevent code execution without an approved plan and block task completion until mandatory verification tests generate passing evidence.

Can I use automated gate-checks for architectural consistency in my existing projects?▼

Yes, automated gate-checks can be applied to your existing projects to satisfy architectural consistency requirements by managing requirements, build states, and verification evidence within a standardized folder structure.

How do I start a new feature implementation using a spec-driven workflow?▼

To start a new feature implementation, invoke the workflow with a brief description of your desired feature to automatically generate project requirements, execution plans, and verification evidence directories.

When should I not use a strict artifact-based development workflow?▼

You should avoid a strict artifact-based development workflow for rapid prototyping or experimental tasks where immediate unstructured code execution is required without formal planning, approval gates, or verification evidence.

Related Skills

Explore More Software Engineering Skills→
asermaxasermax
1

init-framework

Initialize katachi framework directories and CLAUDE.md baseline in projects.

Community
Intermediate
jackson2787jackson2787
1

qa

Run tests, lint, and operational-context checks to produce qa-report.md.

Community
Advanced
TonyQ-AITonyQ-AI
9

requesting-code-review

Deploy a sub-agent to review git diffs against defined requirements.

Community
Advanced
ssaattwwssaattww
1

backend-task-quality-loop

Automate backend task, build, and review cycles with quality gates.

Community
Advanced