Skip to content
Slicemap Docs

What is Slicemap

View as Markdown to paste the page into your agent.

Slicemap is a product map for people who build with a coding agent: Claude Code, Codex, Cursor or any other agent that connects to an MCP server. Your agent lays the product out on a map, and you decide what goes into the next release. Then the agent takes the next story from the map and marks on it what it actually finished.

The map

Section titled “The map”

Across the top are the steps a user goes through: finds you, signs up, pays, comes back. Chapters group the steps. Under each step are the stories, and each story holds its acceptance criteria. Releases are rows across the map: the top row is what the product can’t ship without, the rest waits its turn.

If you want the name: it is user story mapping, Jeff Patton’s method. You don’t need to know the method to use the map.

Who it is for

Section titled “Who it is for”
  • Builders who ship a side project or a startup with a coding agent.
  • Freelancers and small studios who agree on scope with a client and show progress on one map.
  • Product people who already think in releases and acceptance criteria and now build themselves.
  • Small teams: a designer, a second developer and the client on one map, each with their own role.

How the agent works with it

Section titled “How the agent works with it”

The agent connects to Slicemap over MCP by address, with a personal API key. Then, story by story:

  1. It takes the first story of the active release that is not yet in a closed stage.
  2. It estimates the story in minutes of its own work before writing code.
  3. It moves the story through your project’s stages: into development, then on to acceptance.
  4. It ticks each acceptance criterion as it checks it. It can’t move a story to a closed stage while a criterion is unticked.
  5. It records the minutes it actually worked.

When every story of the active release is in a closed stage, the agent stops and lists the backlog. Then you activate the next release or name the story you want. You, your team and your client follow the progress on the map, or by a read-only link that needs no account.

Concepts

Section titled “Concepts”
Concept What it is More
Step A moment in the user’s journey, a column on the map: “signs up”, “pays”. The story map
Chapter A group of steps shown above the columns. Steps in a chapter are numbered 1.1, 1.2. The story map
Story A card under a step: what the user gets. Each story has a number like SM-142. The story map
Acceptance criterion A checklist item inside a story: what must work. The agent ticks it once it has checked it. Acceptance criteria
Release A row across the map, the thinnest version of the product you can show a real person. Stories without a release sit in the Backlog. The slice
Stage Where a story is in development, from Idea to Production by default. Each stage has a description that says what it means. Set up stages
View A tab that shows the same map as a Map, Kanban, Outline, Table or Mindmap. Tabs are shared with everyone on the map. Use views

Next steps

Section titled “Next steps”