Read your OpenSpec

spek turns a repository's openspec/ directory into something you can browse — specs, changes and their tasks, schemas, a timeline, full-text search. It only reads; it never changes a file.

Try the live demo Read the docs

spek showing an OpenSpec change: its delta specs grouped by capability, each requirement with its SHALL keyword highlighted, and tabs for the proposal, design, and tasks. — A change's delta specs, requirement by requirement, with the normative keywords highlighted. Screenshots show illustrative example content.

Specs are meant to be read

OpenSpec keeps a project’s requirements and every change to them as Markdown files under openspec/. That is the right format for an agent to write and for git to track, and a hard one to read: a change is a proposal, a design, a task list, and a delta per capability, spread over a dozen files. spek reads that directory and lays it out — with structure, links between specs and changes, and progress you can see at a glance.

What you can browse

Dashboard

How many specs and changes there are, task completion, average lifecycle, and changes that have gone stale.

Specs and changes

Specs as a folder tree with their history; changes active and archived, each with its proposal, design, tasks, and delta specs as tabs.

Schemas, graph, timeline

The workflow schemas a repository uses, how specs and changes relate, and every change’s lifecycle as a Gantt-style timeline.

Every worktree at once

The in-flight changes of all of a repository’s git worktrees in one list — for agents working in parallel.

spek's dashboard: counts of specs, active and archived changes, task completion and average lifecycle, then the active changes with their progress and the recently archived ones. — The dashboard: what is in flight, how far along it is, and what was archived recently. Screenshots show illustrative example content.

Four ways to run it

All four show the same views. Pick the one that sits where you already work.

VS Code extensionA panel and a sidebar in your editor. From the Visual Studio Marketplace.

JetBrains pluginA tool window in IntelliJ IDEA, WebStorm, PyCharm, and other JetBrains IDEs. From the JetBrains Marketplace.

Web appRun it from the source in your browser, against any repository on your machine.

GitHub ActionBuild a static spek page and status badges for your repository in CI. From the GitHub Marketplace.

How to install and use each: Install spek.

spek's timeline: one row per change, archived changes as bars from creation to archive and active changes extending to today. — Every change's lifecycle on one timeline. Screenshots show illustrative example content.

spek and spekterm

spek’s engine reads OpenSpec for spekterm too: spekterm’s side panel uses spek’s core package (@spekjs/core) to scan specs and changes, and draws spek’s graph and timeline (@spekjs/ui). spek is for reading specs where you already work; spekterm is a desktop workbench for running Claude Code sessions next to them. Neither needs the other.

Open source

spek is MIT-licensed, and its source is on GitHub. It has no account, no telemetry, and no analytics; Data and network lists what each form connects to.