What problem does it solve? Ordo app builds fail when they start from vague requests, because unasked questions become wrong assumptions baked into the architecture. This Skill enforces a structured intake step that pins down exactly what is being built before any blueprint, crate, or code exists. ## Core Features & Use Cases - Structured Questioning: Walks the user through seven requirement areas — purpose, UI, persistence, external systems, local/cloud siting, out-of-scope items, and definition of done — in small focused batches. - Requirements Record: Produces a complete written record stored to the ledger, which the planner gates on before releasing the blueprint step. - Scope Guardrails: Explicitly forbids crate design, scaffolding, and unconfirmed assumptions during intake. - Use Case: A user says "build me an Ordo app that monitors my cameras." Instead of scaffolding immediately, the Skill asks what the UI shows, whether state persists across restarts, and what done looks like, then writes the record. ## Quick Start Ask me the intake questions needed to define my Ordo app before any building starts.
