Dowsing chain
Emperor Time - a full-rigor coding harness skill/plugin: micro-waterfall SDLC gates, scientific-method claim ledgers to cut hallucination, mandatory critique, and consent-based orchestration of other coding agents.
npx -y skills add arbi-elezi/emperor-time --skill dowsing-chainAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Emperor Time's ring-finger chain — intuition made procedure. Router for three aspects: task dowsing (find your own work from repo evidence), system dowsing (scan the machine for counterpart coding agents), and lie detection (flag contradictions between what is said and what is observed). Use when asked to "find your own tasks", scope vague work, or "see what agents are on this machine". Load one aspect file at a time per the Invocation Ritual.
SKILL.md
2.5 KB, as published. Nobody here has run it
Dowsing Chain — router
The pendulum doesn't guess. It swings toward what is actually there.
Dowsing looks like intuition from the outside. Inside, it is a disciplined sweep: every candidate task and every detected agent must be backed by observed evidence. You may not invent work. A dowsed task with no evidence behind it is a hallucination wearing a pendulum.
Selection table — read exactly one
| Your situation | Aspect file |
|---|---|
| "Find something worth doing" / vague goal to scope / between tasks with standing self-assign authority / triaging a codebase | task-dowsing.md |
| Building the enlistable-agent roster / "what agents are on this machine?" / pre-Steal-Chain scan / an unknown CLI needs profiling | system-dowsing.md |
| A source contradicts another (docs vs code, comment vs behavior, agent claim vs observation, memory vs terminal) and you must rule | lie-detection.md |
Multiple situations at once → run them as separate selections in sequence (task dowsing often triggers lie detection; finish the sweep, then rule on the contradictions it surfaced).
Chain-wide laws (apply in every aspect)
- Evidence per swing — every finding cites a quote, a
file:line, or a command output captured this session. "Seems like" findings are discarded before they reach any report. - Read-only chain — dowsing observes; it never fixes, installs, or signs in. Anything worth changing becomes a task candidate for the client (or the waterfall), never an in-place edit "while scanning".
- One artifact per session — a dowsing run ends in exactly one output (candidate table / roster / ruling), recorded in the ledger. An unrecorded sweep is lifespan spent on nothing (Vow 6).
- Skipped probes are declared — inapplicable or unrunnable probes are listed as skipped in the artifact, so absence of findings is never mistaken for absence of problems.