Quox Dev Bundle
Roadmaps and delivery, built for humans and agents alike
QuoxPlan is the place a dev, human or Claude, goes to answer three questions in under five seconds: what matters now, what is the full context of this stream, and what changed while they were gone.
In plain words
What it is, where it lives, when to reach for it
- What is it
- A roadmap tool for streams of work, with views for humans and an API for agents.
- Where do I use it
- In the dashboard on the QuoxPlan page, and in your terminal through the
quox plancommands. - When would I use it
- When you need to know what matters now, what is blocked, and what changed while you were gone.
- How do I use it
- Run
quox plan focusfor what matters now, or open the Focus view and read the board.
Follow the climb
Every screen below is a real capture of QuoxPlan running against its dummy corpus while the live roadmap migration proves itself. Base camp is the Focus lens. The summit is a terminal.
A focus lens instead of a wall of streams, a dependency-aware timeline instead of hand-drawn dates, and a roadmap agent that briefs instead of dumping JSON.
Walk it through
The dependency-aware timeline, pinned bar by bar.
Same Gantt as the summit view above, walked pin by pin: what the stream count and zoom controls do, what a hover reveals, and the real ROADY exchange sitting beside it.
- 1Always know which roadmap you are inThe breadcrumb reads Home, Developers, QuoxPlan, Quox Strategic, Timeline, naming the exact roadmap and view.
- 2Four views, one Edit toggleFocus, Board, Timeline and Streams sit as tabs beside the roadmap and scope pickers, with Edit and ROADY to the right.
- 3The stream count is stated, not hidden417 streams, hover or click a row to trace its dependencies, with Fit and Normal zoom controls and a day-width slider alongside.
- 4Hover a bar for the detailThe Matrix/Mesh Chat Layer row expands into a tooltip: In progress, 10 to 14 weeks, days 0 to 60.
- 5Ask ROADY whyA real question, why the timeline looks like everything is starting simultaneously, gets an answer citing 68 of 83 streams IN_PROGRESS, 11 BLOCKED, 3 DECISION_NEEDED and 1 NOT_STARTED.
- 6Platform health under the roadmapAEE, AOCL, VOLT, WARD, a 2 Services Down readout, Backups and AI Idle run along the footer while the timeline stays open.
Captured from the real QuoxPlan timeline against the live Quox Strategic roadmap, not a mockup.
What it does
Progressive disclosure, from roadmap to plan.
400 streams should never render at once. QuoxPlan shows less, better, at every level, and says plainly which parts are live today and which are still being built.
Focus-first views
The default lens is what matters now: P0 blockers, decisions needed, blocked streams, and anything stale. A handful of cards, never a wall of 400 streams.
Dependency-aware timeline
A Gantt built from depends_on, priority, and estimated effort. Independent streams stack side by side, dependent streams chain, and a blocked stream flags the edge it is blocking.
Edit mode, governed
One explicit toggle flips a read view into an editable one. Read mode has no mutation affordances at all. Edit mode routes every change through a governed PATCH surface.
Append-only notes and events
Notes are a timeline, not a field an update can overwrite. Every mutation lands in an event log, so a stream's history cannot be silently destroyed again.
ROADY and agent context packs
A roadmap specialist agent in a collapsible rail. Ask for a brief on any stream and get a distilled context pack built for a Claude session, not a raw JSON dump.
CLI and TUI parity
quoxplan list, show, focus, status, note, and plan from a terminal, and a full TUI for browsing without leaving the shell. Every UI verb has a CLI counterpart.Org roadmaps and scope filters
One roadmap per organisation, with divisions and departments as live scope filters: a visible selector narrows every view in place, and streams carry scope targeting.
Evidence integration
Governed mutations emit AEE intents and are witnessed into the evidence chain, so a completed stream carries proof, not just a status flag.
Built the Quox way
A native plugin, not another app to open.
QuoxPlan is a Quox plugin, and Quox plugins dissolve into QuoxCORE. Same rule as every other product on this platform: one nav entry, agent-connected, owner-gated where it matters, and every mutation on the record.
One nav entry
QuoxPlan lives under Developers inside QuoxCORE. No separate app, no inner shell, no second sign-in.
Agent-connected
ROADY sits in a rail beside the view it is discussing, wired straight into the dashboard's agent system.
Owner-gated completion
COMPLETE requires explicit owner confirmation at the API layer, the same HITL gate every governed action in Quox uses.
Every mutation logged
Status changes, phase ticks, plan edits, and reprioritising all land in an append-only event feed, not a changelog nobody reads.
Drive it with Claude
The quoxpert-quoxplan subskill teaches Claude the CLI verbs and the agent tools in one load. The quox plan CLI gives Claude an authenticated command line for roadmap reads and writes. MCP agent tools let a connected Claude read roadmaps and file notes without leaving the conversation.
Where it stands
What's stable, what's still beta
This maturity map is the QuoxPlan repository's own status doc, dated to the 2026-07-25 cutover to the live Quox roadmap.
- The server read and write API, dependency-cycle detection, and the owner-confirmation gate on COMPLETE are all Stable, covered by 219 server tests
- The standalone quoxplan CLI and the quox plan CLI parity are Stable for their covered verb sets
- Focus, Board, Timeline, Streams and edit mode are Beta: a full read-and-edit round trip works, but with only hours of usage against the real roadmap since the 2026-07-25 cutover, and no automated browser test suite yet
- Only mutations through the collector proxy, the dashboard and the quox plan CLI get an AEE envelope and WARD witnessing; the standalone quoxplan CLI and direct server calls are not evidenced
- Division and department scopes are filters only, not an access boundary: any caller who can reach the API can read or write a stream regardless of its scope
- The bare :3107 dev server has no authentication by design; the collector proxy is the only sanctioned access path
Plan the climb. Ship the summit.
QuoxPlan is Dev Bundle product #2, built the same way RepoBrain was: its own service, its own CLI, and a home inside QuoxCORE. It pairs with DoneEngine, the readiness instrument that reads this plan as evidence and says when a stream is actually done: plan owns intent, DoneEngine owns boundaries.
How you get it
In the store today, and in the Dev Suite
QuoxPlan is Dev Suite product number two. Buy it alone, or take the suite it belongs to.
On its own
The roadmap store the whole platform plans against: streams, phases, append-only notes and versioned plan documents, with its own service, its own CLI and a home inside QuoxCORE.
Paired with DoneEngine
QuoxPlan owns intent and DoneEngine owns boundaries: it reads the plan as evidence and says when a stream is genuinely finished rather than merely worked on.