SMF·MEISTERTASK
Can a prompt replace MeisterTask?
Project management — kanban with section automations
Exhibit tracking slip
Verdict
MeisterTask is a well-made kanban board with one idea worth stealing: automations attached to the column rather than to a rule engine somewhere else. Cards entering "Review" get an assignee and a due date because the column says so, and that is both obvious to a new user and genuinely useful. A weekend rebuilds it. The gaps are the mobile apps, the mind-map sibling product, and the hosted polish — none of which is a moat.
Exhibit A — The prompt
Received on31.07.2026Build a kanban board where automation lives on the column, not in a rule engine.
Stack: your choice, Postgres, Docker Compose, one command.
Board model: a Project has ordered Sections (columns); a Section holds ordered Cards. A Card has a title, description, assignee, due date, labels, checklist items, comments and attachments.
Section automations, the point of the build. Each section carries an ordered list of actions, run when a card **enters** it, from a closed set:
- assign to a specific person, or to nobody
- set a due date N days from entry, skipping weekends if configured
- add or remove a label
- move to the top or bottom of the section
- post a templated comment
- archive the card
Rules that keep this sane and must be tested: actions run once per entry, in listed order; an action that moves the card to another section does not cascade — the destination's automations do not fire, and the UI warns when you configure one that would; and every automated change is written to the card's activity log labelled as automatic, so a mysterious assignee can be explained.
Section limits: an optional work-in-progress cap per section. Exceeding it does not block the move — it marks the section visibly over capacity, because a hard block just makes people rename things.
Card checklists where completing all items can optionally trigger a move to a named section, which is the second automation people actually want.
Also: a personal "assigned to me" view across all boards sorted by due date, board archive with search, board duplication that copies sections and their automations but not the cards, and CSV export.
Write tests for automation ordering, for the no-cascade rule, and for board duplication copying automations exactly once.
Do not build mind maps, mobile apps, or real-time multiplayer.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the mobile apps and offline board access
- B.2 MindMeister integration, turning a mind map into a project
- B.3 real-time multiplayer on the same board
- B.4 the prebuilt integrations into chat and storage tools
- B.5 hosted reliability and backups
Prior art
Exhibit C — Why people still pay: hosted polish
Because it is pleasant, fast and does not require a workshop to adopt, which is worth more to a small team than a longer feature list.
Questions
Why must automations not cascade?
Because a card that lands in a section which moves it to another section which moves it back is an infinite loop, and the interesting version of that bug only appears in production. Refusing to cascade is simpler to reason about than any loop detector.
Why warn instead of block on a work-in-progress cap?
Because a hard block gets routed around — people create a "Review 2" column — and you lose both the signal and the honesty. A visible over-capacity marker keeps the information.
What makes column-level automation better than a rule engine?
Discoverability. The rule is visible where its effect happens, so a new person opening the board understands why the card got a due date. Rule engines end up as a screen nobody reads.
Can I get my MeisterTask boards out?
Projects export as CSV or JSON from the project settings, including sections, cards, checklists and comments. Attachments come out as links, so download them before closing the account.
Related tools
Receipt