Stories
How a piece of work goes from a sentence to a merged, checked change.
A story is one piece of work with acceptance criteria. It can start as a sentence in the chat, a ticket in your tracker, a thread in Slack or a note from a meeting. kanman shapes it, plans it, writes the change with its helpers, checks it with your CI and an independent review, merges it and tells you how it went.
- Describe You describe a goal or a story, in the chat, on the board or in Slack.
- Plan kanman reads the code and the board, splits the work, picks the order.
- Work Helpers write the code, each in its own sandbox, on its own branch.
- Check Your CI, then an independent reviewer that did not write it. A problem CI or the reviewer finds is fixed and checked again.
- Merge kanman merges and shows every step live and in the activity log.
- Waits on people only what kanman cannot find out, asked once, in one place.
Try this in the chatIn your team's chat
- The CSV export cuts names after 50 characters. Names can be up to 200. Please fix it and add a test.
- Why did SBX-12 need a second attempt?
In this section
How a story flows
The path every piece of work takes: you describe it, kanman plans it, helpers write it, your CI and an independent reviewer check it, kanman merges it, and you see every step live.
Your first story
Take one real story on your own repository from requirement to a merged pull request, and know what to do when something stops.
Write requirements kanman can finish
How to phrase requirements and stories so they pass the readiness checks and end in a merged pull request.
Stories and acceptance criteria
A story is a small, verifiable piece of work with acceptance criteria and a Demonstrate block that shows the outcome.
Work in progress
How kanman's helpers work on your stories: each in its own sandbox and branch, visible live, with every step in the team's activity log.
How kanman checks its work
Every change kanman makes passes your repository's CI and a review by a helper that did not write it before kanman merges it. The rule is enforced outside the model.
Browser proofs
When a change is visible to people, kanman tries it in a real browser and records it: a video with every step named, what passed and what failed.
After the merge
kanman stays with its work after the merge: release notes, watching the deploy, checking production through the story's acceptance check and your signals, and telling everyone when it is live or what failed.
Meeting notes and transcripts
Share meeting notes, a transcript or a recording summary with kanman. It proposes the stories, decisions and context worth keeping, says who said what, and changes nothing until you pick.