LLM-powered platform for roadmap execution, specification authoring, and evaluation.
VisionStudio tracks cross-repository initiatives, roadmap items, and specification quality in one place. It combines a Go CLI and web dashboard (visionstudio) backed by Dolt (a MySQL-compatible, Git-like versioned database) with LLM-as-a-Judge evaluation of specs against workflow rubrics.
| Initiative Definition Specs | Initiative Execution Dashboard |
|---|---|
![]() |
![]() |
| Program Dashboard | Programs and Initiatives Dashboard |
![]() |
![]() |
| Performance Token Dashboard | Performance Token Month View |
![]() |
![]() |
git clone https://github.com/ProductBuildersHQ/visionstudio.git
cd visionstudio
go build -o bin/visionstudio ./cmd/visionstudio
# Bring up the database and web UI together, opens your browser
./bin/visionstudio app startSee Installation and Quick Start for the full walkthrough, including database setup, CLI usage without the browser, and the sibling repos required to build from source.
- ποΈ Programs β Initiatives β Phases β RMIs - Hierarchical tracking of cross-repository roadmap items, with dependencies and progress rollups; programs and initiatives can each be hidden from the dashboard (
visionstudio program hide/initiative hide), with hiding a program cascading to its initiatives - π Reversible Lifecycle - Initiatives move forward one stage at a time (
proposedβ β¦ βclosed) and can reopen to any earlier stage as scope evolves, with lifecycle timestamps cleared for undone stages so history stays truthful - π’ Repositories - Repository catalog with per-repo RMI counts and progress
- π Performance - Token spend and cost tracking by model, initiative, phase, and RMI
- π©Ί Maturity Assessments - Framework-based capability maturity scoring, plus SCALE platform adoption and code-leverage/reuse graphs
- π MCP Server - Stdio server exposing initiatives/RMIs/work assignments to agent sessions
- βοΈ Remote Mode -
--remote <url>runs the same CLI commands and MCP server against a VisionStudio Cloud tenant (visionstudio cloud loginstores the API key); covers the agent-work surface (initiatives, phases, RMIs, dependencies, work claims, evidence, specs)
- βοΈ Spec Viewer - Source and rendered Markdown views per initiative, with PDF export
- βοΈ LLM-as-a-Judge Evaluation - Evaluate specs against workflow rubrics (
structured-evaluation/rubric.Rubric), with per-category findings and next steps - π Workflow Sync - Sync
ROADMAP.mdfiles and spec workflows with the database
βΆοΈ One-command startup -visionstudio app startbrings up the database and web UI together, closing onCtrl-C- ποΈ Database lifecycle -
visionstudio db {init,start,stop,restart,status,commit}for standalone database management - π©Ή Actionable diagnostics - connection failures explain how to fix them (start the database, run migrations, etc.) instead of raw driver errors
- π Serve from anywhere - the web UI is embedded in the binary (
visionstudio ui --address host:port), no separatenpm run devneeded to use it
- π AI Usage Dashboard - Sessions, prompts, commits, AI-assisted %, tool calls, cost, and daily activity/cost charts, sourced from OmniDevX
- π Read-only, disclosure-scoped - VisionStudio never queries the OmniDevX event store directly; it renders whatever devfolio already generated and decided was safe to show
Legacy: per-project spec authoring (Electron desktop app, being phased out)
An earlier surface β the cmd/daemon REST server plus an Electron desktop frontend (desktop/) β covers per-project spec authoring against the VisionSpec methodology directly on the filesystem (no database): dual requirements/implementation methodology selection, AIDLC workflow and document generation, V2MOM cascades, capability stacks, and organization/team settings. It's being superseded by the visionstudio CLI and web dashboard above and isn't under active feature development. See Go Daemon and Frontend for its architecture.
Multiple workflows can be selected, including custom workflows.
Individual specifications with LLM-as-a-Judge evaluations can be viewed.
A list of all findings is provided for easy scanning of all findings.
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β visionstudio binary β
β βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
β β web/ β React + Vite SPA, embedded via go:embed β β
β β β’ Programs β Initiatives β Phases β RMIs β β
β β β’ Repositories, Performance (token spend) β β
β β β’ Spec viewer + LLM-as-a-Judge evaluations β β
β ββββββββββββββββββββββββ¬βββββββββββββββββββββββββββββββββββ β
β β HTTP (same port) β
β ββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββ β
β β cmd/visionstudio β cobra CLI + JSON API β β
β β β’ app/ui/db lifecycle commands β β
β β β’ initiative/rmi/phase/spec/roadmap/maturity commands β β
β β β’ MCP stdio server for agent sessions β β
β ββββββββββββββββββββββββ¬βββββββββββββββββββββββββββββββββββ β
βββββββββββββββββββββββββββΌββββββββββββββββββββββββββββββββββββββ
β pkg/store (Ent)
βββββββββββββββββββββββββββΌββββββββββββββββββββββββββββββββββββββ
β Dolt (MySQL-compatible, Git-like) β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
See Architecture Overview for the full picture, including the type pipeline and the legacy daemon/Electron architecture it's replacing.
- Go 1.26+
- Node.js 20+
- npm
- Dolt (for the database;
visionstudio db init --migratesets it up)
# Clone the repository
git clone https://github.com/ProductBuildersHQ/visionstudio.git
cd visionstudio
# Initialize the database
go run ./cmd/visionstudio db init --migrate
# Run the unified dashboard (frontend + API on one port)
go run ./cmd/visionstudio dashboard --port 9401 --unified
# Or, for frontend hot reload during UI development:
go run ./cmd/visionstudio dashboard --port 9401 # API only
cd web && npm run dev # Vite dev servervisionstudio/
βββ cmd/
β βββ visionstudio/ # Primary CLI + unified daemon
β β βββ main.go # Cobra root, global flags
β β βββ app.go # `app start/status/stop/restart`
β β βββ serve.go # Web UI resolution + address parsing
β β βββ api.go # JSON API handlers, storeβAPI converters
β β βββ db.go # `db` subcommands
β β βββ ... # initiative/rmi/phase/spec/roadmap/maturity commands
β βββ daemon/ # Legacy REST server (being phased out, see README)
βββ pkg/
β βββ apitypes/ # Canonical API types (Go-first type pipeline source)
β βββ store/ # Database layer (Ent-backed, snake_case JSON)
β βββ service/ # Business logic
β βββ reposcan/ # Repository discovery + scanning
β βββ tokens/ # Token spend / cost tracking
β βββ mcpserver/ # MCP stdio server
β βββ remote/ # HTTP store.Store for VisionStudio Cloud tenants (remote mode)
β βββ config/ # Configuration (projects, organization) β shared with cmd/daemon
βββ ent/ # Ent ORM schema and generated client
βββ web/ # Current React + Vite SPA (embedded into cmd/visionstudio)
β βββ embed.go # //go:embed all:dist
β βββ src/
β βββ panels/ # InitiativesOverview, RepositoriesPanel, PerformancePanel, MaturityPanel, etc.
β βββ api/ # Generated types (types.gen.ts) + API client
βββ desktop/ # Legacy Electron app (being phased out, see README)
βββ samples/ # Sample projects (Grafana, Simple)
βββ docs/ # MkDocs documentation
βββ go.mod
VisionStudio is the top layer of the ProductBuildersHQ spec stack
(visionstudio β visionspec); see the
Ecosystem architecture page for how the
layers interact.
- VisionSpec - The contract and the engine: workflow types, schemas, and the embedded 25-workflow library (configs, templates, rubrics), plus scaffolding, LLM synthesis, LLM-as-Judge evaluation, lint/drift/status, and MCP server β all consumed as an imported SDK. specification-workflow-spec, the former standalone home for the contract, was merged into visionspec in v0.16.0 and archived.
- OmniAgent - LLM agent interface
- omnidevx-core - Canonical developer-experience telemetry model, the source of the DevX dashboard's data
- devfolio - Generates the DevX dashboard file VisionStudio renders (
devfolio devx dashboard) - dashforge - Dashboard-IR format the DevX dashboard is rendered from
MIT









