OpenSpec Future Development Plans: The Complete Phase-by-Phase Roadmap

OpenSpec is evolving from a research-grade prototype to a production-ready tool through a structured eight-phase roadmap that introduces standalone stores, reference-based linking, and personal worksets while retiring legacy beta surfaces.

The future development plans for OpenSpec are documented in a living roadmap located at openspec/work/simplify-context-and-workspace-model/roadmap.md within the Fission-AI/OpenSpec repository. This roadmap drives every design decision, implementation detail, and verification step, ensuring each phase delivers a concrete, test-covered slice of functionality.

The Eight-Phase OpenSpec Roadmap

The roadmap progresses through eight distinct phases, each building upon the previous to create a stable, agent-first architecture.

Phase 0: Direction and Discoverability

Phase 0 establishes the foundation by centralizing the roadmap and goal files. The goal.md file defines a simple contract: "specs are true, work is in motion." This makes the active plan discoverable by both agents and humans, ensuring that the entry point src/cli/index.ts can always locate the current authoritative direction.

Phase 1: Standalone Store Model

This phase introduces the store concept: a standalone OpenSpec repository that can exist independently of any project workspace. The implementation adds a --store flag to normal commands, allowing users to select a target root explicitly.

According to the specification in openspec/work/simplify-context-and-workspace-model/slices/store-root-parity/spec.md, users can now create and register stores without touching any legacy initiative or workspace machinery.

# Initialise a new standalone OpenSpec store

openspec store setup --name team-context --path /tmp/team-context

# Verify store health

openspec store doctor --json

Phase 2: Initiative Retirement

All new change flows no longer create initiative links, and the old initiative command groups are hidden from the CLI. This removes confusing beta terminology from the main user path, as specified in the roadmap's Phase 2 slices. The legacy surfaces remain temporarily to prevent breaking existing users, but new work bypasses them entirely.

Phase 3: External References

Projects can now declare a list of references in their openspec/config.yaml. The resolver checks --store first, then the nearest local root, then any declared default store. This makes the relationship between a code repository and its planning stores explicit and read-only.

The reference handling is implemented in openspec/work/simplify-context-and-workspace-model/slices/store-references/spec.md.

# openspec/config.yaml

references:
  - id: team-context
    path: /tmp/team-context

Phase 4: Context Assembly

The new openspec context command builds a JSON brief that contains the project root and all reachable stores. This powers agents that need a full working set without imposing any workspace state.

The implementation lives in openspec/work/simplify-context-and-workspace-model/slices/assemble-working-context/spec.md.

# From any location, assemble the working context

openspec context --json > workset.json

The output contains the root path and associated stores:

{
  "root": "/path/to/project/openspec",
  "stores": [
    { "id": "team-context", "path": "/tmp/team-context" }
  ]
}

Phase 5: Legacy Surface Cleanup

Legacy command groups (workspace, initiative) and their associated schemas are being removed, eliminating approximately 12,000 lines of dead code. The deletion slices in slices/delete-legacy-command-groups/ are already merged, with remaining artifacts scheduled for cleanup once Phase 4 lands in the main branch.

Phase 6: Full-Stack Acceptance

This capstone phase involves a series of persona journeys, usability audits, and technical audits that validate the zero-to-success workflow. The reports, stored in capstone/, confirm that a brand-new user can start from zero context, succeed with a handful of commands, and receive clear guidance on errors. The test suite is already passing; only the final release-readiness documentation merge remains pending.

Phase 7: Personal Worksets

The final phase introduces worksets: purely local, named collections of folders (store checkouts + code repos) that are stored in a machine-local data file and never versioned. Users can compose, list, and open these views in any supported tool (code, cursor, claude, codex).

The specification in openspec/work/simplify-context-and-workspace-model/slices/workset/spec.md defines the command group.

# Compose a workset named "my-dev-view"

openspec workset compose my-dev-view \
  --add /tmp/team-context \
  --add /path/to/project

# Open in VS Code

openspec workset open my-dev-view --tool code

Current Implementation Status

As of the latest commit to the main branch, the roadmap progress stands as follows:

• Completed: Phases 0 through 4 (merge pending for some slices)
• In Progress: Phase 5 (deletion of legacy surfaces)
• Pending: Phase 6 (final acceptance capstone) and Phase 7 (workset merge)

The checklist in openspec/work/simplify-context-and-workspace-model/roadmap.md uses [x] to mark completed items and [ ] for open work.

Summary

• OpenSpec follows an eight-phase roadmap documented in openspec/work/simplify-context-and-workspace-model/roadmap.md that transforms the tool from prototype to production.
• Standalone stores replace the old workspace model, allowing users to create and reference external planning repositories via the --store flag.
• Reference-based linking in openspec/config.yaml enables projects to declare dependencies on external stores without embedding them.
• Context assembly via openspec context produces a JSON brief of the full working set, supporting agent-first workflows.
• Legacy cleanup removes approximately 12,000 lines of beta-phase code, including the workspace and initiative command groups.
• Personal worksets allow users to compose local, named views of arbitrary folder combinations and open them in any supported editor.

Frequently Asked Questions

What is the current status of OpenSpec production readiness?

OpenSpec is currently in Phase 5 of its roadmap, with Phases 0 through 4 implemented and tested. The capstone audits in Phase 6 are already passing, and the final release-readiness report is awaiting merge into the main branch. Users can expect a production-ready release once Phase 6 documentation and Phase 7 worksets are merged.

How do I use the new store model instead of workspaces?

Initialize a standalone store using openspec store setup --name <name> --path <path>, then reference it from any project directory using either the --store flag or by adding it to the references: list in openspec/config.yaml. The legacy workspace commands are being deprecated and should not be used for new projects.

Where is the roadmap file located in the repository?

The master roadmap is located at openspec/work/simplify-context-and-workspace-model/roadmap.md in the Fission-AI/OpenSpec repository. This file tracks every phase, slice, and acceptance criterion with live checkboxes showing current completion status.

What are personal worksets and when will they be available?

Personal worksets are local, named collections of folders (combining stores and code repositories) that can be opened in various editors. They are scheduled for Phase 7 and are fully implemented, pending only the final merge into the main branch. The specification is available in openspec/work/simplify-context-and-workspace-model/slices/workset/spec.md.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}