What problem does it solve? Autonomous multi-step app builds drift: coders skip verification gates, procedural instructions pile up in context, and build state is lost across sessions. This Skill gives the planner a fixed sequencing spec so an Ordo app is built step by step with enforced gates and durable state. ## Core Features & Use Cases - Six gated build steps: intake, blueprint, crate build, crate couple, test, and launch proof, each with an entry condition and an exit gate that must emit a GateResult Pass before advancing. - Build ledger in persistent memory: stores requirements, versioned blueprints, per-crate and per-wiring status, deferred-debt and COUPLE-marker lists, retry history, and launch proof so builds survive session boundaries. - Skill eviction rule: drops a completed step's procedural text from context only at a passed gate, keeping context flat while outputs persist in the ledger. - Use Case: A planner agent resuming an interrupted Ordo build reads the ledger, confirms the last GateResult Pass, evicts the finished step's skill, and releases exactly the next step skill to the coder. ## Quick Start Use the ordo-build-pipeline skill to plan and advance the next gated step of my Ordo app build.
