Roadmap
What the system is working on now, what’s queued up next, and where it’s heading after that. A living view of the direction, not a delivery schedule — dates move; the shape of the work tends to hold.
How this page works
The roadmap describes direction, not commitments. Things in Now are actively being built; things in Next are scoped but not started; things in Later are bets that the team agrees are worth pursuing once the near-term work settles.
Priorities shift as consumer needs become clearer. The clearest signal that something should move up is hearing the same gap from multiple product teams — the pilot team (Inform & Engage) drives a lot of what becomes Next here.
Currently in motion
Wave 1 carryovers and one strategic build, side by side: the MCP server kickoff anchors the year, while the Pattern library opens with Empty State and the catalog overview now that pilot teams need composed UI to ship against.
MCP server kickoff
Scoping the MCP server that will expose tokens, components, anti-patterns, and decisions as queryable resources rather than documentation an agent has to scrape. Headline bet for the year — the early work is mapping the schema, choosing where the server lives, and proving the wiring with a single agent client end-to-end.
Pattern library opens
The Patterns Overview and Empty State ship first, framing what a pattern is and giving pilot teams a concrete model to follow. Form Layout, Navigation Shell, and Data Table follow as the catalog fills in.
Editorial export for Ask Hubert
The data file the future conversational mode will consume — JSON schema plus a curated set of voice rules drawn from the Voice & Tone foundation. Once it lands, Ask Hubert can be built against the same source the docs are written from. Wave 1 carryover.
Per-component conformance cards
A short card on every component page listing what conforms, what doesn’t, and which catalog entries were referenced. Wave 1 carryover. Reviewers and agents can defend a component against the same criteria the docs ask for.
Queued up
Scoped, agreed-on, not yet started. Order may shift based on what the pilot team needs, but the shape of each piece is settled.
DS-aware lint plugin
@jmfamily/eslint-plugin-ds, with a stylelint companion. Flags raw hex and pixel values, blocks banned anti-patterns, and warns when a token already exists for the value being inlined. Once a product team installs it, conformance becomes the default rather than the goal of review — the second leverage bet alongside MCP.More component primitives
Tabs, Accordion, Menu/Dropdown, Pagination, Toast, DatePicker, FileUpload, Breadcrumb. Linear effort, but each one unlocks work the pilot team can’t do with the current catalog. Conformance cards and ComponentGuidance ship alongside every addition.
Strategic horizon
Bigger bets where the shape is still being defined. These represent where the system is heading once the Now and Next work settles.
Agent Kit as an npm package
Today the kit ships as a downloadable zip. The next iteration distributes it as
npx @jmfamily/ds-agent-kit updateso consumers can refresh with one command, pin to a known version, and diff against the prior. Natural follow-up once MCP is live and the kit’s role in the consumption flow is settled.Conversational mode (Ask Hubert)
The conversational entry point for the system. Depends on the editorial export landing first; once it does, what the assistant says comes from the same source the docs are written from. Closes the third consumption mode alongside the reference site and the code-facing Agent Kit.
Page templates
Settings, wizard, dashboard, profile — page-level starting points that compose patterns and components into a working screen. Closes the gap between “here are the parts” and “build me this page.”