sdd-onboard

Guide developers through a complete spec-driven development workflow for codebase changes.

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?

This Skill helps developers adopt Spec-Driven Development by guiding them through a complete real codebase change instead of leaving the workflow as abstract documentation.

Core Features & Use Cases

  • Full SDD Walkthrough: Leads users through exploration, proposal, specification, design, task planning, implementation, verification, and archival phases.
  • Real Codebase Onboarding: Finds a small, valuable improvement opportunity and creates production-quality SDD artifacts while teaching the process.
  • Use Case: A developer new to SDD can use this Skill to complete their first feature change with clear artifacts, validation steps, and an auditable workflow.

Quick Start

Use the sdd-onboard skill to guide me through a complete SDD cycle on my current codebase.

Frequently Asked Questions about sdd-onboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is spec-driven development and how does it apply to onboarding on a real codebase?

Spec-driven development (SDD) is an engineering process that uses structured artifacts to guide codebase changes. For onboarding, it leads developers through exploration, proposal, specification, design, task planning, implementation, verification, and archival phases to complete a valuable feature change.

How do I start a complete spec-driven development workflow for a new feature change?

To start a spec-driven development workflow, initiate the Skill on your current codebase. It will guide you sequentially through proposal, specification, design, task planning, implementation, verification, and archiving phases to produce production-quality SDD artifacts.

Can I use spec-driven development to find a small improvement opportunity while learning the workflow?

Yes, spec-driven development onboarding is designed to find a small, valuable improvement opportunity in your current codebase. It teaches the process by guiding you through creating real SDD artifacts and validation steps for that specific change.

What is the difference between spec-driven development and test-driven development for software workflows?

Spec-driven development focuses on creating structured artifacts like proposals, specifications, and designs before implementation, whereas test-driven development focuses on writing tests first. SDD provides an auditable engineering process for the entire change lifecycle, including archival.

What phases are required in a complete spec-driven development cycle?

A complete spec-driven development cycle requires structured phase execution including proposal, specification, design, task, implementation, verification, and archive workflows. Each phase produces specific artifacts to ensure the codebase change is auditable and validated.