sdd-onboard

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AD-Paladins/beaconator-web --skill sdd-onboard-ad-paladins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-onboard
Source: https://github.com/AD-Paladins/beaconator-web/tree/main/.config/opencode/skills/sdd-onboard
Command: npx skills add https://github.com/AD-Paladins/beaconator-web --skill sdd-onboard-ad-paladins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Learning a spec-driven development (SDD) workflow from documentation alone is abstract and hard to internalize. This Skill teaches the full SDD cycle by executing it live on the user's actual codebase, producing real artifacts and real code changes instead of toy examples. ## Core Features & Use Cases - Guided Full-Cycle Walkthrough: Narrates and executes all SDD phases — explore, propose, spec, design, tasks, apply, verify, and archive — with short explanations of what each step does and why. - Real Change Selection: Scans the codebase for small, low-risk, spec-worthy improvements (missing validation, inconsistent error messages, extractable utilities) and lets the user pick or propose one. - Production-Quality Artifacts: 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 login form" from the suggested options, and ends the session with a complete archived change, updated specs, and working code. ## Quick Start Ask the orchestrator to start the SDD onboarding walkthrough so it can scan your codebase and guide you through a complete spec-driven change.

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 skill through the orchestrator. It scans your codebase for a small, low-risk improvement, then walks you through every SDD phase — from proposal to archive — creating real artifacts and code as it teaches.

What artifacts does an SDD onboarding cycle create?▼

The cycle creates 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. The change is then implemented, verified against the specs, and archived.

What kind of change is suitable for an SDD onboarding session?▼

A good onboarding change is small enough to finish 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 an extractable utility function.

Can I choose my own improvement instead of the suggested options?▼

Yes. The skill presents 2-3 scanned options but lets you suggest your own improvement. It validates that your choice fits the small and safe criteria before proceeding with the cycle.

What happens if tests fail or the design is unclear during onboarding?▼

The skill stops and explains the blocker instead of pushing through. It does not force a broken cycle to completion, since the goal is teaching correct SDD practice on production-quality work.