emperor-scope · diff

v0.3.0 to v0.3.0

1 added, 1 removed. Audit A to A.

---

name: emperor-scope

description: >-

Emperor Time — SCOPE / take-the-task. Quote the client, surface ambiguity,

dowse repo evidence, write G0+G1. Use when the ask is vague, the user says

find work, scope this, take this task, or before any design. Loads Dowsing

Chain, not a substitute for it.

license: MIT

metadata:

version: 0.3.0

chain: dowsing-chain

---

# Emperor Scope (Dowsing wrapper)

This skill does **not** replace Dowsing Chain. It is the phase trigger.

1. Read `chains/dowsing-chain/SKILL.md` (router only).

2. Select **one** aspect: `task-dowsing.md` | `system-dowsing.md` | `lie-detection.md`.

3. Quote the client verbatim into `.emperor/tasks/<id>/ledger.md` from `templates/task-ledger.md`.

4. Write checkable acceptance criteria and an out-of-scope list (G1).

5. Run `scripts/gate.sh g0 <task-dir>` then `scripts/gate.sh g1 <task-dir>`. Quote the tails.

6. If the client has not chosen among options, stop and ask — do not invent scope.

Invocation Ritual still applies: router → one aspect. Record the aspect path in the ledger.

- Ask→spec before setup thrash: `scripts/emperor ask-spec --emit "<ask>" --write .emperor/tasks/<id>/ask-spec.md` (HARD-GATE `--reject-no-spec` / `--require-spec` / `--check-ask-spec`). G0 calls `--require-spec` — setup without a written spec FAILS. SessionStart MUST emits; omitting effort_class still gets tiny hard caps. Harness tool+force: `scripts/emperor harness-plan --emit --from .emperor/tasks/<id> --write .emperor/tasks/<id>/harness-plan.md` (HARD-GATE `--reject-no-plan` / `--require-plan` / `--check-harness-plan` / `--check-forbidden` / `--check-allowed`). G0 calls `--require-plan` — harness selects tools/caps/forbidden from effort_class; G4 enforces Forbidden (`FORBIDDEN_TOOLS_NEVER_RUN`) and Tools∪Optional allowlist (`ALLOWED_TOOLS_ONLY`); tiny forbids excavate/sandbox/critique museum.

+ Ask→spec before setup thrash: `scripts/emperor ask-spec --emit "<ask>" --write .emperor/tasks/<id>/ask-spec.md` (HARD-GATE `--reject-no-spec` / `--require-spec` / `--check-ask-spec`). `--write` chains idempotent `harness-plan.md` emit from stamped `effort_class` (one mechanical path — no second `harness-plan --emit` CLI). G0 calls `--require-spec` / `--require-plan` — setup without a written spec/plan FAILS. SessionStart MUST emits; omitting effort_class still gets tiny hard caps. Standalone `scripts/emperor harness-plan` remains for re-emit/checks (HARD-GATE `--reject-no-plan` / `--require-plan` / `--check-harness-plan` / `--check-forbidden` / `--check-allowed`). Harness selects tools/caps/forbidden from effort_class; G4 enforces Forbidden (`FORBIDDEN_TOOLS_NEVER_RUN`) and Tools∪Optional allowlist (`ALLOWED_TOOLS_ONLY`); tiny forbids excavate/sandbox/critique museum.