Skip to content
0d3sa

Slash commands

Slash commands

Section titled “Slash commands”

The Agentic Team Protocol installs six global slash commands into Claude Code. They are the user-facing control surface for starting, continuing, and governing goals.

Command Purpose
/team Start or continue a goal.
/team-charter Ratify the project charter.
/team-status Show active goals and stages.
/team-escalate Write an escalation record for a blocked or risky goal.
/team-continue Resume an unfinished goal from eden-memory.
/team-handoff Transfer goal ownership to another role.

/team

Section titled “/team”

Top-level entry point. It is intentionally thin: it parses the argument and delegates to the Dispatcher or /team-continue.

Usage

/team
/team <request>
/team <goal_id>

Behaviour

Input Action
No argument Show status and ask for a goal.
UUID-like or contains - Resume via /team-continue.
Any other text Spawn the dispatcher subagent with the request.

Output

  • A goal_record and dispatch_instruction stored in eden-memory.
  • A hand-off to the assigned role subagent.

/team-charter

Section titled “/team-charter”

Reads the project charter and stores a ratification record.

Usage

/team-charter

What it does

  1. Finds .claude/agentic-team-charter.md (project-local) or falls back to ~/.claude/skills/team/CHARTER.md.
  2. Computes a SHA-256 version hash.
  3. Checks for unresolved placeholders and role mismatches with .claude/agentic-team-config.yaml.
  4. Stores a charter_ratification record in eden-memory.

Output

Charter path: .claude/agentic-team-charter.md
Version: <16-char-sha>
Record ID: <uuid>
Status: proceed | no-proceed

/team-status

Section titled “/team-status”

Lists active goals, current stage, owner role, latest record ID, and whether each goal is continueable, blocked, or closed.

Usage

/team-status
/team-status <goal_id>
/team-status <role>

Output columns

Column Meaning
goal_id Stable goal identifier.
stage Current lifecycle stage.
owner_role Role currently responsible.
latest_record_id Most recent durable record.
deadline Dispatch deadline if recorded.
state active, blocked, pending_authorisation, continueable, closed.

/team-escalate

Section titled “/team-escalate”

Writes a structured escalation_record and reports the escalation chain.

Usage

/team-escalate <goal_id: reason and options>

What it captures

  • Goal ID and escalation reason.
  • Consulted roles.
  • Recommended default resolution.
  • Specific question or authority requested.
  • Risk of waiting.

Output

  • An escalation_record in eden-memory.
  • The assigned escalation level (1–4).
  • The next authority in the chain.

/team-continue

Section titled “/team-continue”

Resumes an unfinished goal by reading the latest records from eden-memory and dispatching the correct next role.

Usage

/team-continue
/team-continue <goal_id>

Behaviour by latest record

Latest record Next action
goal_record Route to Dispatcher for dispatch instruction.
dispatch_instruction Route to assigned role.
context_summary Route to Builder or Runtime per plan.
action_record Route to Verifier.
verdict green Route to Archivist for closure.
verdict red/blocked Route to Dispatcher for rework or report blocker.
hand_off_record Route to receiving role.
archival_record (no newer action) Report goal is closed.

Output

  • A run_log continuation record.
  • A hand-off to the next role with the latest context.

/team-handoff

Section titled “/team-handoff”

Transfers ownership of a goal to another role in a durable hand_off_record.

Usage

/team-handoff <goal_id: to_role [reason]>

Required fields

  • goal_id
  • to_role: dispatcher, researcher, builder, runtime, verifier, archivist, or router
  • reason (optional but recommended)

What it copies

The hand-off record copies success_criteria, deadline, and escalation_trigger from the latest dispatch instruction so the receiving role can continue without re-reading the full history.

Output

  • A hand_off_record in eden-memory.
  • The receiving role subagent is spawned with the hand-off payload.

See also

Section titled “See also”