Get started

Three paths depending on where you are.

I want to try it now

Clone the repo and scaffold your first pass in 30 seconds.

$ ./scripts/init-domain.sh "Greenfield Clinic" 1

Created: greenfield-clinic/
  ├── pass-1/
  │   ├── domain-specification.md
  │   ├── gap-report.md
  │   └── gap-resolution-log.md
  └── architecture-palette.md

Ready. Write your domain specification, then run the gap report.

View on GitHub

I want to study first

Walk through the veterinary clinic example — three passes, 23 gaps, full resolution rationale.

Try the interactive walkthrough View the raw example

I want to understand the methodology

The blog series covers the problem, the thinking, and the solution.

Post 1 DDD Has a Solo Builder Problem Post 2 Knowledge Crunching Doesn't Need a Room Post 3 The Reactive Path Has No Vocabulary Post 4 Introducing Signal-Driven Development Post 5 The Gap Report: DDD's Missing Feedback Loop Post 6 The Candidate Lifecycle

Read the full series

Frequently asked questions

Is SDD only for DDD?

Yes, the templates use DDD building blocks — aggregates, bounded contexts, events, commands, invariants. SDD is a DDD methodology.

Does it require a team?

No. SDD is designed for solo practitioners. One architect, one specification, one gap report. Teams can use it too, but it doesn't require collaboration.

How long does a pass take?

Pass 1: 2–4 hours. Pass 2: 1–2 hours. Pass 3: 30–60 minutes. Total for a moderately complex domain: a single focused day.

Can I use it with AI assistants?

Yes. The structured templates work well with AI for gap identification. The architect retains decision authority — AI proposes, you dispose.

What if my domain needs more than 3 passes?

That's fine. The three-pass label is the typical trajectory, not a constraint. The invariant is convergence: gap count must decrease across passes.