sdd

Standardize spec-driven development workflows with a unified command alias.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/hiddink-ai/hiddink-harness --skill sdd-hiddink-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/sdd
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill sdd-hiddink-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the friction in maintaining alignment between technical specifications and implementation by providing a standardized entry point for spec-driven development.

Core Features & Use Cases

  • Workflow Standardization: Provides a unified command to trigger spec-driven development tasks, ensuring consistency across different agents.
  • Alias Integration: Acts as a direct bridge to the primary sdd-dev skill, simplifying command syntax for developers.
  • Use Case: When starting a new feature, use this skill to initialize the spec-driven workflow, ensuring that your implementation remains strictly bound to the defined requirements.

Quick Start

Invoke the sdd skill followed by your task description to initiate the spec-driven development process for your current project.

Frequently Asked Questions about sdd

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

FAQPage Schema
How do I keep my software implementation aligned with technical specifications?

Spec-driven development standardizes execution by binding implementation strictly to defined requirements, ensuring your software engineering project maintains alignment between the initial specification and the final codebase.

How do I standardize spec-driven development workflows across different agents?

You can standardize spec-driven development workflows by using a unified command alias to trigger consistent implementation of technical requirements, ensuring all agents follow the same execution logic across various projects.

What is the best way to initialize a spec-driven workflow for a new feature?

Invoke the unified development alias followed by your task description to initialize the spec-driven workflow, ensuring your feature implementation remains strictly bound to the defined technical requirements from the start.

Do I need the sdd-dev skill module to execute spec-driven development tasks?

Yes, the primary sdd-dev skill module is required as a dependency to execute the underlying development logic, because this skill acts only as a standardized alias bridge to that core module.

Can I use this workflow automation skill for software engineering projects without predefined requirements?

No, this skill requires predefined technical specifications to function correctly, as it is designed to standardize the execution of spec-driven workflows rather than generate the initial project requirements.