kingdom-orchestrator

Governs the Kingdom development environment through owner-relayed verification and drift control.

Updated May 20, 2026
One-click install
npx skills add https://github.com/TechCorp25/kingdom --skill kingdom-orchestrator-techcorp25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kingdom-orchestrator
Source: https://github.com/TechCorp25/kingdom/tree/main/.claude/skills/kingdom-orchestrator
Command: npx skills add https://github.com/TechCorp25/kingdom --skill kingdom-orchestrator-techcorp25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Multi-session AI-assisted development drifts: undocumented changes, stale branches, unverified fixes, and lost context between chats. This Skill provides the operating manual for a governance layer that keeps the Kingdom environment (knowledge base, policies, .claude/ automation, infra hygiene) consistent through intentional, recorded change only. ## Core Features & Use Cases - Session self-bootstrap protocol: Re-derives environment facts from raw owner-pasted git output, confirms the main tip against the newest continuation baseline, and reconciles drift before any work begins. - Owner-relay operating model: Drafts Claude Code task prompts, decision records, continuation baselines, and handoffs as downloadable files; every irreversible step is owner-gated. - Drift control and intentional change: Enforces additive-only knowledge promotion via _proposals/ plus owner-gated git mv, treats infra/automation diffs as decisions, and distinguishes grep-verified from runtime-verified fixes. - Use Case: At the start of a new chat, the orchestrator reads the newest kingdom-continuation-*.md, asks the owner to paste git fetch and git log output, detects that another committer landed work, and reconciles before delegating the next task to Claude Code. ## Quick Start Start a new chat in the kingdom-orchestrator project and ask it to run the session startup protocol and report the current environment state.

Frequently Asked Questions about kingdom-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent environment drift across multiple AI coding sessions?▼

Use a versioned continuation baseline committed in isolation at every clean boundary, then re-derive live facts from raw git output at each session start. Confirm the main branch tip matches the baseline's expected SHA before doing any work.

How do I delegate tasks to Claude Code safely?▼

Draft each task as a downloadable markdown file with /automate-dev as line one, one task per prompt, and per-sub-task completion gates. Require raw git status and diff output plus a re-run quality gate rather than prose summaries.

Can this orchestrator run terminal commands or access the repo directly?▼

No. The orchestrator has no terminal, git, or network access; the owner is the only relay to the machine. Every irreversible step, including pushes to shared remotes, is explicitly owner-gated.

Why does a green ruff/mypy/pytest gate not prove a fix is correct?▼

A passing gate only proves static checks succeed. Configuration or compose fixes verified only by grep are not runtime-verified, so the caveat must be stated explicitly and carried into the continuation baseline.

What are the limitations of this governance layer?▼

It governs only the shared environment: knowledge base, policies, .claude automation, and hygiene. It never touches a project's application code, and it depends entirely on the owner pasting accurate raw command output.