Holy 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 holy-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 thumb chain — restoration. Router for four aspects: triage (stop digging, snapshot, bracket the breakage), reproduce-and-bisect (make it fail on demand, isolate the cause one hypothesis at a time), heal-and-verify (minimal fix, root-cause proof, postmortem line), and process healing (recovering a derailed loop, skipped gates, bad merges from enlisted agents, delivered breaches). Engage when something breaks — a regression, a red build, corrupted state, or the process itself. Load one aspect file at a time per the Invocation Ritual.
SKILL.md
2.4 KB, as published. Nobody here has run it
Holy Chain — router
Enhancement poured into restoration. It does not make the wound not have happened — it makes the body whole and remembers where the blade entered.
Prime directive: stop digging. The moment breakage is detected, the current activity pauses. Continuing to build on a broken foundation converts one wound into many — most "unrecoverable" states are three reasonable-looking actions past the first wound.
Selection table — read exactly one
| Your situation | Aspect file |
|---|---|
| Breakage just detected — secure the scene before anything else | triage.md |
| Scene secured — make it fail on demand and isolate the cause | reproduce-and-bisect.md |
| Cause isolated — fix minimally and prove the cure | heal-and-verify.md |
| The process broke: skipped gate, bad agent-merge, delivered falsehood, derailed loop | process-healing.md |
Code wounds run the sequence: triage.md → reproduce-and-bisect.md →
heal-and-verify.md. Process wounds go straight to process-healing.md
(which loops back into the code sequence when the process wound left code
damage behind).
Chain-wide laws (apply in every aspect)
- Reversibility before action — from triage onward, every step must be undoable; healing that can't be reverted is a second gamble, not a cure.
- Combat-speed science — hypotheses and predictions still get written before probes (a one-line ledger form exists for exactly this); urgency never suspends the scientific method, it compresses the paperwork.
- Root cause or labeled symptom-patch — the heal claims what it actually is; "it stopped happening" is not "it's fixed".
- Every heal ends in a postmortem line — one structured line; the wound pays for a lesson or it was pure loss.