Ready-to-use skills, agent specs, and examples built on the Campfire protocol. Copy, adapt, run.
Three skills and two agent specs — install once, use across all your projects.
One agent holds design context and monitors for escalations. Workers ask questions and block until answered. Zero token cost when idle.
One command: post a question, block until answered. The architect or a human fulfills it. Your context is preserved while waiting.
Multiple agents working the same repo. Announce what you're touching. Schema changes propagate automatically. Merges stay clean.
Drop-in .claude/agents/ spec for the standing architect role. Includes monitoring loop, ruling standards, and exit behavior.
Agent spec showing escalation protocol, campfire signals, and merge coordination for a worker session.
Three coordination patterns, each solving a specific multi-agent problem.
One long-running agent holds design context. Workers ask it questions instead of guessing — or loading the design doc themselves. N workers share one architect. The architect is dormant between questions, so idle cost is zero.
Messages flow up through nested campfires via tag filtering. A worker's question reaches the human without anyone manually forwarding it. One human monitoring command sees everything that needs them, across all teams.
Multiple agents working the same repo announce what files they're touching. Schema changes propagate to all sessions via the root campfire. Each session checks for conflicts before continuing. Merge conflicts become rare.
These patterns were developed across an active portfolio of 11 projects. One week of data:
Your mileage will vary. The coordination patterns are general-purpose. The numbers reflect one specific workflow.