Why Slicemap exists
I’m Dmitrii Bugaev. I’m a product manager, and I build products with a coding agent—Slicemap included.
The agent works fast, but it doesn’t keep a plan. Every session it asked again what we were building, the plan lived in a file that went stale, and I kept retyping it into new chats. So I gave the plan a place of its own: a map the agent lays out with me and then builds from, one story at a time, handing each one in against its criteria.
I build Slicemap with its own map, story by story, with an agent doing most of the coding. If you build the same way, I’d like to hear how it goes for you.
—Dmitrii
What Slicemap keeps to
Plan first, then code
The agent lays the product out on the map before it writes code, and estimates each story before it starts.
Done means checked
A story closes only when every acceptance criterion is checked. The agent checks them; you accept the work.
You see who changed what
Every card shows who changed it last: you, a teammate or the agent.
Your code stays yours
Slicemap never sees your repository and never calls a model.
Your data stays in the EU
Maps are stored in the European Union (Lithuania).
You can always leave
Export any map to JSON or Markdown at any time.
Built with Slicemap
Slicemap is planned and built on its own map: steps of the user’s journey, releases by week, and an agent that takes the next story, estimates it and records the minutes it spent.
Try it on your own project
Sign-up takes a minute. The beta is free, and everyone who joins now gets three months of the paid plan for free when paid plans start.
Join the free beta