sdd-onboard

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

Updated May 24, 2026
One-click install
npx skills add https://github.com/etrigan16/v0-cipher-ar --skill sdd-onboard-etrigan16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-onboard
Source: https://github.com/etrigan16/v0-cipher-ar/tree/main/.opencode/skills/sdd-onboard
Command: npx skills add https://github.com/etrigan16/v0-cipher-ar --skill sdd-onboard-etrigan16

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams adopting spec-driven development (SDD) often struggle to learn the workflow because tutorials use toy examples instead of real code. This Skill teaches the full SDD cycle by executing it live on the user's actual codebase, producing real artifacts and a real code change. ## 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 at each step. - 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 one. - Artifact Generation: Creates production-quality proposal.md, delta specs with Given/When/Then scenarios, design.md, and tasks.md, then archives the change into the main specs. - Use Case: A developer new to SDD runs the onboarding, picks "add input validation to the contact form endpoint," and ends the session with a complete change folder, implemented code, verified spec compliance, and archived specs. ## 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.

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 onboarding walkthrough, which scans your codebase for a small improvement opportunity and guides you through the full cycle. Each phase — explore, propose, spec, design, tasks, apply, verify, archive — is narrated so you understand what happens and why.

What artifacts does a spec-driven development workflow produce?▼

The workflow produces a proposal.md explaining the why, delta specs with Given/When/Then scenarios defining observable behavior, a design.md documenting decisions, and a tasks.md breaking work into checkable steps. After verification, the change is archived and delta specs merge into the main specs.

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

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 missing loading state.

Does the SDD onboarding skill support test-driven development?▼

Yes, when Strict TDD mode is active the apply phase follows the RED, GREEN, TRIANGULATE, REFACTOR cycle. The failing test is written first, then the minimum code needed to pass it, with each step explained.

When should I not use the full SDD workflow?▼

Skip the full SDD cycle for small tweaks and trivial fixes where agreeing on behavior upfront adds no value. Reserve it for features, APIs, and architecture decisions where specifying what to build before coding prevents rework.