← ClaudeAtlas

adopt-ruleslisted

Invoke ONLY when the user explicitly asks to install / adopt editable copies from workflow-toolbox into their config, or to check adopted copies for updates. Two managed sets — the cross-cutting RULE files (the delegation ladder) and the pilot AGENT-definition copies (pilot / pilot-watchdog / pilot-orchestrator, whose project copies enable the watchdog observer pairing that plugin-installed agents can't). E.g. "adopt the delegation rules", "install the workflow-toolbox rules as editable files", "install project copies of the pilot agents", "adopt the pilot watchdog into this project", "check my adopted workflow-toolbox rules/agents for updates". Writes versioned, fingerprinted, editable files ONLY on explicit request — never automatically. Re-invoke to detect stale copies (installed version behind the plugin) and refresh them. Not for authoring workflows (workflow-composer) or composing a pilot wave (pilot-wave).
home-dev-lab/workflow-toolbox · ★ 1 · AI & Automation · score 64
Install: claude install-skill home-dev-lab/workflow-toolbox
# adopt-rules — install editable copies of workflow-toolbox's guardrails and pilot agents This skill writes **editable, versioned copies** of workflow-toolbox material into the user's project, on explicit request only. It manages two sets: - **rules** — the cross-cutting guardrail rule files, SOURCED from the plugin's `rules/` bundle (every `*.md` there except `README.md` — currently the delegation ladder; the set is exactly what the plugin bundles and grows with it, the mirror of how the agents set sources `agents/`). **Until adopted, these rules are NOT in force.** A plugin's `rules/` directory is inert — nothing loads it into a session. The only ambient injection is a `SessionStart` hook that emits a SIX-LINE digest of the delegation ladder alone; every other rule in the set (proportionate verification, ground-truth verification, answer-first reporting, memory hygiene, checkpointing, task tracking, …) reaches a session ONLY as a copy this skill writes into a real config dir. Adopting is therefore what puts them in force — not merely what makes them editable. - **agents** — project copies of the pilot delegation suite's agent definitions, SOURCED from the plugin's `agent-templates/` bundle (`pilot.md`, `pilot-watchdog.md`, `pilot-orchestrator.md`, `pilot-orchestrator-watchdog.md`). These templates are deliberately NOT plugin-registered agents — current Claude Code versions do NOT honor the `observer:` frontmatter for a plugin-installed agent, so