{{ lv.body }}
{{ lv.body2 }}
{{ lv.noteBody }}
Treat the agents like a capable new team, not a magic box. Give clear intent, let the review gates do their job, and read the summaries that come back. The skills handle the how. Your job stays the what and the why.
The agent-org skill installs a complete engineering company: a CTO who sets direction, an assistant who routes work, five department heads who review, ten juniors who build, and one independent Chief Engineer who must approve every change. They talk on real channels with enforced walls: a junior cannot message the CTO, and no agent can touch files outside its department. Click anyone below to meet them.
{{ selAgent.bio }}
Here's what actually happens when you report a bug to James. Step through it. The people involved light up in the chart above.
{{ loopDesc }}
The org talks over three Slack-style channels backed by a tiny database. The separation isn't politeness. It's enforced by code. A junior posting to the executive channel gets rejected, and a guard blocks any agent from editing files its department doesn't own.
Once installed, several skills drive the org for you, from one carefully-reviewed task to a four-lane overnight shift.
Search by name or by what you're trying to do. Click any card for the full briefing: what it does, when to use it, an example you can copy, and what it needs set up first.
{{ sel.what }}
{{ sel.when }}
{{ sel.output }}
Practical walkthroughs for the things the skill pages assume you know: the concepts you haven't met yet, the setups behind parallel and overnight runs, and the judgment calls: models, budgets, which Claude surface to use when.
{{ g.tagline }}
{{ curGuide.tagline }}
{{ sec.body }}