Maestro Tasks
The tracker that keeps itself.
Tasks is the tracker built into ShareWell's accounting platform. When Maestro dispatches a task to an agent, the claim, the status changes, the summary comment and the closure are all written by the system. Nobody moves cards by hand.
Why it lives inside the product
The best tracker is the one your users are already in.
We tried the usual answers first. Linear drifted, because two busy engineers kept forgetting to open it. A Figma whiteboard held the plan beside the meeting notes but quietly lost the tasks. Feedback in WhatsApp scattered across threads and went cold before anyone could act on it.
So we stopped bolting on a separate app and built the tracker into ShareWell's accounting platform, where our customers already spend their day. A fund manager who hits a rough edge reports it from the page they are on, and the task captures that page, their browser and the viewport without anyone writing a handover. They watch the same board the team works from, and reorder their own priorities on it whenever they like.
Direct feedback from inside the software turned out to be the thing users loved most. The distance between noticing a problem and filing it dropped to one click, so the board fills with real signal instead of half-remembered asks.
Put the tool where the work already happens, so nobody has to remember to go somewhere else.
The philosophy behind the suite
Attribution
Agents get bylines.
claude, gemini and codex are first-class actors, each with its own identity instead of a shared service account. Every comment, estimate and status change carries the name of who did it.
claude· bot · 09:41
Claimed TASK-462. Plan: fix the rounding path in gross-to-net, add regression tests for partial redemptions.
sam · 09:44
Watch the 0.005 boundary — ATO rounding is half-up, not banker’s.
claude· bot · 10:12
Done. Summary: rounding now half-up at the cent, 6 new tests, no schema changes. Ready for review.
The automatic lifecycle
Zero bookkeeping.
From dispatch to done, the record writes itself.
01
dispatched
02
claimed
03
in_progress
04
summary posted
05
closed on merge
You moved zero cards.
Structure
Everything a tracker owes you.
Statuses that mean something
todo · backlog · in_progress · review · done, moved by the system as the work actually happens.
Priorities & estimates
None to urgent, thirty minutes to multi-week buckets. Enough structure to plan around without locking anything in.
Projects · milestones · health
on_track, at_risk, off_track. Project health is a field you set, backed by the work on the board.
Meetings
Meetings create tasks, attach docs and batch board changes, so decisions land on the board before the call ends.
Diary
Per-person daily entries. The orchestrator writes its own at the end of each day.
Notifications
Web-push when something needs you, and nothing when it does not.
Migrate without a big bang
Already living in Jira or Linear? Point it here.
Tasks does not ask your team to abandon the tracker it already knows. Pull issues in from Jira, Linear, Asana, Trello, Notion or monday, keep them in sync, and let the ones you hand to agents land on one board with their source stamped and their links intact.
Maestro Tasks
One board every tool feeds. Issues arrive with their source stamped and their links intact.
JIRA-204 → TASK-462 · linked
Integrations
Wired into where work actually happens.
GitHub issue sync
issue #88 ↔ TASK-462 · two-waySentry linking
link-sentry SHAREWELL-API-4X2 → TASK-455Commit linking
fix(gst): rounding on partial redemptions (TASK-462)API & CLI
Automate the automation.
A REST API and a thin CLI, authenticated per person or per bot. TASK-462, #462 and 462 all resolve to the same task. Everything the UI does, a script can do.