Skip to content

Roadmap ​

Source: .usm/system.usm → roadmap

17 shipped · 2 in progress · 1 planned

StatusTitleShipped InTarget DateDescription
shippedVitePress docs integration0.1.02026-06-22usm docs serve and usm docs build with auto-generated sidebar, angle bracket escaping, and index page
shippedReview-quality feature markdown0.1.02026-06-22Flows as numbered steps, contracts as checklists, tests as Given/When/Then, decisions with alternatives
shippedSuppress empty sections in generated docs0.1.02026-06-22No more empty App Services, No UI pages documented, or No risks defined pages
shippedRoles field in system schema0.1.02026-06-22Any project can describe who uses their system and what they need
shippedADR schema enrichment0.1.02026-06-22Alternatives and consequences fields on decisions for proper ADR-style recording
shippedRoadmap with feature links and delivery tracking0.8.2—Roadmap items link to feature specs, show shipped_in version, sidebar dead links fixed, mermaid rendering
shippedConfigurable output paths0.8.2—Generators read output paths from usmconfig.json — no hardcoded .usm-workspace layout
shippedHelp docs reference expansion0.8.2—CLI reference, usage examples, options, and prerequisites rendered in help docs from spec data
shippedMCP write tools0.1.0—draft_feature, update_feature_status — close the spec-first loop so agents can author .usm files
shippedTool-specific rules files0.1.0—Generate .cursor/rules, CLAUDE.md, copilot-instructions.md with spec-first workflow instructions
plannedMarketing site——Next.js + shadcn landing page at usm.dev with spec-first workflow story
shippedUser docs composed from personas and journeys0.9.0—Personas and journey flows (actor/surface) as first-class spec data; user guides and Playwright e2e skeletons generated from the same journeys; help docs for feature pages composed instead of filtered
shippedTool-specific rules files generator0.1.0—Per-tool rules files (.cursor/rules, CLAUDE.md, copilot-instructions.md) generated from spec data with the spec-first workflow instructions baked in
shippedHelp vs developer docs split0.9.0—Two docs audiences from one .usm source — developer docs (full internals) and help docs (user journeys) with a subtraction filter and audience-specific sidebar
shippedHelp docs reference expansion0.8.2—CLI reference, usage examples, options, and prerequisites rendered in help docs from spec data
shippedMCP write tools (spec authoring)0.1.0—draft_feature, write_feature, update_feature, update_feature_status, write_system, write_service — close the spec-first loop so agents author .usm files with validation
shippedConsumer integration fixes (config validation, CI gate, help docs, MCP merge)0.9.1—From the safekeys integration report: usmconfig.json validated at load with usm validate --config (issue #43); generate --check skips untracked outputs (issue #42); help-tree nesting guard + path-honest output (issues #44/#47); upgrade --apply stamps alignment (issue #46); update_system/update_service merge id-bearing arrays (issue #48); package ships universal onboarding docs (issue #45)
shippedUniversal onboarding docs shipped in the npm package0.9.1—getting-started, agent-setup-guide, and 36 per-editor MCP setup guides ship inside the package and merge into consumer docs when the consumer repo has no docs-source/; homepage Getting Started link lights up on first generate
in-progressDocs sidebar information architecture restructure——Single-level sidebar nesting that VitePress renders correctly; unique human labels; dedicated Reference group; Architecture naming; help docs reduced to user-journey content; roadmap kept current
in-progressDeprecate subtraction-based help docs for feature pages——Feature pages in --audience help switch to composed content; subtraction filter retained for system-level pages during one transition cycle. Progressed by usm/docs-ia-restructure: help tree now excludes feature build specs entirely and surfaces composed persona guides instead.