orchestrator-scaffoldlisted

# /orchestrator:scaffold — Project Scaffolding Closes the gap between Phase 1 boot reporting what's missing and the scaffolding actually existing. Handles both scaffolding tiers: the v2.1 lifecycle agent files (six domain specialists) and the v2.2 grounding files (mission.md, brand.md, principles.md — the identity layer that survives compaction). A bare `/orchestrator:scaffold` reads SCAFFOLDING.md, checks what's actually on disk, and presents gaps. The two explicit modes (`lifecycle` and `grounding`) let you skip straight to a specific goal. Sibling to `/orchestrator:update`, which handles config evolution. This skill handles initial setup and gap-filling, not config changes. --- ## Modes ### default — auto-detect what's missing Triggered by: bare `/orchestrator:scaffold` #### Steps 1. Read `~/.claude/projects/SCAFFOLDING.md` to find the project's recorded version. 2. Identify the current project from cwd — derive the project name from the directory name. Match against the registry table. If not found, treat as v0. 3. Derive the memory dir path: replace every non-alphanumeric character in the full path with `-`, prepend nothing. Example: `~/Code/my-app/` → `~/.claude/projects/-Users-yourname-Code-my-app/memory/`. 4. Run the presence check (see Detection Logic section): - Check project root for: `CLAUDE.md`, `DESIGN.md`, `mission.md`, `brand.md`, `principles.md`, `BACKLOG.md` - Check memory dir for: `agent-product.md`, `agent-experience.md`, `agent-craft.md`, `a