[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-81169":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":15,"stars7d":17,"stars30d":17,"stars90d":16,"forks30d":16,"starsTrendScore":18,"compositeScore":19,"rankGlobal":10,"rankLanguage":10,"license":20,"archived":21,"fork":21,"defaultBranch":22,"hasWiki":23,"hasPages":21,"topics":24,"createdAt":10,"pushedAt":10,"updatedAt":33,"readmeContent":34,"aiSummary":35,"trendingCount":16,"starSnapshotCount":16,"syncStatus":17,"lastSyncTime":36,"discoverSource":37},81169,"opencode-agent-orchestration-kit","jcarlosrodicio\u002Fopencode-agent-orchestration-kit","jcarlosrodicio","Starter kit for OpenCode agent orchestration with product-development workflows, Open Design integration, Superpowers, Docker, and docs.","",null,"JavaScript",31,4,29,1,0,2,3,45.3,"Apache License 2.0",false,"master",true,[25,26,27,28,29,30,31,32],"agent-orchestration","ai-agents","developer-tools","docker","open-design","opencode","product-development","superpowers","2026-06-12 04:01:32","# opencode-agent-orchestration-kit\n\nA starter kit for configuring OpenCode with a product-development agent orchestration flow, Open Design integration, optional Impeccable design context, Superpowers workflow discipline, local process skills, a TUI token-usage plugin, and optional AHE observability sidecars.\n\nThis project is for developers who want a reproducible global OpenCode setup without hand-writing agents, commands, skills, tools, and Docker notes from scratch.\n\nThis repository is not affiliated with OpenCode, Open Design, Impeccable, or Superpowers.\n\n## Architecture\n\nBy default, free-form messages open with `lead` as a bounded router. Lead quickly chooses `developer`, `researcher`, `designer`, or `specifier`, and asks the user when ambiguity changes the correct flow. Small, clear, low-risk changes are usually delegated straight to `developer`.\n\nCore feature flow:\n\n```text\nlead -> designer if applicable -> researcher -> specifier -> developer -> reviewer\n```\n\nScoped research\u002Fspec flow:\n\n```text\nscoper -> researcher -> scoper synthesis -> specifier\n```\n\nPlan-only flow:\n\n```text\nlead -> researcher -> specifier -> reviewer\n```\n\nDesign flow:\n\n```text\ndesigner -> open-design\n```\n\nOptional harness-evolution flow:\n\n```text\nevaluator -> debugger -> evolver -> lead approval -> developer -> evaluator -> debugger -> reviewer\n```\n\nHarness contracts are versioned inside the shipped OpenCode config:\n\n- `opencode\u002FAGENTS.md`: short index for agents.\n- `opencode\u002Fdocs\u002Fai\u002Fharness\u002F`: agent, command, evidence, and check contracts.\n- `opencode\u002Fdocs\u002Fai\u002Fevolution\u002F`: AHE benchmark and evolution records.\n- `opencode\u002Fscripts\u002Fcheck-harness.mjs`: local mechanical validation for the harness.\n- `opencode\u002Fplugins\u002Ftoken-tree-usage.tsx`: sidebar TUI plugin that reports lead\n  tokens and total tokens across child\u002Fsubagent sessions when the OpenCode TUI\n  exposes session children.\n\n## Skills and integrations\n\nIncluded locally:\n\n- `open-design`: shipped in this repo at `opencode\u002Fskills\u002Fopen-design`. It wraps Open Design workbench usage through `OPEN_DESIGN_URL` and the `open_design_*` tools.\n- Process skills under `opencode\u002Fskills\u002F` for source-driven development,\n  testing, debugging, API\u002Finterface design, review, simplification, security,\n  performance, and documentation\u002FADRs. Agents use them as checklists, not as\n  mandatory extra phases.\n\nReferenced from upstream:\n\n- `superpowers`: not vendored in this repo. It is enabled through the upstream OpenCode plugin `superpowers@git+https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers.git`, so OpenCode downloads\u002Floads it from upstream when plugins are supported and network access is available.\n\nOptional, user-installed:\n\n- `impeccable`: not included in this repo. Install it from upstream if you want `designer` to use it when `PRODUCT.md` or `DESIGN.md` are missing.\n\n## Quick install\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fjcarlosrodicio\u002Fopencode-agent-orchestration-kit.git\ncd opencode-agent-orchestration-kit\n.\u002Finstall.sh\n```\n\nThen configure your environment:\n\n```bash\ncp env.example .env\nsource .env\n(cd opencode && npm install)\nopencode auth login\nopencode\n```\n\n## Use without installing globally\n\n```bash\nexport OPENCODE_CONFIG_DIR=\"$PWD\u002Fopencode\"\nexport OPEN_DESIGN_URL=\"https:\u002F\u002Fopen-design.example.com\"\nopencode\n```\n\nThis is the safest way to test the kit before touching your global config.\n\n## Global install\n\n```bash\n.\u002Finstall.sh\n```\n\nThe installer copies agents, commands, skills, and tools to `${OPENCODE_CONFIG_DIR:-$HOME\u002F.config\u002Fopencode}`. It creates a backup when existing files are present. It does not overwrite `opencode.json` or `AGENTS.md` unless you pass `--force`.\n\n```bash\n.\u002Finstall.sh --target \"$HOME\u002F.config\u002Fopencode\"\n.\u002Finstall.sh --force\n```\n\nIf your existing `opencode.json` was preserved, add Superpowers manually. This references the upstream plugin; it does not copy Superpowers into this repository:\n\n```json\n{\n  \"plugin\": [\"superpowers@git+https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers.git\"]\n}\n```\n\nIf your existing `tui.json` was preserved, add the bundled token usage plugin\nmanually:\n\n```json\n{\n  \"plugin\": [\".\u002Fplugins\u002Ftoken-tree-usage.tsx\"]\n}\n```\n\nFor reproducibility you may pin a version:\n\n```json\n{\n  \"plugin\": [\"superpowers@git+https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers.git#v5.0.5\"]\n}\n```\n\n## Models\n\nThe example config reads models from environment variables:\n\n```bash\nexport OPENCODE_MODEL=\"openai\u002Fgpt-5.5\"\nexport OPENCODE_SMALL_MODEL=\"$OPENCODE_MODEL\"\nexport OPENCODE_LEAD_MODEL=\"$OPENCODE_MODEL\"\nexport OPENCODE_DEVELOPER_MODEL=\"$OPENCODE_MODEL\"\n```\n\nSee `env.example` for all role-specific variables.\n\n## Open Design configuration\n\nSet `OPEN_DESIGN_URL` to the base URL of your Open Design workbench.\n\nValid:\n\n```bash\nexport OPEN_DESIGN_URL=\"https:\u002F\u002Fopen-design.example.com\"\nexport OPEN_DESIGN_URL=\"http:\u002F\u002F192.168.1.50:7456\"\n```\n\nInvalid:\n\n```bash\nexport OPEN_DESIGN_URL=\"https:\u002F\u002Fopen-design.example.com\u002Fprojects\u002Fmy-project\"\nexport OPEN_DESIGN_URL=\"https:\u002F\u002Fopen-design.example.com\u002Fprojects\u002Fmy-project\u002Ffiles\u002Findex.html\"\n```\n\nDo not expose Open Design directly to the Internet without authentication, VPN, Tailscale, WireGuard, or a secure reverse proxy.\n\n## Command examples\n\n```text\n\u002Ffeature Create onboarding with plan selection and welcome screen\n\u002Fplan Add a dry-run flag to the harness check without implementing it yet\n\u002Fscope Research Stripe Checkout integration and generate an MVP spec\n\u002Fmvp-spec Email notifications when an agent finishes a task\n\u002Fdesign Read PRODUCT.md and DESIGN.md, create an editable Open Design project, and generate a first version\n\u002Ftest Reproduce the checkout regression with a focused test\n\u002Fcode-simplify Simplify the parser branch without changing behavior\n\u002Freview\n```\n\nWithout a slash command, simple implementation requests go directly through `developer`. Use `\u002Fplan` when you want research, spec, and reviewer feedback without implementation; use `\u002Ffeature` when you want the full orchestration flow.\n\n## Validate the kit\n\n```bash\nnpm run check\n```\n\nThis runs the repository checks plus the harness validator in `opencode\u002Fscripts\u002Fcheck-harness.mjs`.\n\n## Docker Open Design\n\n```bash\ncd docker\u002Fopen-design\ncp .env.example .env\ndocker compose up -d --build\n```\n\nAuthenticate OpenCode inside the container if you want Open Design to use OpenCode as the design engine:\n\n```bash\ndocker exec -it open-design bash\nopencode auth login\nopencode models openai --refresh\nexit\n```\n\nThen set:\n\n```bash\nexport OPEN_DESIGN_URL=\"http:\u002F\u002F192.168.1.50:7456\"\n```\n\n## Security\n\n- Do not commit `.env`, auth files, sessions, logs, or provider credentials.\n- Do not commit private `PRODUCT.md` or `DESIGN.md` files unless intended.\n- Open Design can run local agent CLIs and write files inside project workspaces.\n- Prefer localhost, LAN, VPN, Tailscale, WireGuard, or authenticated HTTPS reverse proxy.\n\n## Troubleshooting\n\n- `OPEN_DESIGN_URL is not set`: export the base URL, not a project URL.\n- `\u002Fapi\u002Fhealth` fails: check Open Design is running and reachable from your OpenCode process.\n- OpenCode does not appear in Open Design agents: run `opencode auth login` and ensure `opencode` is on `PATH`.\n- `crypto.randomUUID` fails on HTTP LAN: use HTTPS or the optional upstream frontend patch described in docs.\n- Superpowers skills do not load: restart OpenCode and verify the plugin line in `opencode.json`.\n- TUI token usage does not appear: verify `tui.json`, run `npm install` in the\n  OpenCode config directory, and restart OpenCode.\n- Designer cannot see Open Design: verify `OPEN_DESIGN_URL`, tool registration, and `opencode\u002Ftools\u002Fopen_design.ts`.\n\n## License\n\nApache License 2.0. See `LICENSE` and `NOTICE.md`.\n","opencode-agent-orchestration-kit 是一个用于配置 OpenCode 代理编排的启动工具包，支持产品开发工作流、Open Design 集成、Superpowers 工作流程、Docker 和文档。其核心功能包括通过预定义的角色（如开发者、研究员、设计师等）来自动选择合适的工作流程，并且提供了清晰的技术架构和详细的技能集成方案。项目采用 JavaScript 编写，适合需要快速搭建可重复使用的 OpenCode 环境而不想从零开始编写代理、命令、技能及 Docker 配置文件的开发者使用。此外，它还支持与外部服务如 Superpowers 和 Impeccable 的集成，进一步增强了项目的灵活性和实用性。","2026-06-11 04:03:46","CREATED_QUERY"]