Skip to content

Run your first team goal

This tutorial walks through the shortest complete ATP lifecycle: install the global primitives, opt a project in, ratify its charter, and run a goal that is recorded, built, and handed off in eden-memory.

  • eden-memory installed and on your PATH.
  • Claude Code CLI.
  • A local git repository you can use as a sandbox (nothing will be pushed).

Step 1 — Install the global ATP primitives

Section titled “Step 1 — Install the global ATP primitives”

Run the installer:

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

The installer 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) so the new commands and agents appear.

Expected result: After restart, the command palette accepts /team-charter and /team-status.

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. If eden-memory is not on your PATH, use the full path to the binary.

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
  • .claude/skills/agentic-team-protocol/SKILL.md

Open .claude/agentic-team-charter.md and replace the placeholders:

  1. Set the project name and path.
  2. Write a one-sentence mission.
  3. Confirm the default active roles (Dispatcher, Researcher, Builder, Verifier, Archivist).
  4. Keep Runtime gated unless you intend to run live operations.

Then run:

/team-charter

The command reads the charter, computes a SHA-256 version hash, and stores a charter_ratification record in eden-memory.

Expected output:

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

If the command reports placeholders or missing guardrails, edit the charter and run it again.

Run the top-level protocol command with a tiny request:

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

The /team command spawns the Dispatcher subagent. The Dispatcher records a goal_record and a dispatch_instruction in eden-memory, then hands off to the Builder.

Expected output:

Goal recorded: goal-atp-first-goal-<id>
Dispatch: builder
Deadline: <timestamp>

The Builder reads the dispatch instruction, creates the README, and writes an action_record in eden-memory. It then hands off to the Verifier.

You should see:

  1. A draft README in your repository.
  2. A Builder action summary in the conversation.
  3. A Verifier review that results in green, red, or blocked.

If the Verifier returns green, the Archivist links the records and closes the goal.

Run:

/team-status

This lists active and recently closed goals with their current stage, owner role, and latest record ID. The goal you just ran should appear as closed or recording_and_archival.

  • .claude/agentic-team-charter.md contains real project values and has been ratified.
  • Eden-memory contains at least a charter_ratification, goal_record, dispatch_instruction, action_record, and verdict for the same goal_id.
  • The sandbox repo has a new README summarising the project.