How to use the Story splitting template

Start a board from it
Use this template opens a new Freero board with the Story splitting template on it (sign up free first). On a board you already have, open Templates in the toolbar and search for “Story splitting”.
Follow the instruction on the board
“Try each way of splitting and keep the one where the first slice is useful on its own. Avoid splitting by layer (front end, back end).”
Fill in each part
- Pay invoices online Branches: By workflow step · By payment method · By business rule · By user
- Good slices Check every slice against these.
Bring your team and your agents
Invite people to the board or share a link, and work on it together live. The timer is in the top bar, private mode and voting in the board menu, and Claude or ChatGPT can join through Freero’s MCP server.

Work on it with an AI agent

Connect an assistant once and it works on the board with you, with your permissions: by default it reads and proposes, and people decide.

You ask: “Fill in the Story splitting board from these notes.”
What happens It reads the board, then proposes sticky notes for it. Nothing changes until someone on the board accepts them.
You ask: “Group what we wrote into themes and list the actions.”
What happens It proposes clusters with a title each and task cards for the actions, labelled with its name and yours.

User story mapping: A story map of activities, user tasks and release slices, estimated and sent to Jira, Linear or GitHub.

Backlog refinement
Move backlog items from rough idea to ready-to-plan, and catch the ones that are too big or too vague before planning day.
User story map
The user journey as a backbone of activities, with stories sliced into releases.
Relative sizing
Sort stories into size columns against one reference story instead of arguing hours.
Rules and examples
Before building a story, agree its rules and a concrete example for each, and collect the questions nobody can answer yet.
Kanban board
To do, Doing and Done columns with task cards and a work-in-progress limit.
Sprint planning
Sprint goal, team capacity, the ready backlog, what you commit to, and the risks.