sdd-onboard

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/Alountk/Bloodbowl_Project --skill sdd-onboard-alountk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-onboard
Source: https://github.com/Alountk/Bloodbowl_Project/tree/main/.opencode/skills/sdd-onboard
Command: npx skills add https://github.com/Alountk/Bloodbowl_Project --skill sdd-onboard-alountk

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 production-quality code while explaining each step. ## Core Features & Use Cases - Guided full-cycle walkthrough: Narrates all SDD phases — explore, propose, spec, design, tasks, apply, verify, archive — with short explanations of what and why at each step. - Real change selection: Scans the codebase for small, low-risk, spec-worthy improvements (missing validation, inconsistent error messages, TODO comments) and lets the user pick or suggest their own. - Real artifact generation: Creates proposal.md, delta specs with Given/When/Then scenarios, 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, updated specs, and working code. ## Quick Start Ask the orchestrator to launch the SDD onboarding walkthrough so it can scan your codebase and guide you through a complete spec-driven change from proposal to archive.

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?▼

Launch the SDD onboarding through the orchestrator, which scans your codebase for a small, low-risk improvement and walks you through the full cycle. Each phase from explore to archive is narrated so you understand what each artifact does.

What artifacts does an SDD workflow produce?▼

The cycle 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 with concrete checkable steps. After verification, the change is archived and delta specs merge into the main specs.

What makes a good first change 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 production-quality change, not a demo. It writes actual code during the apply phase, runs verification against the spec scenarios, and archives the change into the artifact store.

When should I not use the SDD onboarding walkthrough?▼

Skip it once you already know the workflow and use the individual sdd-* skills directly for new features. It is also unsuitable for large or risky changes, since onboarding requires small, safe, single-session improvements.