Orchestrate Attractor Loops

Own the outcome. Treat routing as a manager judgment informed by artifacts, not as a scripted state machine.

Establish authority and proof

1. Read the complete governing specification and repository instructions before delegating.
2. Copy or pin external authority locally when the task requires a stable reference.
3. After context compaction, re-read this skill and the specification sections governing the active phase before doing more work.
4. State observable proof claims. Separate hygiene checks from proof through the running software.
5. Keep designs, reviews, transcripts, and proof under the repository's ephemeral-work path unless another location is prescribed.

Run the design loop

1. Give a fresh author agent the authoritative specification, current repository, constraints, and requested design path. Ask for a complete design, not implementation.
2. Launch an independent reviewer through the repository's agent CLI. Let the CLI select the reviewer; do not name a model positionally.
3. Ask for an unconditional review of the entire current design against its authorities. Do not seed expected findings or protected areas.
4. Read the review artifact. Accept supported material findings, reject incorrect ones with evidence, and send the author a bounded revision assignment.
5. Resume the same reviewer with the full current design and a new output path. Advance only when the reviewer reports no material findings or only nits.