KM Online — Task Manager design preview

One board the whole company works out of — staff and agents. Move cards left → right through the stages. (Purple ring = an agent.)

💭 Initial Ideas 2
kmonline.co.uk/sop — surface SOPs + agent files on the portal
Product
MManish💬 1
Manish drops raw ideas here anytime → Robin triages into Backlog
Process
MManish💬 0
💡 Backlog / Ideas 3
Portal Task Manager (this board)
Product
MManish💬 5
Family messaging app
Product
MManish💬 2
eSagu repricing automation
Ops
MManish💬 1
📋 To Do 2
Restock → auto-create FBA shipments
Ops
FFranky💬 6
Email two-way inside portal
Feature
UUsopp💬 9
🔨 In Progress 2
Delete messages — for-me / for-everyone / burn
Chat
FFranky💬 14
Security authz gates (turnover, Xero, checklist)
Security
VVivi💬 11
🔍 Review (§9) 1
Authz server cluster — code review
Security
DDoflamingo💬 8
🧪 QA 1
Authz fixes — live verification matrix
Security
CChopper💬 5
🚀 Shipped 3
rio — supplier feedback page
Supplier
RRobin💬 7
git ✓flutterweb ✓
Message delete — for-me + for-everyone
Chat
FFranky💬 14
git ✓flutter ✓web ✓
Location capture → Robin
Feature
FFranky💬 3
git ✓flutter ✓web
Columns (the major stages): 💭 Initial Ideas → 💡 Backlog → 📋 To Do → 🔨 In Progress → 🔍 Review (§9) → 🧪 QA → 🚀 Shipped  ·  configurable.
💭 Initial Ideas = your inbox: drop raw ideas here the instant they hit you — no waiting on Robin. Robin triages each into Backlog with the full write-up. Decouples your speed from the crew's.
Shipped checkboxes: every shipped card carries git · flutter · web — tick each surface as it lands (greyed/struck = not applicable, e.g. a web-only feature has no flutter).
Two views: Board (kanban) + List (above toggle). Same tasks, your pick. Agents = staff: any card assigned to a person or agent (purple ring); both log every update.
Static design preview — not the working tool. The real board would live at kmonline.co.uk/taskmanager.

Logical + easy to maintain (humans + agents) + simple API:
• One card = one task. Fields: title (plain English) · category · stage · assignee · activity log · surface-flags (git/flutter/web).
• Stage is just a column — moving a card = one field change. Clean for a person dragging, and for an agent calling PATCH /api/tasks/:id {stage}.
• Obvious endpoints: GET /api/tasks?stage= · POST /api/tasks · PATCH /api/tasks/:id · POST /api/tasks/:id/log. One API serves both views + both humans and agents.