scaffold

# scaffold ## Purpose The "zero to production-ready" orchestrator. Takes a project description and autonomously generates a complete, working project — directory structure, code, tests, documentation, git setup, and verification. Orchestrates 8+ skills in sequence to produce output that builds, passes tests, and is ready for development. <HARD-GATE> Generated projects MUST build and pass tests. A scaffold that produces broken code is WORSE than no scaffold. Phase 9 (VERIFY) is mandatory — if verification fails, fix before presenting to user. </HARD-GATE> ## Triggers - `/rune scaffold <description>` — Interactive mode (asks questions) - `/rune scaffold express <detailed-description>` — Express mode (autonomous) - Called by `team` when task is greenfield project creation - Auto-trigger: when user says "new project", "start from scratch", "bootstrap", "create a new [app/api/lib]" ## Calls (outbound) - `ba` (L2): Phase 1 — requirement elicitation (always, even in Express mode) - `sentinel-env` (L3): Phase 1.5 — environment pre-flight (validate runtime versions, ports, required tools before generating code) - `research` (L3): Phase 2 — best practices, starter templates, library comparison - `plan` (L2): Phase 3 — architecture and implementation plan - `design` (L2): Phase 4 — design system (frontend projects only) - `skill-forge` (L2): when scaffolded project includes custom skills or plugin structure - `fix` (L2): Phase 5 — code generation (implements the plan) - `team` (L...