sdd-onboard

Guides users through a complete spec-driven development cycle on their real codebase.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Balthael/ciberbal-ai --skill sdd-onboard-balthael
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-onboard
Source: https://github.com/Balthael/ciberbal-ai/tree/main/internal/assets/skills/sdd-onboard
Command: npx skills add https://github.com/Balthael/ciberbal-ai --skill sdd-onboard-balthael

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New users of spec-driven development (SDD) often struggle to understand how the full workflow fits together, from exploration to archiving. This Skill teaches the entire SDD cycle by executing a real, small improvement on the user's actual codebase, narrating each phase so users learn by doing rather than reading documentation. ## Core Features & Use Cases - Guided End-to-End Walkthrough: Runs all SDD phases (explore, propose, spec, design, tasks, apply, verify, archive) with short narrated explanations of what each step does and why. - Real Change Selection: Scans the codebase for small, low-risk, spec-worthy improvements such as missing input validation, inconsistent error messages, or TODO comments, and presents options for the user to choose. - Artifact Production: Creates production-quality proposal.md, delta specs, design.md, and tasks.md following the formats of the individual sdd-* skills, then implements and verifies the change. - Use Case: A developer new to SDD launches the onboarding flow; the agent finds a missing loading state in an async component, builds the full artifact set, implements it with TDD narration, verifies against spec scenarios, and archives the change. ## Quick Start Ask the orchestrator to launch the sdd-onboard skill to walk you through a complete SDD cycle using a small improvement in your current codebase.

Frequently Asked Questions about sdd-onboard

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

FAQPage Schema
How do I learn spec-driven development with a hands-on walkthrough?

Launch the sdd-onboard skill through the orchestrator and it will guide you through a full SDD cycle on your real codebase. It selects a small improvement, builds all artifacts, implements the change, and explains each phase as it goes.

What kind of change does the SDD onboarding pick?

It scans the codebase for small, low-risk improvements completable in 30-60 minutes, such as missing input validation, inconsistent error messages, extractable utility functions, or TODO comments with clear intent. You can also suggest your own change if it fits the criteria.

What artifacts does a full SDD cycle produce?

A complete cycle produces proposal.md explaining the why, delta specs with Given/When/Then scenarios defining the what, design.md documenting decisions, and tasks.md with concrete checkable steps. After verification, the change is archived and delta specs merge into the main specs.

Can I stop or adjust the onboarding walkthrough mid-cycle?

Yes, the skill pauses after the proposal phase so you can review and adjust before continuing. If anything blocks the cycle, such as failing tests or an unclear design, it stops and explains rather than pushing through.

When should I use SDD instead of just writing code directly?

Use SDD for features, APIs, and architecture decisions where you want to agree on what to build before writing code. Small tweaks and trivial fixes do not need the full cycle and can be coded directly.