Agent Team Kit
Scanned@ryancampbell
npx machina-cli add skill @ryancampbell/agent-team-kit --openclawAgent Team Kit — SKILL.md
A framework for self-sustaining AI agent teams.
What This Is
A complete team process kit for OpenClaw agents that enables:
- Self-service work queues — Agents pick up tasks without human bottlenecks
- Clear role ownership — Everyone knows who does what
- Continuous discovery — Work flows in automatically
- Proactive operation — The team runs itself via heartbeat
Quick Start
1. Copy the Process Files
# From your workspace root
cp -r skills/agent-team-kit/templates/process ./process
This creates:
process/INTAKE.md— The 5-phase work loopprocess/ROLES.md— Role definitionsprocess/OPPORTUNITIES.md— Raw ideas/discoveriesprocess/BACKLOG.md— Triaged work queueprocess/STATUS.md— Who's working on what
2. Add Heartbeat Config
Merge templates/HEARTBEAT.md into your existing HEARTBEAT.md:
cat skills/agent-team-kit/templates/HEARTBEAT.md >> HEARTBEAT.md
Or copy it directly if you don't have one yet.
3. Customize Roles
Edit process/ROLES.md to match your team:
- Rename roles to fit your domain
- Add/remove specialized execution roles
- Update the human lead section with your name
The Intake Loop
DISCOVER → TRIAGE → READY → EXECUTE → FEEDBACK
↑ ↓
└──────────────────────────────────────┘
- Discover — Find opportunities (Scout role)
- Triage — Decide what's ready (Rhythm role)
- Ready — Self-service queue (any agent)
- Execute — Do the work (assigned agent)
- Feedback — Learn and spawn new ideas (completing agent)
Core Roles
| Role | Mission | Owns |
|---|---|---|
| Scout 🔍 | Find opportunities | OPPORTUNITIES.md, discovery |
| Rhythm 🥁 | Keep work flowing | BACKLOG.md, triage |
| Harmony 🤝 | Keep team healthy | Unblocking, retros |
| [Human] | Strategic direction | Hard calls, spawning |
Execution roles (spawn as needed):
- Link 🔗 — Builder
- Pixel 🎨 — Designer
- Sage 🦉 — Architect
- Echo 📢 — Voice
- Spark ✨ — Creative
Key Principles
Self-Service
If it's in Ready, any agent can pick it up. No approval needed.
Clear Ownership
Every phase has ONE owner. No ambiguity.
Always Log
Ideas, discoveries, completions — if you don't log it, it didn't happen.
Spawn, Don't Solo
Main agent coordinates. Sub-agents execute. Don't do everything yourself.
File Structure
process/
├── INTAKE.md # How the loop works (reference)
├── ROLES.md # Who does what
├── OPPORTUNITIES.md # Raw discoveries (anyone adds)
├── BACKLOG.md # Triaged work (Rhythm maintains)
└── STATUS.md # Current activity (self-updated)
HEARTBEAT.md # Proactive check triggers
Heartbeat Integration
Add to your heartbeat checks:
### Team Health (run hourly)
- [ ] OPPORTUNITIES.md stale? → Spawn Scout
- [ ] Ready queue empty? → Alert Rhythm
- [ ] Active work stuck >2h? → Nudge owner
- [ ] Any unresolved blockers? → Harmony
The heartbeat keeps the loop spinning even when the human isn't watching.
Customization
Adding a New Role
-
Define in
ROLES.md:- Mission (one sentence)
- Owns (what they're responsible for)
- Cadence (how often they work)
- Outputs (what they produce)
-
Update the ownership matrix
-
Add spawn criteria in
INTAKE.mdif needed
Changing the Loop
The 5-phase loop is flexible. Adapt it:
- Add validation gates between phases
- Split EXECUTE into parallel tracks
- Add approval checkpoints (if your domain requires it)
Anti-Patterns
❌ Human manually adds every task → Use triage role instead
❌ Waiting for permission to pick up work → Ready = fair game
❌ One agent does everything → Spawn specialists
❌ Ideas stay in heads → Log to OPPORTUNITIES.md
❌ Heartbeat just returns OK → Actually check the loop
Metrics (Optional)
Track team health:
- Cycle time — OPPORTUNITIES → DONE
- Queue depth — Items in Ready (healthy: 5-15)
- Stale items — Days since last triage
- Spawn rate — Sub-agents created per day
The system runs itself. Your job is to trust it.
Overview
Agent Team Kit provides a complete process framework for OpenClaw agents to operate without bottlenecks. It enables self-service work queues, clear role ownership, continuous discovery, and proactive operation through a heartbeat system. The kit ships with predefined files (INTAKE, ROLES, OPPORTUNITIES, BACKLOG, STATUS) plus a heartbeat integration to keep the loop alive.
How This Skill Works
Agents populate OPPORTUNITIES.md through discovery, Rhythm handles triage and backlog, Ready allows self-service task selection, and Execute completes work with assigned agents. A heartbeat mechanism triggers proactive checks to spawn opportunities, nudge owners, and keep the loop spinning, while roles such as Scout, Rhythm, Harmony, and various execution roles coordinate across the five-phase intake loop.
When to Use It
- When you want self-service work queues with no human bottlenecks
- When you need clear ownership defined for each phase and task
- When you require continuous discovery and automatic work-flow ingestion
- When you want proactive operation using a heartbeat to sustain the loop
- When you aim to spawn new ideas and expand roles as needed
Quick Start
- Step 1: Copy the Process Files from skills/agent-team-kit/templates to ./process (INTAKE.md, ROLES.md, OPPORTUNITIES.md, BACKLOG.md, STATUS.md)
- Step 2: Add Heartbeat Config by merging templates/HEARTBEAT.md into your HEARTBEAT.md or creating one if missing
- Step 3: Customize Roles by editing process/ROLES.md to fit your domain and update the human lead
Best Practices
- Define ROLES.md with explicit mission, ownership, cadence, and outputs
- Keep OPPORTUNITIES.md updated with raw discoveries and ideas
- Assign a single owner per each phase to avoid ambiguity
- Configure heartbeat checks to trigger actionable tasks (spawn, nudge, alert)
- Log every idea, discovery, and completion to the corresponding file
Example Use Cases
- A product development squad uses the kit to manage feature work from discovery to delivery with a self-service READY queue
- R&D teams coordinate experiments by continuously logging opportunities and triaging them into BACKLOG
- Customer support automation teams self-manage issue triage and suggested resolutions via OPPORTUNITIES and BACKLOG
- Data engineering workflows use the heartbeat to detect stalled tasks and reassign ownership
- Marketing or content teams spawn specialized roles (Link, Pixel, Sage, Echo, Spark) to execute campaigns