Opencode Crew

---

🏗️ How the system works

flowchart LR
    U[You] --> T[team lead]
    T --> R[researcher] & P[pm] & A[architect]
    A --> B[backend / engineer]
    B --> Q[qa]
    Q --> D[devops] & W[docs-writer]
    subgraph memory loop
        L[(learnings.md)] -. read before / append after .-> R & P & A & B & Q
    end
    subgraph surveillance loop
        PLG[orchestrator plugin] -->|JSONL telemetry| DB[(telemetry)]
        DB --> OBS[/observe/] --> IMP[improver · /retro] --> CFG[better config] --> PLG
    end

1. You talk to the team lead; it routes work to the right specialist.
2. Every specialist has a learning hook — lessons go to shared learnings.md and get read back before similar future work.
3. The plugin records telemetry on every tool call; /observe and /retro turn that into concrete config improvements.
4. The loop compounds: your team gets measurably better at your stack over time.

📦 What you get

Component	Contents
Agent team	team (lead/router) + 13 specialists: researcher, pm, architect, backend, engineer, qa, devops, marketing, docs-writer, finance, router, cicd, improver
Commands	/orchestrate full pipeline · /parallel fan-out · /headless background runs · /loop goal-driven iteration · /observe telemetry report · /retro self-improvement · /heal self-healing · /ship quality-gate shipping · /multi multi-repo
Skills	context-hygiene, memory-protocol, model-router, tool-poisoning-guard
MCP server	Local orchestrator: telemetry summaries/errors, shared memory, headless task launching
Plugin	orchestrator.ts — JSONL telemetry + injection scanning for every agent
CI template	GitHub Actions workflow with headless agent runs (/ship uses it)
Obsidian config	25 community plugins, AnuPpuccin theme, snippets, tuned settings

🚀 Quick start

Prerequisites: just git — Node.js ≥ 20 and the opencode CLI are installed automatically when missing.

One-liner (Windows PowerShell):

powershell -c "irm https://raw.githubusercontent.com/vaibhavtayade07/opencode-crew/main/bootstrap.ps1 | iex"

One-liner (macOS / Linux):

curl -fsSL https://raw.githubusercontent.com/vaibhavtayade07/opencode-crew/main/bootstrap.sh | bash

Or clone manually:

git clone https://github.com/vaibhavtayade07/opencode-crew
cd opencode-crew
powershell -ExecutionPolicy Bypass -File install.ps1   # Windows
# bash install.sh                                      # macOS / Linux

What the installer does: checks and auto-installs Node.js (via winget on Windows; exact instructions elsewhere) and the opencode CLI (npm, with scoop/choco/curl-script fallbacks), copies everything to ~\.config\opencode\, rewrites machine-specific paths, and runs npm install. For Obsidian:

• Existing vault detected? Used automatically (multiple vaults → you pick).
• Otherwise: .\install.ps1 -VaultPath "D:\MyVault" or .\install.ps1 -SkipObsidian (on macOS/Linux: bash install.sh --vault=/path/to/vault)

Then open a new terminal:

opencode          # start working with the team

Try: "use /orchestrate to build me a tiny URL shortener".

🎨 Make it yours

This kit is a starting point, not a straitjacket:

• Agents — edit prompts in agent/*.md; each is frontmatter + working style.
• Memory — agent/learnings.md starts empty by design; your agents fill it with lessons about your stack.
• Commands — add .md files under command/ with $ARGUMENTS placeholders.
• MCP servers — add entries to the mcp block in opencode.jsonc. Use the __HOME__ placeholder for home-relative paths; the installer rewrites it per machine.
• Permissions — tune the permission block to match your risk tolerance.

🔒 Security

Audited before publishing: no API keys or tokens anywhere, no personal data, all plugin credential fields empty, home paths parameterized via __HOME__. The plugin's injection scanner flags manipulation attempts in tool output. If you fork and add MCP servers, keep secrets out of git; remote/OAuth-based MCPs authenticate per machine.

📄 License

MIT — free to use, modify, and ship.