@epicsagas/team
AOrg-level agent team designer via `epic team` CLI (cross-project, append-merge). Subcommands: list, show, sync, link, unlink, history. Use when setting up agents, designing teams, or /spec yields 3+ requirements.
Install
agr install @epicsagas/team --target claudeWrites 1 file into .claude/skills/, pinned to git-8fae9319.
- .claude/skills/team/SKILL.md
Document
name: team
description: "Org-level agent team designer via epic team CLI (cross-project, append-merge). Subcommands: list, show, sync, link, unlink, history. Use when setting up agents, designing teams, or /spec yields 3+ requirements."
/team — Agent Team Design
This skill is a thin wrapper around the epic team CLI.
Run in terminal:
epic team
epic team handles the full interactive flow:
- Resolves org (
HARNESS_ORGenv → prompt → default"epic") - Scans the project (tech stack, domain boundaries, key modules)
- Recommends team type and agent composition
- Shows diff if team already exists in
~/.harness/orgs/ - Applies merge strategy (no silent overwrites)
- Copies agents to
.claude/agents/{team}/with## Team Contextinjected
For the full spec see docs/research/team-spec.md.
Other subcommands
epic team list # list teams in current org
epic team show {team} # config + agents + mission
epic team show {team} --playbook # full accumulated playbook
epic team sync {team} # re-copy agents to .claude/agents/
epic team link {team} # attach existing team (skip design)
epic team unlink {team} # remove .claude/agents/{team}/
epic team history {team} {agent} # show .history/ entries
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-8fae931903a72026-07-31