Ready-to-install multi-agent teams for OpenCode. Pick a team, install it into a project, and start with @team_lead_agent.
中文 | Quick Start | PPT Demo | Teams | What You Get
Open Agent Team is a library of reusable multi-agent teams. Each team packages role prompts, shared quality protocols, delivery standards, and optional skills for one complete workflow.
The goal is simple: make advanced multi-agent collaboration usable in one command.
choose a team -> install it into your project -> open OpenCode -> ask @team_lead_agent
- One-command installation: install a complete team into any OpenCode project.
- Complete deliverables: teams are designed to produce finished output packages, not loose chat notes.
- Reliable workflows: shared protocols define quality gates, source tracing, review loops, and final delivery checks.
- Reusable team library: use built-in teams or register your own local team directory.
- OpenCode-native layout: installs agents, protocols, skills,
AGENTS.md, andopencode.jsoninto.opencode/.
From this repository root:
python -m pip install -e .
agent_team listInstall a team into your project:
agent_team install --name ppt_writer_team --path /path/to/your/projectOpen that project with OpenCode and ask:
@team_lead_agent Create a 15-slide investor deck from the materials in ./materials.
The installer creates:
/path/to/your/project/.opencode/
AGENTS.md
opencode.json
agents/
protocols/
skills/
ppt_writer_team turns source materials, templates, notes, spreadsheets, PDFs, and public research into a complete PowerPoint package:
delivery/final_deck.pptx: editable.pptx, not a static image deck.delivery/speaker_notes.md: presenter notes and talk track.delivery/source_trace.md: source trace for claims and data.deck_spec/deck_spec.json: structured deck plan for review and regeneration.
The team can also extract visual style from an existing PPT template while avoiding unrelated template content reuse.
▶ Click the image to watch the ppt_writer_team demo
Two complete input/output examples are included under examples/ppt_writer_examples:
| Example | Prompt input | Editable deck | Speaker notes | Source trace | Executive summary |
|---|---|---|---|---|---|
| English Van Gogh deck | prompt_input1.txt | final_deck.pptx | speaker_notes.md | source_trace.md | executive_summary.md |
| Chinese Van Gogh deck | prompt_input2.txt | final_deck.pptx | speaker_notes.md | source_trace.md | executive_summary.md |
These examples show the intended end state: a polished editable PPT, a readable talk track, an executive summary, and source-backed trace files that make the deck easier to review and trust.
paper_survey_team helps with research direction surveys, daily paper radar, and single-paper deep reads:
- ranked paper lists with why each paper matters;
- clear metadata, authors, institutions, years, links, and reading priority;
- method lineage, benchmark evolution, key labs, representative people, and unresolved problems;
- single-paper reports covering background, contribution, method, experiments, limitations, and follow-up reading.
The output is built for scanning, filtering, and deciding what to read next.
Engineering teams produce practical artifacts:
- code review findings ordered by severity;
- test plans, unit tests, integration tests, and edge cases;
- bug triage reports with reproduction plans, root-cause hypotheses, fix options, and verification plans;
- architecture maps, ADR-ready design notes, API/data model plans, and implementation roadmaps.
| Team | Use it for | Typical deliverables |
|---|---|---|
auto_research_team |
Automated research loops from topic to reproducible code, experiments, and paper-style report | research plan, code/data manifest, experiment logs, analysis, LaTeX report |
ppt_writer_team |
Editable presentations from materials, templates, and research | .pptx, speaker notes, source trace, deck spec |
paper_survey_team |
Literature surveys, paper radar, and paper deep reads | ranked paper lists, survey report, lineage map, reading path |
paper_writing_team |
Academic writing, related work, manuscript revision, rebuttal | manuscript sections, literature synthesis, review notes, rebuttal strategy |
grant_proposal_team |
Grant proposal packages | proposal, specific aims, budget justification, compliance checklist |
story_team |
High-quality short story creation with revision loops | final story, critique notes, revision trace |
course_creator_team |
Course and lesson package creation | syllabus, lesson plans, assignments, quiz bank, teacher script |
business_plan_team |
Business plans and pitch narratives | business plan, pitch narrative, financial assumptions, risk register |
job_application_team |
Resume, cover letter, outreach, interview prep | tailored resume, cover letter, outreach, interview prep |
code_review_team |
Findings-first code review | review findings, risk summary, test gaps, suggested fixes |
test_generation_team |
Test design from code, bugs, or requirements | test plan, unit tests, integration tests, edge cases |
bug_triage_team |
Logs, stack traces, and issue diagnosis | triage report, reproduction plan, root-cause hypotheses, verification plan |
codebase_onboarding_team |
Understanding unfamiliar repositories | onboarding guide, architecture map, key files, quickstart |
software_architect_team |
Requirements-to-architecture planning | requirements breakdown, architecture, API/data model, roadmap |
iphone_app_team |
iPhone app product/design/engineering handoff | product scope, IA, design system, iOS architecture, QA handoff |
skill_creator_team |
Create reusable skills from user problems, expected outputs, and workflow examples | generated skill folder, validation cases, gotchas, maintenance report |
skills_evolving_team |
Skill design, evaluation, and improvement | reusable skills, evaluation rubric, iteration report |
team_creator |
Create new installable agent teams | new team directory, agents, protocols, skills, validation report |
List teams at any time:
agent_team list
agent_team list --verbose
agent_team list --jsonInstall into the current directory:
agent_team install --name code_review_teamPreview without writing files:
agent_team install --name code_review_team --path /path/to/project --dry-runClean generated OpenCode team files before reinstalling:
agent_team install --name code_review_team --path /path/to/project --clean--clean removes generated .opencode/agents, .opencode/protocols, and .opencode/skills. It keeps other files in .opencode.
Most teams follow this layout:
teams/<team_name>/
README.md
agents/
team_lead_agent.md
*_agent.md
protocols/
quality_protocol.md
delivery_protocol.md
skill_registry.md
skills/
<skill_name>/
SKILL.md
During installation:
agents/*.md -> .opencode/agents/
protocols/*.md -> .opencode/protocols/
skills/* -> .opencode/skills/
The installer also writes .opencode/AGENTS.md and merges .opencode/opencode.json so OpenCode loads the team guidance automatically.
Create a team directory:
my_team/
README.md
agents/team_lead_agent.md
protocols/quality_protocol.md
protocols/delivery_protocol.md
protocols/skill_registry.md
skills/
Register it:
agent_team add --name my_team --path /path/to/my_team
agent_team install --name my_team --path /path/to/projectUpdate or remove it later:
agent_team update --name my_team --path /new/path/to/my_team
agent_team remove --name my_team- Teams use a
team_lead_agentas the default coordinator. - Protocols define mandatory quality and delivery rules.
- Skills provide task-specific methods and scripts.
- Deliverables are named and structured so they can be reviewed, regenerated, or handed off.
- Source-heavy teams emphasize traceability and evidence cards instead of unsupported claims.
This project is released under the MIT License. See LICENSE.
Some bundled skills are adapted from third-party open-source repositories and remain subject to their original licenses. See NOTICE and THIRD_PARTY_LICENSES for attribution and bundled license texts.
