- Added per-tool usage: when to use OpenCode/OpenSpec directly vs orchestrator
- Direct interaction patterns for manual work
- Clear gate: you review specs before build — critical step
- When to step out of the orchestrator workflow
- Smoother flow diagram
- New module: modules/home-manager/dev-orchestrator/
- Wraps script via writeShellApplication, git as runtime dep
- opencode + openspec already in PATH via existing modules
- Enabled in jpporta-nixos home.nix
After rebuild: dev-orchestrator available in PATH
- cmd_spec now only scaffolds (OpenSpec change + worktree + deps), no auto-fill
- Added cmd_fill as fallback for headless spec filling
- Output guides user to /opsx:explore and /opsx:continue inside OpenCode
- cmd_build (dev→QA loop) unchanged — core value proposition
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Dev Orchestrator
Script + workflow guide para orquestração de desenvolvimento com IA usando OpenCode + OpenSpec + git worktrees.
Arquivos
tooling/dev-orchestrator— script principal (executável)tooling/WORKFLOW.md— guia completo de uso e arquiteturaComandos
dev-orchestrator initdev-orchestrator spec <feature>dev-orchestrator build <feature>dev-orchestrator statusdev-orchestrator clean <feature>Fluxo
Dependências
Zero binários pesados. Apenas:
git(já incluso)opencodeCLI (npm install -g opencode-ai)openspecCLI (npm install -g @fission-ai/openspec)Pesquisa e implementação baseadas na análise de Swarm Tools, Gas Town, git-stint e Vibe Kanban. Caminho escolhido: leve, scriptável, OpenCode-native.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.