sdd-onboard

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams adopting spec-driven development often struggle to learn the workflow because tutorials use toy examples that never touch real code. This Skill walks users through a full SDD cycle — explore, propose, spec, design, tasks, apply, verify, archive — using an actual improvement in their own codebase, producing real production-quality artifacts. ## Core Features & Use Cases - Guided SDD Walkthrough: Narrates each phase of the SDD cycle (explore → propose → spec → design → tasks → apply → verify → archive) with short explanations of what is happening 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 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 a missing validation on an API endpoint, and ends the session with a complete archived change, merged specs, and working tested 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 a real project?▼

Run the sdd-onboard walkthrough, which scans your codebase for a small improvement and guides you through the full SDD cycle. You produce real artifacts — proposal, specs, design, tasks — and implement, verify, and archive an actual change.

What is the SDD workflow cycle for code changes?▼

The cycle is explore, propose, spec, design, tasks, apply, verify, archive. You investigate the code, write a proposal defining what and why, create testable Given/When/Then scenarios, document design decisions, break work into tasks, implement, verify compliance, and archive the change.

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, genuinely useful, and spec-worthy with at least one requirement and two scenarios. Examples include missing input validation or inconsistent error messages.

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

Yes, you can suggest your own improvement during the codebase analysis phase. The skill validates that it fits the small and safe criteria before proceeding, and stops to explain if the change is too complex for an onboarding session.

Does the onboarding skill support test-driven development?▼

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

When should I not use the SDD onboarding walkthrough?▼

Skip it for trivial tweaks that do not need agreed-upon specs, and for large or risky changes involving migrations or breaking behavior. The walkthrough is designed for small, safe, spec-worthy improvements completable in one session.