Run your first team goal
Run your first team goal
Section titled “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.
Prerequisites
Section titled “Prerequisites”- 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:
curl -fsSL https://0d3sa.com/agentic-team-protocol/install.sh | shThe 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:
cd ~/your-sandbox-repoeden-memory setup claudeThis 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.
Step 3 — Opt your sandbox project in
Section titled “Step 3 — Opt your sandbox project in”Install the project-local ATP templates:
cd ~/your-sandbox-repocurl -fsSL https://0d3sa.com/agentic-team-protocol/install.sh | sh -s -- --localThis creates:
.claude/agentic-team-charter.md.claude/agentic-team-config.yaml.claude/skills/agentic-team-protocol/SKILL.md
Step 4 — Edit and ratify the charter
Section titled “Step 4 — Edit and ratify the charter”Open .claude/agentic-team-charter.md and replace the placeholders:
- Set the project name and path.
- Write a one-sentence mission.
- Confirm the default active roles (Dispatcher, Researcher, Builder, Verifier, Archivist).
- Keep Runtime gated unless you intend to run live operations.
Then run:
/team-charterThe 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-repoVersion: a1b2c3d4e5f67890Record ID: <uuid>Status: proceedIf the command reports placeholders or missing guardrails, edit the charter and run it again.
Step 5 — Dispatch a trivial goal
Section titled “Step 5 — Dispatch a trivial goal”Run the top-level protocol command with a tiny request:
/team Add a README file that lists the project purpose and ATP rolesThe /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: builderDeadline: <timestamp>Step 6 — Observe the hand-off
Section titled “Step 6 — Observe the hand-off”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:
- A draft README in your repository.
- A Builder action summary in the conversation.
- A Verifier review that results in
green,red, orblocked.
If the Verifier returns green, the Archivist links the records and closes the goal.
Step 7 — Inspect the durable record
Section titled “Step 7 — Inspect the durable record”Run:
/team-statusThis 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.
Expected final state
Section titled “Expected final state”.claude/agentic-team-charter.mdcontains real project values and has been ratified.- Eden-memory contains at least a
charter_ratification,goal_record,dispatch_instruction,action_record, andverdictfor the samegoal_id. - The sandbox repo has a new README summarising the project.
Next steps
Section titled “Next steps”- Learn how to amend and re-ratify the charter in the Ratify a project charter tutorial.
- Read the lifecycle for the full seven-stage flow.
- Browse the slash command reference to know which command to use when.