skills.rest
CarlosWilliamsR
CarlosWilliamsRCOMMUNITY
Explore all skills by this author →
GitHub

sdd-onboard

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

Updated Aug 25, 2026
Search Tags:#workflow#onboarding#codebase analysis#tutorial#spec-driven development#openspec#walkthrough
One-click install
npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill sdd-onboard-carloswilliamsr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-onboard
Source: https://github.com/CarlosWilliamsR/SketchOS/tree/main/.config/opencode/skills/sdd-onboard
Command: npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill sdd-onboard-carloswilliamsr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Learning a spec-driven development (SDD) workflow is hard when examples are toy projects disconnected from real work. This Skill teaches the full SDD cycle by executing it on the user's actual codebase, producing real artifacts and real code changes. ## Core Features & Use Cases - Guided Full-Cycle Walkthrough: Narrates each SDD phase — explore, propose, spec, design, tasks, apply, verify, archive — with short explanations of what and why. - Real Change Selection: Scans the codebase for small, low-risk, spec-worthy improvements (missing validation, inconsistent errors, TODOs) and lets the user pick. - Production-Quality Artifacts: Creates 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 runs the onboarding, picks "add input validation to the signup endpoint," and ends the session with a complete archived change and merged specs. ## Quick Start Ask the orchestrator to launch the SDD onboarding walkthrough so it can scan your codebase and guide you through a complete change cycle.

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 on my own codebase?▼

Run the sdd-onboard walkthrough, which scans your codebase for a small, low-risk improvement and guides you through the full SDD cycle. Each phase is narrated so you understand what each artifact does while producing a real change.

What artifacts does an SDD change produce?▼

An SDD change produces a proposal.md explaining the why, delta specs with Given/When/Then scenarios defining the what, a design.md documenting decisions, and a tasks.md breaking work into checkable steps. After implementation and verification, the change is archived and specs are merged.

What kind of change is suitable for SDD onboarding?▼

A good onboarding change is small enough to complete in 30-60 minutes, low risk with no breaking changes or migrations, and spec-worthy with at least one requirement and two scenarios. Examples include missing input validation, inconsistent error messages, or a clear TODO comment.

Does the onboarding skill make real code changes?▼

Yes, it implements a real change on your actual codebase, not a demo. The artifacts and code must be production-quality, and the cycle stops and explains if tests fail or the design is unclear.

When should I not use the full SDD workflow?▼

Skip SDD for small tweaks where you can just code directly. Use it for features, APIs, and architecture decisions where you want to agree on what to build before writing code.

Related Skills

Explore More Software Engineering Skills→
AD-PaladinsAD-Paladins

sdd-onboard

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

Community
Advanced
EduardoJVNEduardoJVN

sdd-archive

Merge delta specifications into main specifications and archive completed change folders.

Community
Advanced
Gentleman-ProgrammingGentleman-Programming
6.1k

sdd-onboard

Guides users through a complete Spec-Driven Development cycle on their real codebase.

Official
Advanced
udecodeudecode
1.2k

creating-pr

Create or update GitHub pull requests with conventional commits.

Official
Intermediate