Slicemap
Join the free beta

Changelog

What changed in Slicemap, newest first. Follow it in your reader: RSS.

Releases get dates and a goal

Give a release a start date, an end date and a goal, so everyone sees what the release is for and when it ends.

  • Your agent can set them too with slicemap_create_release and slicemap_update_release.

Chapters above the steps

Group the steps of the user’s journey into chapters shown above them on the board, with numbers like 1.1.

  • Chapters fold and unfold, and your agent can create and edit them.

Short story numbers like SM-142

Every story gets a short number with the project key, so you and the agent can name it in a chat.

  • Change the project key at any time: numbers with an earlier key keep working.

Estimate statistics for each project

A Statistics page shows how many open stories are estimated, plan against actual minutes and how far off the agent usually is.

  • Your agent gets the same numbers from slicemap_project_stats.
  • Stories the agent finds unclear are listed with what is missing, so you can answer before coding starts.

Your agent estimates in minutes, then records the actual time

Before writing code, the agent estimates a story in minutes of its own work; when it hands the story over, it records the minutes it actually spent.

  • The estimate has a range, a complexity, a clarity score and what is missing.
  • The plan freezes when the story first goes into work, so plan and actual can be compared.

Columns and rows by any field

Build the board the way you need it: columns and rows by step, release, stage, assignee, persona or priority.

  • Choose which fields cards, Outline rows and table columns show, and how dense the view is, in Display.
  • Expand the whole map to steps, stories or criteria in one click.

Development stages with descriptions

Each project has its own page of development stages: their order, colors, the default stage and what each stage means.

  • Your agent reads the stage descriptions and knows when a story moves on.
  • Ask the agent to set up stages for your project: it proposes a flow and changes it after you agree.

Connect your agent by address

Slicemap answers as an MCP server at its own address: connecting an agent is an address and a key, with nothing to install.

  • Claude Code takes one command, Codex a block in ~/.codex/config.toml, Cursor and other clients a few lines of JSON.
  • New tools reach every connected agent with the next release, without reinstalling anything.

Saved views as tabs above the map

Every map has tabs of saved views, each with its own filters, grouping and sorting, shared by everyone on the map.

  • Five views come with every map: Map, Kanban, Outline, Table and Mindmap.
  • A change to a tab is saved for the whole team; viewers and guests change the view only for themselves.
  • Stories and steps can be dragged on the mind map with the mouse and the keyboard.

See who changed a card last

Every card shows who changed the story or its criteria last and when, and a change made by an agent is signed as the agent.

  • The signature is set by the database, so the time and the author cannot be faked by the client.
  • The read-only link does not show it.

Your agent opens any story with its criteria

The agent reads a single story from anywhere on the map, with its acceptance criteria and their ids.

  • slicemap_get_story returns one story from the active release, a later one or the backlog.
  • When the agent replaces a story’s criteria, a criterion with the same text keeps its id and its checkmark.