emperor-require-design v0.3.0A

Immutable. This exact content never changes and is served at /api/v1/blob/e620c886e4e66301.

---
name: emperor-require-design
description: >-
  Emperor Time — REQUIRE + DESIGN. Write acceptance criteria and a fat work
  order a zero-context worker can execute. Use when planning, writing a spec,
  designing an approach, or before any implementation. Pairs with G1/G2.
license: MIT
metadata:
  version: 0.3.0
  chain: judgment-chain
---

# Emperor Require-Design (G1/G2 wrapper)

1. Confirm G0/G1 exist. If not, load `skills/emperor-scope/SKILL.md` first.
2. Read `references/work-order.md` then copy `templates/work-order.md` to
   `.emperor/tasks/<id>/work-order.md`.
3. Every non-trivial task step must include: real paths, exact commands,
   `Expected: FAIL` then `Expected: PASS` strings. No TBD.
4. Fill the Plan header: Goal, Architecture, Tech Stack, Spec,
   Global Constraints, Review Focus (or `none (checked)`). Leaf from
   obra/superpowers writing-plans Plan Document Header — not the whole skill.
5. Rejected alternative is mandatory (one line).
6. Run `scripts/gate.sh g2 <task-dir>` (calls `scripts/lib/work_order.py`)
   and quote the tail before BUILD.
7. Judgment on the design (does the work order match G1?) uses
   `chains/judgment-chain/SKILL.md` → `gatekeeping.md` only.