sdd-init

Scan a repository and generate .harness config, spec, and design files.

8|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/zxdxjtu/harness --skill sdd-init-zxdxjtu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-init
Source: https://github.com/zxdxjtu/harness/tree/main/skills/sdd-init
Command: npx skills add https://github.com/zxdxjtu/harness --skill sdd-init-zxdxjtu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initializing a new project for Spec-Driven Development can be error-prone and time-consuming. SDD Init automates the setup by scanning the codebase and creating the foundational documents needed to start a new sprint.

Core Features & Use Cases

  • Auto-detects project type, tech stack, and test framework from repository state.
  • Generates .harness/config.json, .harness/full-spec.md, and .harness/full-design.md reflecting detected state.
  • Provides a guided summary and prompts to start a new feature with the /proposal workflow.

Quick Start

Run the sdd-init skill to initialize the SDD harness for your project and generate the base configuration, spec, and design documents.

Frequently Asked Questions about sdd-init

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

FAQPage Schema
How do I initialize spec-driven development for an existing project?

Spec-driven development setup is automated by scanning your repository to detect the project type and tech stack, then generating baseline .harness configuration, spec, and design documents to guide your sprint.

What files are generated when setting up an SDD harness?

Setting up an SDD harness generates a baseline .harness/config.json, .harness/full-spec.md, and .harness/full-design.md, which reflect the current repository state and detected test framework to prepare for new features.

Do I need to manually configure tech stack settings before generating project specs?

No, you do not need to manually configure tech stack settings because the initialization process auto-detects the project type, tech stack, and test framework directly from the repository state to generate accurate specs.

What is the best way to start a new feature after project initialization?

The best way to start a new feature after project initialization is to use the /proposal workflow, which is prompted automatically after the SDD harness setup completes and provides a guided summary of the project.

Can I use automated spec generation for any repository structure?

Automated spec generation analyzes the repository structure to detect readiness for SDD harness integration, making it suitable for existing projects that need foundational spec and design documents based on detected technology.