How do I install the Uads Orchestrator skill?

Run npx skillmds@latest add kayzenroot/uads-orchestrator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Uads Orchestrator safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Uads Orchestrator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Uads Orchestrator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Uads Orchestrator?

KayzenRoot (@kayzenroot) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Uads Orchestrator by kayzenroot — Agent Skill

Name: Uads Orchestrator
Author: KayzenRoot

Uads Orchestrator

UADS orchestrator kernel by NexLabs. Use to inspect a repo, normalize a request into structured intake, call uads plan, dispatch a bounded execution run, collect digest-bound evidence, require independent review, and finalize. Global-first, zero project footprint.

KayzenRoot 4e031ee 9 files · 10.2 KB Updated Sep 17, 2026

File contents

UADS Orchestrator

Host-side semantic protocol for the deterministic UADS kernel. Do not dump the repository into context. Do not call provider APIs from the kernel.

Protocol

Inspect state (uads status, uads inspect, uads resume).
Normalize the user request into schemas/intake.schema.json.
uads plan --intake <file> (preferred) or uads plan --request as fallback.
uads dispatch --session <implementer-session-id> — dirty worktrees block; UADS will not reset/stash/clean. The session is the authoritative implementer identity.
Invoke selected implementation specialist(s) from the Work Order. Edit only NECESSARY scope.
uads verify — binds a change digest. Do not claim gates passed.
Run selected gates in the host terminal. uads evidence record for each selected non-review gate.
On FAIL/BLOCKED: uads failure record then uads diagnose. Treat ranked paths as hypotheses, not verified root cause.
uads assurance start, then distinct reviewer session(s). uads assurance record.
On CORRECTION_NEEDED, return to implementation, re-verify (new digest), and re-review.
uads finalize is the only completion gate. Then uads review if a ZIP is required.

The user should not pick specialists by hand. Routing controls that. Prefer native subagents for isolated reviewer context. If independence cannot be met, record BLOCKED — never self-approve.

Fallback classifier

uads plan --request is a conservative text heuristic. Prefer structured intake.

References

references/ORCHESTRATION-PROTOCOL.md
references/INTAKE.md
references/ROUTING.md
references/RISK-AND-GATES.md
references/CONTEXT.md
references/EVIDENCE.md
references/EXECUTION.md

---name: uads-orchestratordescription: UADS orchestrator kernel by NexLabs. Use to inspect a repo, normalize a request into structured intake, call uads plan, dispatch a bounded execution run, collect digest-bound evidence, require independent review, and finalize. Global-first, zero project footprint.---# UADS OrchestratorHost-side semantic protocol for the deterministic UADS kernel. Do not dump the repository into context. Do not call provider APIs from the kernel.## Protocol1. Inspect state (`uads status`, `uads inspect`, `uads resume`).2. Normalize the user request into `schemas/intake.schema.json`.3. `uads plan --intake <file>` (preferred) or `uads plan --request` as fallback.4. `uads dispatch --session <implementer-session-id>` — dirty worktrees block; UADS will not reset/stash/clean. The session is the authoritative implementer identity.5. Invoke selected implementation specialist(s) from the Work Order. Edit only NECESSARY scope.6. `uads verify` — binds a change digest. Do not claim gates passed.7. Run selected gates in the host terminal. `uads evidence record` for each selected non-review gate.8. On FAIL/BLOCKED: `uads failure record` then `uads diagnose`. Treat ranked paths as hypotheses, not verified root cause.9. `uads assurance start`, then distinct reviewer session(s). `uads assurance record`.10. On `CORRECTION_NEEDED`, return to implementation, re-verify (new digest), and re-review.11. `uads finalize` is the only completion gate. Then `uads review` if a ZIP is required.The user should not pick specialists by hand. Routing controls that. Prefer native subagents for isolated reviewer context. If independence cannot be met, record BLOCKED — never self-approve.## Fallback classifier`uads plan --request` is a conservative text heuristic. Prefer structured intake.## References- `references/ORCHESTRATION-PROTOCOL.md`- `references/INTAKE.md`- `references/ROUTING.md`- `references/RISK-AND-GATES.md`- `references/CONTEXT.md`- `references/EVIDENCE.md`- `references/EXECUTION.md`

Frequently asked questions