Gh agent org

Skill aymandakirgh/ghclaudetoolkit/skills/gh-agent-org

Use when coordinating GrowthHackers' multi-agent company / agent org and the user mentions the agent company, the 14 agents, the build engine, the agent bus, routing work to an agent, or making a structural/organizational decision across the agents. Triggers on "coordinate the agents", "agent org", "14-agent company", "route this to an agent", "update the bus", "agent-ceo", "W1..W13", "BUILD-ENGINE", "AGENT-ORG", "which agent owns this", "checkpoint the agents", "structural decision for the company". Requires reading BUILD-ENGINE.md + AGENT-ORG.md (the bus) before any structural decision, routing to agent-ceo and workers W1–W13, updating the bus, and checkpointing.From its SKILL.md

Install

npx -y skills add aymandakirgh/ghclaudetoolkit --skill gh-agent-org

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.2 KB, as published. Nobody here has run it

gh-agent-org

Coordinate the GrowthHackers 14-agent company: one agent-ceo plus thirteen workers W1–W13. This skill is the protocol for making and recording cross-agent decisions through the shared bus — not for doing a single agent's task.

Read before you decide

Before ANY structural or organizational decision, read the two source-of-truth files:

BUILD-ENGINE.md — how the company builds: the pipeline, the cadence, the rules of operation.
AGENT-ORG.md — the bus: the org chart, each agent's mandate, current ownership, and the running log of decisions/handoffs.

Do not propose a restructure, reassignment, or new initiative without first reading both. Decisions made blind to the bus create conflicts and duplicate work.

Roles

agent-ceo — sets direction, arbitrates between workers, owns structural calls. Route company-level or cross-worker decisions here.
W1–W13 — the workers. Each owns a domain defined in AGENT-ORG.md. Route a task to the worker whose mandate covers it; if it spans several, escalate to agent-ceo to split and assign.

(The human org — Federico CEO, Giacomo CTO, Michelangelo Socio/Sherpa, Ayman builder — sits above the agent org; agents serve that org, they don't replace it. See gh-brand-voice.)

Routing protocol

Classify the request: single-domain task → a specific worker; cross-domain or structural → agent-ceo.
Check ownership in AGENT-ORG.md — who currently owns the affected area? Don't step on an active owner.
Route to the right agent with a crisp brief (goal, constraints, definition of done).
Update the bus — append the decision/handoff to AGENT-ORG.md so the org stays coherent: what was decided, who owns it now, what's expected back.
Checkpoint — record a short state snapshot (what changed, what's in flight, what's next) so the next coordination round starts from truth.

Updating the bus (always)

Every routing or structural decision ends with a bus update. The bus is the single source of truth; an un-logged decision didn't happen. Keep entries short, dated, and attributed to the deciding agent.

Checklist

Read BUILD-ENGINE.md and AGENT-ORG.md before deciding.
Classified the request (worker vs agent-ceo).
Confirmed current ownership; no collision with an active owner.
Routed with a clear brief.
Appended the decision/handoff to the bus (AGENT-ORG.md).
Wrote a checkpoint snapshot.