sdd:init

/sdd:init does two things, both optional and idempotent:

1. Scaffold — create the .sdd/ folder for project-wide context (principles, ADR storage, config).
2. Adopt — incrementally bootstrap Layer 1 living specs from an existing codebase, one area at a time.

You can stop after the scaffold. Adoption is never forced, never whole-repo, and safe to re-run — it only adds new areas and never overwrites a spec you've reviewed.

Shared Instructions

• Layered Context — living-spec paths, the resolver script (lib/scripts/resolve-spec-paths.py), tier files, and the domains registry.

Steps

1. Detect state

Check the project root for: .sdd.json, .sdd/principles.md, .sdd/decisions/, and whether .sdd.json already has a domains map.

• If the scaffold artifacts are missing → first run: do Phase 1, then offer Phase 2.
• If they all already exist → already initialized: skip Phase 1 and go straight to Phase 2 (adopt another area).

---

Phase 1 — Scaffold (Layer 0)

Build a list of only the artifacts that don't exist (never overwrite). If the list is empty, say ✓ .sdd/ already initialized and go to Phase 2.

1. Present via AskUserQuestion: Create all / Customize / Cancel. (Customize → ask per-artifact yes/no.)
2. Create the chosen artifacts:
   • .sdd.json (only if absent): minimal default

     { "specsDir": "specs", "commitFormat": "conventional", "noAttribution": true }
     

   • .sdd/decisions/.gitkeep (empty file so git tracks the folder).
   • .sdd/principles.md — ask via AskUserQuestion how to seed it:
     • Blank template — copy lib/templates/principles.md verbatim.
     • Infer from codebase — spawn one subagent: read lint/format/test/build config (e.g. eslint, prettier, tsconfig, package.json scripts, CI files), CLAUDE.md, and the folder layout, then draft 5–10 candidate project MUSTs in the principles.md bullet shape. Ground every rule in something it actually saw; mark anything uncertain for the user. Show the draft; the user confirms/edits before you write the file.
3. Output the created files.