ordo-crate-build

Builds Ordo blueprint crates one at a time with anti-stub and warnings-as-errors gates.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Rekonquest/ordo-pro --skill ordo-crate-build-rekonquest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ordo-crate-build
Source: https://github.com/Rekonquest/ordo-pro/tree/main/default-user-files/skills/ordo-crate-build
Command: npx skills add https://github.com/Rekonquest/ordo-pro --skill ordo-crate-build-rekonquest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When building a multi-crate Rust workspace, the biggest risks are stubbed implementations (todo!/unimplemented!/placeholder returns) that compile but do nothing, and warnings that get silenced to force a green build. This skill enforces a per-crate gate so every crate is genuinely complete before the next one starts. ## Core Features & Use Cases - Sequential crate building: Builds blueprint crates one at a time in topological order, each as a sealed function primitive with frozen inputs and outputs. - Anti-stub gate: Deterministically fails any crate containing todo!(), unimplemented!(), placeholder returns, or commented-out bodies. - Warnings-as-errors policy: Runs cargo check under -Dwarnings, with a single scoped exception for dead_code/unused marked with a tracked // COUPLE: comment recorded as ledger debt. - Use Case: During step 3 of the Ordo pipeline, build each subsystem crate against its frozen ledger contracts, verify it compiles clean and passes its unit check, then record status and COUPLE markers before the planner releases the coupling phase. ## Quick Start Ask the AI to build the next Ordo blueprint crate in topo order, enforcing the anti-stub gate and -Dwarnings policy, and to record any COUPLE markers in the ledger.

Frequently Asked Questions about ordo-crate-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build Rust crates one at a time in a multi-crate workspace?▼

Build each crate in topological order, get it compiling clean and passing its unit check, then move to the next. Do not start crate N+1 while crate N is unfinished, and do not wire crates together during the build phase.

How do I enforce warnings as errors in a Rust build?▼

Set RUSTFLAGS="-Dwarnings" so cargo check itself fails on any warning, making the compile gate inherit the policy for free. The only allowed exception is a scoped #[allow(dead_code)] with a // COUPLE: <consumer-crate> marker tracked as debt.

What counts as a stub in a Rust crate implementation?▼

A stub includes todo!(), unimplemented!(), or unreachable!() standing in for real logic, placeholder returns like hardcoded Ok(()) or Default::default(), and commented-out or silently empty function bodies. Any match deterministically fails the gate.

When is it acceptable to allow dead_code warnings in Rust?▼

Only when a crate is built in isolation and its consumer does not exist yet, and only during the build step. The allow must be scoped, carry a // COUPLE: <consumer-crate-name> marker, and be recorded in the ledger for removal during coupling.

What happens when a crate fails its build gate?▼

The failure routes to ordo-error-router, which decides between bounded autonomous correction and a hard halt. Silencing, stubbing, or working around the failure to force a pass is prohibited because it defeats every downstream gate.