Skip to main
MDCC-RDM/00THE ROADMAP75 shipped, 0 in flight, 6 queued

Roadmap.

Every phase, past and planned. Source of truth lives in .ai/plans/ and .ai/state/STATE.md. This page regenerates on every build.

All phases.

83 units · regenerated 2026-06-18

Shipped

  1. [x]MDCC-RDM/canvas-chromFeature: Canvas-shell chrome follows the Maude theme + per-artboard theme override

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is a risky dev-server refactor (repoints CSS custom-property sources across the w...

  2. [x]MDCC-RDM/canvas-figjaFeature: Canvas viewport — FigJam-grade direct-manipulation feel

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

  3. [x]MDCC-RDM/client-tree-Client tree restructure — sidecar nesting, DS-primary section, hidden-files toggle

    Restructure the dev-server sidebar (the FILES panel at app.jsx:273–365) so it stops drowning daily work in non-canvas noise:

  4. [x]MDCC-RDM/comment-layeFeature: Shell-owned comment layer (comments in bare specimens)

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — this touches the canvas mount harness and canvas-lib, which are load-bearing for ever...

  5. [x]MDCC-RDM/decouple-floFeature: Decouple flow plugin from GitHub issues (generic issue-tracker abstraction)

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

  6. [x]MDCC-RDM/dependency-fFeature: Dependency freshness sweep + Biome v2 / Motion v12 major migration

    Land every outstanding dependency bump across the pnpm workspace (., site, plugins/design/dev-server, plugins/design/hub) and the side projects (plugins/design/hub bun.lock, scripts/video/final), s...

  7. [x]MDCC-RDM/design-systePlan: Design system bootstrap workflow (skill `design-system` bootstrap mode) + multi-DS + docs sync

    This plan converts the retro at .ai/logs/system-reviews/design-system-bootstrap-review.md (R1–R6) into sequenced work, plus folds in the multi-DS portion of the old Phase 5 (Tasks 2–7) since multi-...

  8. [x]MDCC-RDM/dev-server-sFeature: Dev-server system view — bias-free token + type rendering

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

  9. [x]MDCC-RDM/export-pipelFeature: Export pipeline fixes — 6 bugs (size, chrome leak, selection/artboard scoping, SVG bg, HTML artboard, PPTX validity)

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan touches the export pipeline that was just hardened (graceful Playwright-miss...

  10. [x]MDCC-RDM/feature-annoFeature: Annotation tooling polish — text unification, theme-aware ink, dashed shapes, highlighter

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is a dev-server change to the FigJam-style annotation system — the standing rule...

  11. [x]MDCC-RDM/feature-annoFeature: Annotations FigJam-parity v3 + bidirectional AI loop

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This phase again touches the most load-bearing dev-server file (apps/studio/annotation...

  12. [x]MDCC-RDM/feature-docsFeature: docs-site MDCC-DSN/01 follow-ups

    Surfaced during /flow:done closeout of feature-docs-site-mdcc-skin on 2026-05-15. The parent feature shipped (commits 78d9d8f + 94b4e77) with 0 hard-blockers in scenario-runner but DS-guard + a11y-...

  13. [x]MDCC-RDM/feature-docsFeature: Docs Site — MDCC-DSN/01 re-skin

    Validate canvas + fumadocs source before implementing. Token names, fumadocs --fd-* slots, and Berkeley/JetBrains fallback chain are authoritative — don't paraphrase them.

  14. [x]MDCC-RDM/feature-drawFeature — Draw animation: keyframe IR (authoring) + Lottie-from-code (web+mobile delivery)

    tracks on any node) is the cross-platform animation source; maude is its editor (/design:draw + motion utils). It extends the DDR-067 single-source invariant from static geometry to time. (alias /d...

  15. [x]MDCC-RDM/feature-hub-Feature: Hub sync cold-start safety + honest status — "link & it just works"

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. *This touches the sync hot path (apps/studio/sync/) — the standing rule applies: inven...

  16. [x]MDCC-RDM/feature-in-aFeature: In-app "What's New" + guided tour for the Maude UI

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — mirror ai-banner.tsx, build-roadmap.mjs, and the HelpModal in client/app.jsx rather t...

  17. [x]MDCC-RDM/feature-runtFeature: Maude runtime restructure — extract dev-server + hub out of `plugins/design/` into top-level `apps/`

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, the binary-resolution path (DDR-009/045/084), the maude design <verb> dispatcher (DDR-062), npm files ship...

  18. [x]MDCC-RDM/feature-studFeature: Studio — full functionality + design parity (Plan C, completes DDR-096)

    Validate docs and codebase patterns before implementing. Pay attention to the canvas-origin split (DDR-054 — in-iframe overlays are untrusted; structural changes there carry the runtime-health "par...

  19. [x]MDCC-RDM/feature-studFeature: Studio UI redesign — rewrite the dev-server browser shell into the maude Design System (per `Studio.tsx`)

    Validate docs and codebase patterns before implementing. Pay attention to the canvas-origin split (DDR-054 — the in-iframe overlays are untrusted, treat them differently from the shell), the CSS la...

  20. [x]MDCC-RDM/fix-binary-oFeature: fix-binary-oxc-parser-binding

    Keep oxc-parser. Work around a Bun 1.3.4+ regression in --compile NAPI native-binding embedding by setting NAPI_RS_NATIVE_LIBRARY_PATH from a Bun-embedded asset path before oxc-parser loads. Per-ta...

  21. [x]MDCC-RDM/hub-admin-reFeature: Rework Hub Admin UI according to Sync Hub Admin design

    Validate design files and existing IDs before implementing. Every JS-referenced ID must be preserved verbatim.

  22. [x]MDCC-RDM/hub-redesignFeature: Hub admin redesign — maude-DS reskin + additive operator console ("Studio Hub")

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan reskins + extends the EXISTING hub admin SPA — it does not build a new app....

  23. [x]MDCC-RDM/12Phase 12: In-canvas direct edit — CSS + text + Layers panel

    Three direct-manipulation capabilities on the already-shipped Inspector substrate, so small tweaks don't need a /design:edit "<feedback>" AI round-trip:

  24. [x]MDCC-RDM/12.2Phase 12.2: In-canvas CSS panel — proper UX

    ---

  25. [x]MDCC-RDM/16Feature: Intro video v4 — total rebuild, scene-by-scene visual iteration

    ---

  26. [x]MDCC-RDM/17Feature: Docs site infographics + diagrams

    Add a small library of diagram primitives to the docs site and insert them into the highest-traffic pages. Today the docs are text-heavy markdown tables — accurate but visually flat. Adding SKU-sta...

  27. [x]MDCC-RDM/20Feature: Canvas Undo / Redo (Cmd+Z / Cmd+Shift+Z)

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports (DDR-045 paths, DDR-013 module layout, DDR-048 input-router classify table).

  28. [x]MDCC-RDM/21Phase 21 — Annotation vocabulary expansion (FigJam-feel)

    Today the annotation toolkit ships pen / rect / ellipse / arrow / text (anchored only) / eraser. Real review workflows that the user keeps reaching FigJam for need three things we don't have:

  29. [x]MDCC-RDM/22Phase 22 — Annotation brief-board → `/design:new` ingest

    Today a canvas is born from a text brief (/design:new "<name>" "<brief>"). There is no way to start from a blank surface, sketch intent with sticky notes / text / arrows, and then ask Claude to rea...

  30. [x]MDCC-RDM/23Phase 23 — Canvas media: drag-and-drop images + paste-link chips

    The user wants to drop images onto the canvas (drag a .png from Finder, or paste from clipboard) and paste links that render as a preview chip (favicon + title) — the FigJam move where reference ma...

  31. [x]MDCC-RDM/24Feature: Annotations FigJam-parity polish v2 (Phase 24)

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This phase touches the most load-bearing dev-server file (annotations-layer.tsx, 2755...

  32. [x]MDCC-RDM/25Feature: `design:draw` — principle-grounded SVG generation agent + deterministic geometry engine

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. The load-bearing prior art for this whole feature already lives in the repo: plugins/d...

  33. [x]MDCC-RDM/3.6Phase 3.6: Canvas format — `.tsx` over single-file HTML (`data-cd-id` ready)

    Replace the current canvas format — single-file HTML with inline <style> (~50 KB hand-rolled CSS) + <script type="text/babel"> JSX + React 18 UMD + Babel-standalone UMD, reference canvas weighing 7...

  34. [x]MDCC-RDM/3.7Phase 3.7 — `/design:setup-ds` hardening + motion subsystem unification

    Two interlocked workstreams, one phase, because the visual-sanity gate (workstream A) is the same screenshot pass that catches the motion regressions workstream B prevents — splitting them would re...

  35. [x]MDCC-RDM/3.7.1Feature: setup-ds hardening round 2 — reconciliation, aspiration bar, restraint

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is plugin-internal spec/prompt engineering (markdown skills + commands + template...

  36. [x]MDCC-RDM/6.5Phase 6.5: Canvas export (UI-first, multi-format, scope-aware)

    A first-class export feature surfaced from the canvas UI (not just CLI). One dialog covers seven formats × four scopes:

  37. [x]MDCC-RDM/8Phase 8: Live collaboration foundation (multi-tab + hub-ready)

    Lay down the Yjs runtime, Awareness protocol, and persistence layer that Phase 9 needs — and as a side-effect, enable multi-tab collab on a single machine: two browser tabs (or two Claude Code inst...

  38. [x]MDCC-RDM/9Phase 9 (v1.1): Self-hostable hub + bidirectional file sync — THE collaboration story

    Make collaboration usable across the internet without exposing anyone's laptop, without requiring SaaS, without making contributors learn Yjs / PartyKit / Hocuspocus. Three pieces:

  39. [x]MDCC-RDM/9.1Phase 9.1: Unblock linked-mode sync for the TSX-only canvas format

    Three strategies were weighed for "make .tsx sync safe":

  40. [x]MDCC-RDM/9.2Feature: Rock-solid shared collaboration doc — converge the two per-canvas Y.Docs into one

    Linked-mode collaboration today keeps two separate Y.Doc instances per canvas in the dev-server and reconciles them through a side channel (disk files + wholesale-replace relays). That side-channel...

  41. [x]MDCC-RDM/phase-a-depsPhase A — `maude doctor`: deps preflight + config health + quality gates

    ---

  42. [x]MDCC-RDM/phase-b-orchPhase B — Orchestration speed: parallel fan-out + batch tool calls + lazy-load skills

    ---

  43. [x]MDCC-RDM/phase-c-sidePhase C — Sidecar cache + Monitor + background work

    ---

  44. [x]MDCC-RDM/redesign-docFeature: Redesign the docs site → "Studio Docs" (maude DS)

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This re-skins the live site/ Fumadocs app to match the approved maude-DS Studio Docs c...

  45. [x]MDCC-RDM/rename-md-clFeature: Rename `maude` → `Maude` (project-wide brand migration)

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. The four key decisions are baked in below — do not re-litigate them mid-execution.

  46. [x]MDCC-RDM/security-ageFeature: Security review agents (suite) — `security-auditor` + `ethical-hacker`

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports in plugins/flow/.

  47. [x]MDCC-RDM/security-disFeature: User-facing security disclaimer in the docs

    Add a user-facing "Is maude safe?" page to the docs site that explains the threat model honestly: what runs where, what's trusted vs untrusted, and the mechanisms that make each mode safe. Audience...

  48. [x]MDCC-RDM/setup-ds-aesFeature: setup-ds aesthetic-ambition axis (rozbít single-accent funnel)

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is a spec/infrastructure change to the design plugin's bootstrap flow — pure mark...

  49. [x]MDCC-RDM/setup-ds-mooFeature: setup-ds — moodboard direction gate + Batch-A hero preview (fail-fast on direction)

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan changes the design-plugin bootstrap spec (markdown skill + command docs + re...

  50. [x]MDCC-RDM/setup-ds-pasFeature: Setup-DS — 3-stage discovery (Vision → Research → Refinement) inspired by Pastier

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. The 3-stage architecture below is load-bearing — do not collapse stages, do not reintr...

  51. [x]MDCC-RDM/setup-ds-rouFeature: setup-ds Round-2 — scaffold-integrity gates + dev-server boot/export hardening

    The moodboard direction gates catch a disliked direction before the scaffold. They do not catch a scaffold that ran but produced silently-broken output — empty files trusted as written, a transpile...

  52. [x]MDCC-RDM/1Phase 1: Contribute infrastructure + Changesets bootstrap

    Establish the contribution baseline: documented "how to contribute" path, GitHub repo hygiene (PR / issue templates, branch protection docs, Dependabot), basic CI quality gates beyond version parit...

  53. [x]MDCC-RDM/3Phase 3: `integrations.changelog` + `/flow:release-changelog` + `/flow:release` (downstream-reusable)

    Productize release-note + release-cut hygiene as a reusable flow capability. Add a new integrations.changelog block to .ai/workflows.config.json (provider + scope + releaseGuide path), implement th...

  54. [x]MDCC-RDM/11Phase 11: Flow ↔ Design integration

    Close the gap between flow and design plugins. Flow commands (/flow:plan, /flow:done) become aware of .design/ — /flow:plan automatically detects canvases relevant to a feature and pulls them into...

  55. [x]MDCC-RDM/2Phase 2: Docs site (Fumadocs)

    Stand up a public documentation site under site/ using Fumadocs — a Next.js-based MDX docs framework chosen because its output is AI-readable (clean MDX in repo, indexable via crawlers + LLM tools)...

  56. [x]MDCC-RDM/13Feature: Canvas Activity Overlay — live "agent works here" indicator

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — the dev-server is Bun-authoritative (DDR-009), the canvas lib is single-source in plu...

  57. [x]MDCC-RDM/13Phase 13: Flow command categorization (strict prefix naming, no subfolders)

    Reshape the 29 /flow:* commands (26 existing + 3 Phase 3 additions: help, release-changelog, release-cut) so every command except daily-use ones carries a group prefix. Result:

  58. [x]MDCC-RDM/13Phase 13 — Stable element IDs + canonical screenshot pipeline + cheap helpers

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

  59. [x]MDCC-RDM/14Feature: design-system-keeper agent + pattern-priors envelope + token-usage doctrine

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports in plugins/design/agents/, plugins/design/commands/, and .design/system/project/.

  60. [x]MDCC-RDM/3.4Phase 3.4: Dev-server architecture refactor (performance pre-cleanup)

    Refactor the dev-server's shell to a build-pipeline-driven, Bun-runtime-authoritative architecture targeting concrete performance budgets. Concretely: migrate server source to Bun.serve / Bun.file...

  61. [x]MDCC-RDM/3.5Phase 3.5: Dev-server UI/UX refresh — shell visuals only

    Two-part scope:

  62. [x]MDCC-RDM/3.6.1Phase 3.6.1 — Canvas envelope hygiene + reusable canvas-lib + HMR + DS specimens as TSX

    Make every TSX canvas — UI mock OR DS specimen — a fully self-contained, browser-loadable canvas backed by a small shared canvas-lib (@mdcc/canvas-lib, virtual-module-resolved at the dev-server lev...

  63. [x]MDCC-RDM/4Phase 4: Canvas v2 — infinite-canvas engine inside the canvas runtime

    Today every .tsx canvas under .design/ renders inside its iframe as a static TSX flow — DCArtboard is a labeled card that participates in normal document flow. Phase 4 turns DesignCanvas into a tra...

  64. [x]MDCC-RDM/4.0.5Phase 4.0.5: canvas-lib + perf-lab single source in dev-server

    Implements DDR-025. The current architecture (DDR-022) treats canvas-lib as project-owned source that gets scaffolded into <designRoot>/_lib/canvas-lib.tsx on first /design:setup-ds. That design ha...

  65. [x]MDCC-RDM/4.1Phase 4.1: FigJam-style canvas interactions

    Add a FigJam-equivalent input layer to canvas-lib's DesignCanvas as an opt-in inputMode prop:

  66. [x]MDCC-RDM/4.2Phase 4.2: Free-form artboard repositioning

    Make artboards spatially editable on the infinite canvas:

  67. [x]MDCC-RDM/15Feature: Video pipeline toolchain — setup + smoke tests

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

  68. [x]MDCC-RDM/15.1Feature: Video pipeline infrastructure — Remotion-native workspace + skills + caption + regression harness

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

  69. [x]MDCC-RDM/15.5Feature: Marketing demo — real green-field onboarding lifecycle (~60s primary + 30s tight cut)

    Produce two 1920×1080 H.264 MP4s — site/public/demo.mp4 (primary, ~60s, embedded in the docs landing) and site/public/demo-30s.mp4 (tight cut for the GitHub README, < 10 MB) — by:

  70. [x]MDCC-RDM/15.5Feature: Marketing demo video v2.1 — real maude in sandbox, single perfect cut

    Produce one MP4 at site/public/demo.mp4 (~90 s, single cut, < 16 MB post-loudnorm) by composing 16 scenes on top of phase-15.1 infrastructure (nested workspace, <TransitionSeries>, <TerminalFrame>...

  71. [x]MDCC-RDM/5Phase 5: Draw / annotation tools for the dev server

    Toolbar buttons in canvas chrome: pen, circle, arrow, eraser, color picker. Drawing happens on a transparent SVG layer sized to the canvas world (zoomable with viewport from Phase 4). On stroke com...

  72. [x]MDCC-RDM/5.1Phase 5.1 — FigJam-style annotation overhaul

    Rework annotations-layer.tsx from a self-contained pointer-claiming overlay into a portal-rendered layer that lives inside .dc-world (so the world's CSS zoom/translate moves the strokes natively, w...

  73. [x]MDCC-RDM/6Phase 6: In-place comments UX (FigJam-style bubbles)

    Replace the current shell-bound BottomBar composer with a FigJam-grade in-place comment experience: the composer pops up at the click location on the canvas (not in a panel chrome at the bottom), p...

  74. [x]MDCC-RDM/18Feature: Bias-free design plugin templates

    Validate the docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — this plan refactors load-bearing bootstrap contracts (design-system skill ↔ templ...

  75. [x]MDCC-RDM/19Phase 19 — Dev-server first-boot bootstrap fixes

    Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Planned

  1. [ ]MDCC-RDM/26Phase 26 — Native Maude: Tauri shell + sidecar lifecycle

    Validate docs and codebase patterns before implementing. Pay attention to the binary-resolution path (DDR-009/084), real-disk paths (DDR-045), canvas-origin split (DDR-063), and the canvas-origin g...

  2. [ ]MDCC-RDM/27Phase 27 — Native Maude: In-UI git layer

    Validate docs and codebase patterns before implementing. Pay attention to canvas-create.ts security pattern, canvas-origin-gate.test.ts, DDR-045 disk paths, and the vocabulary map (Save version / P...

  3. [ ]MDCC-RDM/28Phase 28 — Native Maude: GitHub identity & remote

    Validate docs and codebase patterns before implementing. Pay attention to the OAuth token never landing in _server.json or .design/, DDR-045 disk paths, and the canvas-create.ts security pattern fo...

  4. [ ]MDCC-RDM/29Phase 29 — Native Maude: Onboarding wizard + repo/branch switcher

    Validate docs and codebase patterns before implementing. Aspiration bar applies — this is the first-impression surface; /design:new with --perfect is mandatory before Task 2.

  5. [ ]MDCC-RDM/30Phase 30 — Native Maude: Live multiplayer + artboard locking + hub realignment

    Validate docs and codebase patterns before implementing. Read DDR-054, DDR-064, DDR-063 and the 3-lane collab model in collab-model-design.md before touching any sync/collab code. The no-break exha...

  6. [ ]MDCC-RDM/32Phase 32 — Native Maude: Distribution, auto-update & maintenance

    Validate docs and codebase patterns before implementing. MAUDE_SKIP_RUNTIME_BUILD=1 discipline is load-bearing throughout this phase — never let a CI step regenerate the committed runtime bundles.

Icebox

  1. [*]MDCC-RDM/7Phase 7: ACP local chat sidebar — ICEBOX (deferred, v1.1+ if validated)

    Embed a chat sidebar directly in the canvas chrome that speaks the Agent Client Protocol (ACP). The sidebar can connect to a locally-running Claude Code session (or any ACP-compatible agent) so the...

  2. [*]MDCC-RDM/31Phase 31 — Native Maude: ACP sidepanel (de-icebox phase-7)

    Validate docs and codebase patterns before implementing. Read the existing phase-7 plan (.ai/plans/phase-7-acp-chat-sidebar.md) in full — this phase executes it largely as-written with the native-s...