sdd-initlisted

# /sdd init — bootstrapping a project Three scenarios, auto-detected: 1. **Greenfield**: empty project, no existing code. Bootstrap from prose. 2. **Import**: project already has source, no `sdd/` yet. Enter **Import Mode** — derive a spec where behavior is clear from source/tests/comments/commits, file the unclear parts to `sdd/.init-triage.md` with concrete Context + Recommendation, write the scaffolding. 3. **Resume**: `sdd/` exists and `sdd/.init-triage.md` has `**Status:** open` items. Enter **Resume Mode** — surface one triage item at a time with refreshed Context. Detect via source-file count (greenfield-vs-import) and presence of open triage items (resume). ## Greenfield — lean two-confirm flow Compresses the old 10-15-turn back-and-forth into two decisions. 1. **Ask for vision** (one free-form question if `$ARGUMENTS` is empty). Confirm what you heard in one sentence. **Then ask for spec flavour** with one question: ``` What kind of spec is this? 1. Technical — REQs may name protocols (OAuth, JWT), vendors (Cloudflare, Stripe), HTTP status codes, performance targets, and user-facing strings. Default for engineering teams shipping software. 2. Business / behavioural — REQs describe observable behaviour only. No protocols, no vendor names, no status codes inside REQs; technical detail lives in documentation/. Pick this when stakeholders read REQs. 3. Custom — set each of the five forbidden-content allowlist flags i