MeisterTask

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me the automated kanban board that replaces MeisterTask.

The idea worth taking is narrow and good: **the automation belongs to the column, not to the card.** "Anything that lands in Done gets marked complete and unassigned" is a rule you write once, and it is why this board needs less tending than others.

STACK
- Node 20+ with Fastify, server-rendered HTML with a little vanilla JS
- SQLite through better-sqlite3, WAL mode, FTS5 across cards
- Caddy in front

THE DATA MODEL
- boards: id, name
- sections: id, board_id, name, position, automations_json, wip_limit
- cards: id, section_id, title, body_md, assignee_id, due_on, position, archived_at
- moves: id, card_id, from_section, to_section, actor, at — **append-only, and every report is computed from it**
- checklists, comments, attachments as small tables
- watchers: card_id, user_id

SECTION AUTOMATIONS
- A short vocabulary: set status, assign to somebody, add or remove a label, set a due date relative to today, notify a watcher, move to another section
- Run on arrival, in order, once. **A cap of one automated move per card per arrival**, or two sections that push to each other will ping-pong forever — this is the failure everybody ships once
- Record every automated action in the moves table with the rule that caused it, so a card that ended up somewhere strange can be explained
- A dry run: pick a card, see what would happen if it landed here

THE BOARD
- Drag between sections, keyboard reachable, positions as sparse integers so a move is one write
- A work-in-progress limit per section, shown as a warning rather than a block — a hard block makes people rename sections to get around it
- Filters by assignee, label and age, saved per person

RECURRING WORK, WHICH IS WHAT THIS SHAPE SUITS
- A card can recur on a schedule: when it is completed, the next one is created with the same checklist
- **Never create the next one until the current is done**, or a fortnight away produces fourteen copies of the same chore

REPORTS THAT ARE ACTUALLY TRUE
- Time in section, from the moves history — the only honest measure of where work sits
- Cards with no movement for a fortnight, per section. **The most useful report any board has**
- Throughput per week and cycle time as a distribution, never as an average

OPERATIONS
- .env: DATABASE_PATH, BASE_URL, SESSION_SECRET, SMTP_URL
- Notifications batched: one digest per person per day, plus immediate for a direct mention. A board that emails on every move gets muted

WHAT MATTERS MOST
The one-automated-move cap and the append-only move history. The first stops the rules fighting each other; the second is what makes every report defensible.