sdd-onboard

Guide users through a full Spec-Driven Development cycle on their codebase.

1|1|Updated Apr 19, 2026

Search Tags:#collaboration #onboarding #codebase #governance #sdd #artifact #phase-driven

Ready to run

npx skills add https://github.com/RamonsDka/the-architect-overlay --skill sdd-onboard-ramonsdka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-onboard
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/sdd-onboard
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill sdd-onboard-ramonsdka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboard and coach teams through a complete Spec-Driven Development (SDD) cycle by applying it to a real codebase, producing auditable artifacts and aligned changes.

Core Features & Use Cases

Guided end-to-end SDD workflow: Explore, Propose, Spec, Design, Tasks, Apply, Verify, Archive.
Artifact-first onboarding: generates proposal.md, specs, design, tasks, and archive steps to document and audit changes.
Safe, small-change coaching: ensures changes are small, reviewable, and revertible with clear phase gating.

Quick Start

Start an SDD onboarding session with the orchestrator, then follow the phase prompts to complete a full cycle.

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 guide codebase changes?▼

Spec-driven development (SDD) is a phase-driven workflow that guides codebase changes through propose, spec, design, tasks, apply, verify, and archive stages. It enforces phase gating to ensure changes remain small, reviewable, and aligned with auditable artifacts.

How do I onboard my team to spec-driven development using a real codebase?▼

You can onboard your team to spec-driven development by applying an end-to-end SDD cycle directly to your real codebase. This coaching approach generates auditable artifacts like proposal.md, specs, and design docs while enforcing safe, revertible changes.

What is the best way to structure software design artifacts for team collaboration?▼

The best way to structure software design artifacts is using a standardized SDD format that produces proposal, spec, design, and tasks documents. This artifact-first approach ensures team governance, clear evaluation criteria, and repeatable outcomes across the development cycle.

How do I enforce phase gating and safe changes during software engineering onboarding?▼

You can enforce phase gating during software engineering onboarding by following a strict spec-driven development sequence. This requires completing each phase—propose, spec, design, tasks, apply, verify, archive—before advancing, ensuring changes are small and revertible.

Does spec-driven development work without external dependencies or tools?▼

Yes, spec-driven development workflows can operate with no external dependencies. The SDD onboarding process relies entirely on applying phase-driven governance and generating markdown artifacts within your existing codebase environment.

When should I use an artifact-first approach for codebase governance?▼

You should use an artifact-first approach for codebase governance when you need auditable records of changes and clear evaluation criteria. This phase-driven method ensures repeatable outcomes and safe modifications during team onboarding and software engineering collaboration.