how-agents-work

Explains the Circus model for briefing multiple coding agents from one doctrine source.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill how-agents-work-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: how-agents-work
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/circus/skills/how-agents-work
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill how-agents-work-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams running multiple coding agents (Claude Code, Codex) struggle to keep shared doctrine, per-agent instruction files, and plugin adapters consistent, and often misunderstand when a running agent picks up a new or edited skill. ## Core Features & Use Cases - Cross-agent mental model: Explains the author-once-render-per-agent doctrine layer, where shared doctrine plus per-agent specifics produce one instruction file per agent (CLAUDE.md, AGENTS.md). - Skill reload lifecycle: Clarifies that SKILL.md edits in watched directories are picked up live mid-session, while new top-level skill directories and non-SKILL plugin components need a restart or /reload-plugins. - Background agent handling: Documents why claude --resume <id> --bg branches a new session and how claude attach plus /reload-plugins reloads a background agent under the same session id. - Use Case: When building a plugin with Circus, use this skill to decide where knowledge belongs (personal source vs. distributed artifacts) and to run circus plugins build, check, and versions --check before committing. ## Quick Start Ask the agent to explain how Circus briefs multiple coding agents from one doctrine source and whether a newly edited skill requires a session restart.

Frequently Asked Questions about how-agents-work

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

FAQPage Schema
How do I reload a skill in Claude Code without restarting?▼

Edits to SKILL.md in a watched skills directory are picked up live mid-session with no action needed. For other plugin components like hooks or .mcp.json, run /reload-plugins in an interactive session; /reload-skills re-scans skill and command directories.

How do I restart a Claude Code background agent to pick up changes?▼

Use claude attach <session-id> to convert the background agent to interactive, run /reload-plugins, then detach with the left arrow key. Running claude --resume <id> --bg branches a new session instead of restarting in place.

What is the difference between how-plugins-work and how-agents-work?▼

how-plugins-work covers plugin, skill, and marketplace mechanics such as name resolution, manifests, adapters, and caches. how-agents-work covers the Circus orchestration model: shared doctrine, per-agent rendering, runtime activation, and the personal-data boundary.

Does a new skills directory require a Claude Code restart?▼

Yes. A brand-new top-level skills directory that did not exist when the session started is not watched, so it needs a restart or a plugin install at next startup. Edits inside already-watched directories are detected live.

Where should personal doctrine live when using Circus?▼

Personal doctrine, machine-specific paths, and host-specific adapters stay in the user-level source under ${LAICLUSE_HOME:-~/.laicluse}/circus/. Generated targets contain that data only when explicitly configured as destinations, and generated files should never be hand-edited.