Guides
Step-by-step help for the tasks you do when you run kanman in a real team.
Each guide solves one task from start to finish and links to the reference for every setting it uses.
Write requirements kanman can finish
How to phrase requirements and stories so they pass the readiness checks, get a useful Demonstrate block and end in a verified pull request.
Add an acceptance manifest to your repo
Teach kanman how to start your app in a fresh environment and run acceptance specs, so every story ends with real proof.
Choose and tune a preset
Pick the preset that fits how much your team wants kanman to do on its own, and adjust single settings without losing track.
Answer decisions from Slack
Connect Slack so kanman posts decisions with their options to a team channel, you answer with one click, and requirements from threads become stories.
Run the self-hosted runner
Run kanman's code work on your own infrastructure with a Docker image that connects outbound only, without opening ports or sharing database credentials.
Use kanman from Claude Code or Codex
Add the kanman MCP server to Claude Code or Codex on your machine, pick up a kanman story from the terminal and still get the evidence pack.
Roll out to a second team
Take what worked for the first team to the next one: reuse connections and settings, carry over the acceptance manifest pattern, and keep each team's rules its own.