Skip to content
0d3sa

Quick start

This tutorial gets the Agentic Team Protocol installed, a project charter ratified, and a trivial first goal dispatched in under ten minutes.

[!TIP] ATP installs per-project inside your Claude Code workspace. Each repository you use it in gets its own .claude/agentic-team-charter.md, .claude/agentic-team-config.yaml, and .claude/skills/agentic-team-protocol/SKILL.md. Read the charter anatomy and the first team goal tutorial for the full workflow.

Prerequisites

Section titled “Prerequisites”
  • eden-memory installed and available on your PATH.
  • Claude Code CLI.
  • A git repository to use as a sandbox.

Step 1 — Install the global primitives

Section titled “Step 1 — Install the global primitives”

Run the installer:

Terminal window
curl -fsSL https://0d3sa.com/agentic-team-protocol/install.sh | sh

This copies the skill, agents, and slash commands into ~/.claude/:

  • ~/.claude/skills/team/SKILL.md
  • ~/.claude/agents/{dispatcher,builder,runtime,verifier,researcher,archivist,router}.md
  • ~/.claude/commands/{team,team-charter,team-status,team-escalate,team-continue,team-handoff}.md

Restart Claude Code completely (/exit, then reopen).

Step 2 — Wire eden-memory for the project

Section titled “Step 2 — Wire eden-memory for the project”

The ATP agents need the eden-memory MCP server to write and read lifecycle records. In your sandbox repo, run:

Terminal window
cd ~/your-sandbox-repo
eden-memory setup claude

This configures the current directory in ~/.claude.json as an MCP project and installs the /eden-* fallback slash commands.

Step 3 — Opt your project in

Section titled “Step 3 — Opt your project in”

Install the project-local ATP templates:

Terminal window
cd ~/your-sandbox-repo
curl -fsSL https://0d3sa.com/agentic-team-protocol/install.sh | sh -s -- --local

This creates .claude/agentic-team-charter.md, .claude/agentic-team-config.yaml, and .claude/skills/agentic-team-protocol/SKILL.md.

Step 4 — Ratify the charter

Section titled “Step 4 — Ratify the charter”

Edit .claude/agentic-team-charter.md and replace the placeholders with your project identity, mission, boundaries, and active roles. Then run:

/team-charter

The command reads the charter, computes a SHA-256 version hash, and stores a charter_ratification record in eden-memory. It reports whether the team may proceed.

Expected output:

Charter ratified for project: your-sandbox-repo
Version: a1b2c3d4e5f67890
Record ID: <uuid>
Status: proceed

Step 5 — Run your first goal

Section titled “Step 5 — Run your first goal”

Run the top-level command with a small request:

/team Add a README file that lists the project purpose and ATP roles

The Dispatcher records a goal_record and dispatch_instruction, then hands off to the Builder. The Builder creates the README and writes an action_record. The Verifier reviews it and writes a verdict. If the verdict is green, the Archivist closes the goal.

Step 6 — Check status

Section titled “Step 6 — Check status”

Run:

/team-status

You should see your first goal listed as closed or recording_and_archival, with links to the latest record IDs.

What next?

Section titled “What next?”