sdd-onboard

Guides users through an SDD onboarding cycle on their actual codebase to implement a small, safe improvement.

2|Updated Jul 29, 2025
One-click install
npx skills add https://github.com/kurojs/EnderDots --skill sdd-onboard-kurojs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-onboard
Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/sdd-onboard
Command: npx skills add https://github.com/kurojs/EnderDots --skill sdd-onboard-kurojs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of uncertainty and missed context when introducing a real, production-quality change by guiding you through an end-to-end SDD onboarding cycle on your actual codebase.

Core Features & Use Cases

  • Real codebase onboarding walkthrough: Leads the user through explore → propose → specs → design → tasks → apply → verify → archive using genuine artifacts and deltas, not a toy example.
  • Small, safe change selection: Helps you pick a narrowly scoped, low-risk improvement that is spec-worthy (clear requirements and multiple scenarios).
  • Inline instructional phases for SDD artifacts: Ensures you produce proposal, delta specs, design, tasks, and the final archive in a consistent format that the next phases can verify.

Quick Start

Ask the orchestrator to start the SDD onboarding for your current codebase and follow the phase-by-phase walkthrough it triggers.

Frequently Asked Questions about sdd-onboard

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

FAQPage Schema
How do I implement a safe codebase change using specification-driven development?

Specification-driven development guides you through selecting, proposing, specifying, designing, implementing, verifying, and archiving a low-risk codebase change using real artifacts like proposal.md and delta specs.

What is the SDD onboarding workflow for an existing software project?

The SDD onboarding workflow walks you through a complete cycle from explore to archive, helping you pick a small, spec-worthy improvement and generate structured artifacts for production-quality implementation.

How do I create structured design and task artifacts for a codebase change?

You create structured artifacts by following inline instructional phases that produce proposal documents, delta specs, design files, and task lists in a consistent format ready for verification.

Can I apply SDD to a real production codebase for a small improvement?

Yes, SDD applies directly to your actual codebase, helping you select a narrowly scoped, low-risk improvement that has clear requirements and multiple scenarios for safe implementation.

Does the SDD workflow pause for approval before implementation?

Yes, the SDD workflow includes safe gating that asks you before continuing past the proposal phase, ensuring you review and approve the specification before any code changes are applied.

When should I not use specification-driven development for codebase changes?

You should avoid SDD for changes that are not spec-worthy, such as large, high-risk modifications lacking clear requirements and multiple testable scenarios for safe incremental improvement.