Habits
What kanman keeps doing without being asked: built in, or made by you in the chat.
A habit is something kanman keeps doing without being asked again: when something happens, kanman does what you asked and tells you where you want to hear it, within what it may do and the team’s budget. Habits are how kanman becomes yours: the more it knows about how your team works, the better it fits.
- Built in: every team starts with a few, such as reviewing merge requests, watching main and keeping dependencies current. You can pause them or change how they work.
- Made in the chat: tell kanman what to keep doing, in your own words. It answers with a habit card; Start it, and the habit appears on the team’s Habits tab.
- For the team or just for you: a team habit reports to the team; a personal habit only to you, on For you.
- One-off asks (“tell me when !412 merges”) are kept the same way and drop off once they fired.
Try this in the chatIn your team's chat
- Every Friday at 15:00, post what we shipped this week
- Whenever a merge request touches database migrations, flag it in the team chat
- Tell me when main is green again
New habit
Shipped this week
- When
- Fridays 15:00
- What
- Wins from merged work and closed stories
- Where
- Team chat, nothing on a quiet week
- May do
- Nothing outside kanman
- Budget
- From the team budget
In this section
How habits work
A habit is something kanman keeps doing for your team, or just for you, without being asked again: review merge requests, watch main, keep dependencies current, post what shipped every Friday. A few come built in; you make, change and pause habits by telling kanman in the chat, and the team's Habits tab shows them all with their runs.
Habit ideas to copy
Ready-to-paste habits for keeping the team informed, guarding quality, keeping repositories healthy, handling alerts and looking after yourself. Copy one into the chat and change the words until it fits.
Code review
kanman reviews your team's merge requests like a careful colleague: on request or every one, with comments only. It is a built-in habit you change in the chat. kanman never approves, pushes to or merges a person's merge request.
Failing pipelines
kanman watches the pipelines of your default branches, including the nightly scheduled runs, tells a broken test from a flaky one or a service that is down, files one fix story per failure across all affected repositories and pursues infrastructure problems until the pipelines are green.
Maintenance mode
kanman scans your repositories on a schedule for vulnerable, outdated and unused dependencies, broken links and drift, lists what it finds, decides with you what becomes a story, and works alongside Renovate and Dependabot.
Incidents and on-call
kanman can be on call for the services your team runs: it opens an incident when something degrades, investigates, acts within your rules and closes the loop with a summary and follow-up stories.