super-bootstraplisted

# Super Bootstrap — Public Entry, Thin Orchestrator The single command users invoke. Orchestrates — detect, route, dispatch, integrate — and owns no install procedure itself: scaffolding lives in the generic runway, [`/super-bootstrap:harness-bootstrap`](../harness-bootstrap/SKILL.md). The entry writes no product content and asks no product questions. `overview.md` / `techstack.md` / `backlog.md` are scaffolded by the runway; their product content fills later at GAP-card pickup. ## Orchestration spine 1. **Git-init** if absent (correctness move). 2. **Dispatch the runway** — `/super-bootstrap:harness-bootstrap` (generic, always; it self-detects fresh-vs-sync). 3. **Detect** — are the seed docs substantive? 4. **Greenfield branch** (not substantive) — seed 3 GAP cards via `/super-bootstrap:log`, stop at the resolve gate. 5. **Substantive branch** — gated tier-2 tech curation. 6. **Disclose** — one post-hoc heads-up line (substantive branch; the greenfield branch's resolve gate is its disclosure). ## Git-init (correctness move) If the repo is not a git repo (`git rev-parse --git-dir` fails), run `git init` first. One log line, no gate. ## Dispatch the runway (always) Invoke `/super-bootstrap:harness-bootstrap` via the Skill tool. The runway installs fresh or syncs drift — its own detection — scaffolding CLAUDE.md, skeleton docs, path-scoped rules, core plugin pins, and returns "runway installed/synced + committed." The entry dispatches it unconditionally, so a documented