- Home
- Skills
- Workflow Automation
- opencode-agent-team
More screenshots
Works with the AI Agents you already use
Opencode Agent Team
Turn any OpenCode project into a software company in one command — a project-grounded agent team (PM, architect, devs, testers, reviewer, triager, security, devops, writer) with pipeline slash commands. V1+V2 compatible.
$19
opencode-agent-team
Example session with this skill installed
Use the opencode-agent-team skill: init --roles core --lang English
- Read your context and instructions
- Compiled the opencode-agent-team
Explores the repo, confirms the team with 4 questions, then writes: .opencode/agents/{product-manager,architect,backend-dev,test-engineer,code-reviewer,bug-triager}.md (mode: subagent, correct permissions), .opencode/commands/{feature,fix,test-all,prd,adr,review,standup,team}.md, .opencode/agent-team.json, per-role memory dirs, and docs/{PROJECT-CONTEXT.md,TEAM.md,LEARNINGS.md,product/BACKLOG.md}. Fills PROJECT-CONTEXT.md with verified facts (stack, test commands, architecture, red flags), runs --check (frontmatter clean), and reports the roles created, commands available, and the first two commands to try.
Connects securely to your tools. The creator never sees your data.
About this skill
Turn any OpenCode project into a working software company — in one command.
This skill bootstraps a project-grounded agent team inside your repo: subagents (product manager, architect, backend/mobile/web devs, test engineers, code reviewer, bug triager, security, devops, tech writer), pipeline slash commands, a shared context file, and per-role memory. The team is grounded in your project's real code — its stack, its tests, its architecture, its conventions — not generic prompts.
What you get
- 17 roles — pick
core(PM, architect, one dev per stack, test-engineer, code-reviewer, bug-triager) or thefullteam. - 10 pipeline commands —
/feature,/fix,/test-all,/prd,/adr,/security-audit,/release,/standup,/review,/team. - A verified context file (
PROJECT-CONTEXT.md) every agent reads first — the single source of the team's quality, filled from your actual code (stack, test commands, architecture, conventions, hygiene red flags) before any agent runs. - Per-role memory so agents get smarter over time, committed with your repo (no secrets).
Why it's different
The team's quality comes from one rich, verified context file — not from long agent prompts. The skill explores your real code and writes verified facts (not guesses). Every generated agent carries correct OpenCode permission rules: the code-reviewer can't edit, testers can't reach the network, docs-only roles can only touch docs and their own memory.
Compatibility
- V1 + V2 — detects your OpenCode version and emits the right permission format (
permissions:list for V2, legacypermission:map for V1 viacompat_v1). - Any provider — subagents inherit your session model by default, so it works with whatever provider you run. Pin models per tier or per role if you want.
How it works
- Explores your repo (stack, test commands, architecture, conventions, red flags).
- Asks four quick questions (profile, role set, report language, docs location).
- Writes a config and runs a self-contained Python renderer that generates every agent, command and doc.
- Fills
PROJECT-CONTEXT.mdwith verified facts about your project.
After that, mention an agent by name (@code-reviewer review this diff) or run a command (/feature add JWT login). Also supports add <role>, status, and upgrade <role|all> operations. MIT-licensed.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.
Built specifically for OpenCode (not Claude Code, Cursor, or generic agents). OpenCode subagents cannot spawn subagents, so multi-role coordination runs through the slash commands in your main session rather than nested agents. Requires Python 3 on PATH to run the renderer. The skill fills PROJECT-CONTEXT.md from your repo during the exploration step; the depth of that context (and therefore the team's quality) depends on that step being run against a real codebase.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 16 days ago
- Software
- OpenCode V1 or V2
Python 3.8+
Git
OpenCode V1 means 1.x. Python must be on PATH; it uses only the standard library.
Permissions
File Scopes
Runs python3 to render templates into your project. Writes only under .opencode/ and your chosen docs directory. Never reads or writes .env files or secrets, never runs git write commands or deploys, and makes no network calls.