Unblock Open the app

Your agents keep the plan · you see where things stand

What should I work on next?

Unblock The task that unblocks the most.

A live map of your project, kept by your agents. The plan is a dependency graph in your repo, .github/unblock.json. Your agents keep it current as they work; you see what's done, what's next, what's in the way, and how close a feature is. No tickets to groom, nothing to administer.

Open the app
Point your agent at unblock.esh.sh/skill.md
  • No tickets, sprints or seats
  • The plan is one file in your repo
  • Works with any agent, CLI or MCP
22s · made with /brag-slim

01 · The idea

Plans aren't lists. They're graphs.

Kanban columns can't say what waits on what. Unblock draws it, then does the arithmetic: which tasks are ready, which are blocked, and how close each blocked one is.

  1. Tasks wait on tasks.

    Arrows run from a prerequisite to the task that waits on it, so work flows left to right. Group related tasks under a parent.

  2. Every task shows % unblocked.

    The share of all the work upstream of it that's done, weighted by estimate. The landing page: 4 of 7 points upstream are done, so 57%.

  3. Finish one, watch the next unblock.

    Two prerequisites get done and the landing page goes from blocked to ready. Ready and blocked are worked out, never stored.

  4. Fold a group into one card.

    Links in and out of the group are kept on the folded card, with its progress on the front. You can also dive into a group and see only what's inside.

  5. Or see it as a force graph.

    Every task becomes a circle sized by its estimate, and a group becomes an outline around its tasks. Drag circles to untangle it.

02 · Agents

Your agent works the same plan.

A one-file CLI reads and edits the board, validates every write and refuses loops. The loop is four commands, and unblock point lets the agent show you what it means.

  1. Ask for the next tasknext lists ready tasks, most unblocking first.
  2. Claim itset <id> doing before starting.
  3. Point at itpoint rings it in your viewer with a note.
  4. Finish itset <id> done prints what just became ready.

Point your agent at unblock.esh.sh/skill.md

It explains how to install the CLI, start a board for your repository, work through it, and show you progress. It's written as a Claude Code skill, so you can save it as .claude/skills/unblock/SKILL.md. For any other agent, paste the link.

https://unblock.esh.sh/skill.md

03 · MCP

The board, right in the chat.

unblock mcp runs the CLI as an MCP server. Its show_board and point tools come with an MCP App, so the interactive board appears in the conversation with the pointed tasks ringed and the agent's note beside them.

  • It's the full app. Fold groups, switch to the force view, go full screen and edit. Edits save to the file through the server.
  • Clicking a task tells the agent which one you mean, and Work on this in the chat in a task's menu starts on it.
  • Clients without MCP Apps get the same information as text.
$ claude mcp add unblock -- python3 ~/.local/bin/unblock mcp
  • Claude Desktop
  • VS Code GitHub Copilot
  • Goose
  • and others

04 · Any repo

Track any repo's plan at /gh/owner/repo.

Commit a board as .github/unblock.json and open https://unblock.esh.sh/gh/<owner>/<repo>. The page reads the board straight from GitHub. There's no sign-up, no server storage, and nothing to install.

Private repositories too

  • You pick which repositories Unblock may use. It reads them, and writes only when you ask: saving your edits, or starting an agent.
  • The page never holds your GitHub token. Unblock's server keeps it and makes only the calls Unblock needs: it reads plans, never your code. Sign out in the side panel revokes it.
  • It checks for new commits every few minutes, so progress an agent pushes shows up on its own.
  • No board yet? The page offers to create .github/unblock.json with a starter board already filled in.
  • Add #point=<id>&note=<text> to any board address to link to a pointed task.

05 · The file

It's a JSON file in your repo. Agents and people share it.

Commit the board together with the code change it describes, so the history shows progress. This is a real task from Unblock's own roadmap, which is kept as an Unblock board.

.github/unblock.json
  "format" "unblock/v1"  "title" "Unblock roadmap"  "tasks"              "id" "ln-landing"      "title" "Landing page at unblock.esh.sh that explains the idea"      "status" "todo"      "parent" "launch"      "dependsOn""gh-dogfood" "joy-share" "ln-examples"      "estimate" 2      
Landing page at unblock.esh.sh that explains the idea
BLOCKED2 pt
Plain, documented format
unblock/v1, with a JSON Schema. Any other fields you add are kept as they are.
Checked on every write
The CLI refuses loops, missing ids and a task waiting on its own group. unblock validate names the ids involved.
Nothing to host
The app is one self-contained file. The CLI is one Python 3.8+ file, standard library only. Your plan stays in your repo.

06 · Pull requests

See what a pull request does to the plan.

Add one GitHub Action and every pull request gets a comment: which tasks it finishes, what it unblocks and what it adds, with a picture of those tasks drawn like the app.

The comment's real picture for the change that added this feature to Unblock's own roadmap (2755ba5 → f128f43).

One command to set up

$ unblock init --ci
  • Only this pull request's changes. It compares GitHub's merge result with the base branch, and keeps one comment up to date as you push.
  • Drawn like the app: cards, % rings with the value before, and chips for new, done, now ready and now blocked, in light and dark.
  • Nothing to configure. The run proves which repository it is with GitHub's built-in token. Private repositories get a Mermaid graph unless you turn pictures on.
  • Fails the check if a pull request would leave the board invalid.
  • unblock diff main...feature shows the same in your terminal, and /gh/owner/repo/compare/main...feature in the app.

07 · Get started

Start with one link.

Your agent can do the setup. Or run it yourself: these are the same commands the skill uses.

For your agent

Point it at the skill

It installs the CLI, drafts a board from what you asked for, the README and the code, and commits it.

https://unblock.esh.sh/skill.md
By hand

Install the CLI

Once per machine (macOS and Linux; Windows below). It checks the download against the release's sha256 and puts unblock on your PATH. Then create a board and open it in the browser; edits there save to the file.

curl -fsSL https://unblock.esh.sh/install.sh | sh
irm https://unblock.esh.sh/install.ps1 | iex
unblock init
unblock view
In the chat

Add the Claude Code plugin

The board in a pane beside the conversation, the plan above the prompt, and the CLI and MCP server with it. Other MCP clients (Claude Desktop, Cursor, Copilot) run the server with uvx.

claude plugin marketplace add sqvist-ab/unblock
claude plugin install unblock@unblock
uvx --from unblock-cli unblock mcp

Open the app. Or let your agent.

The app opens with an example board. Or browse a repository's board at unblock.esh.sh/gh.