oc-team

/oc-team Command

Manage agent team workspace — scaffold directories, generate SOUL.md templates, validate registry, show team structure.

Arguments

The user provides: $ARGUMENTS

Parse:

• subcommand (required): init, soul, validate, or show
• agent-id (required for soul): lowercase slug identifier for the agent

Subcommands

init

Scaffold the agent team workspace directory structure.

1. Ask the user for the workspace path (default: current directory).
2. Ask for a comma-separated list of agent IDs to create (or use a sensible default like jarvis).
3. Create the directory structure:

WORKSPACE="<path>"
mkdir -p "$WORKSPACE"/{agents,team-memory,clawport}

for agent in <agent-list>; do
  mkdir -p "$WORKSPACE/agents/$agent"/{logs,output}
  touch "$WORKSPACE/agents/$agent/MEMORY.md"
  touch "$WORKSPACE/agents/$agent/SOUL.md"
done

touch "$WORKSPACE/team-memory"/{market-brief,icp-profile,competitor-map,brand-voice,content-calendar}.md
touch "$WORKSPACE/MEMORY.md"

1. Create a starter clawport/agents.json with the first agent as orchestrator (reportsTo: null) and the rest as direct reports.
2. Report what was created.

soul <agent-id>

Generate a SOUL.md template for the given agent.

1. If clawport/agents.json exists, read it to get the agent's name, role, reports-to, and direct-reports.
2. Generate a SOUL.md template using this structure:

# AGENT_NAME -- Role Title

## Identity
I am AGENT_NAME, the [Role Title]. [Describe personality and communication style].

## Expertise
- [Domain 1]
- [Domain 2]

## Operating Rules
- [Constraint 1]
- [Constraint 2]

## Relationships
- Reports to: [Parent Agent] ([Role])
- Manages: [Child agents, if any]
- Collaborates with: [Peer agents]

## Memory
- Persistent knowledge lives at agents/<id>/MEMORY.md
- Daily logs written to agents/<id>/logs/

1. Write the template to agents/<agent-id>/SOUL.md.
2. Tell the user to customize the personality, expertise, and constraints.