docs/agentspot_task_manager_agent.md

AgentSpot agent: Task Manager, on the team tracker

Design and paste-ready agent definition. Written 2026-10-20 from boone's brief and his answers (Supabase store, server-side GitHub, two repos, ThoughtSpot views). Code on branch feature/tracker; status in sprint_2026_04.md. The agent is built in the AgentSpot UI on secloud. The tracker is code in this repo: demoprep_app/tracker/ (schema, store, GitHub sync, TML) and six tools in mcp_server.py.

Team: Mike (mike.boone), Jack (jack.rayner), Manny (mani.uppala), Gora (gora.sudindranath). Overall view also for Paul.

---

The brief

Pull requests already go through GitHub, but nothing else does. Sprint notes are markdown files in this repo and "ping Jack" happens in Slack by hand. Wanted:

• one task list the team can assign to each other, kept in Supabase;
• pull requests understood by the tracker: which task a PR belongs to, what state it is in;
• a personal view (my stuff) for each person, and an overall view for a manager;
• a way to hand work to an agent, through Slack or the database.

---

Decisions

Item	Decision	Source
Task store	Four tables in the existing Supabase project beside demo_history: tasks, task_notes, pull_requests, tracker_people, plus the task_board view for ThoughtSpot. Real tables, not the demo_history status-sentinel pattern, because ThoughtSpot needs typed columns. demoprep_app/tracker/schema.sql.	boone (Supabase); shape recommended
Who writes	Six tools on the DemoPrep MCP server: list_tasks, create_task, update_task, add_task_note, list_pull_requests, sync_pull_requests. The AgentSpot agent, the Slack bot, and any Claude Code session with the connector use the same tools.	recommended
Pull requests	The MCP server polls GitHub with a repo-scoped token every 10 minutes (demoprep_app/tracker/github_sync.py). A PR links to a task by a stored link, by the task's own pr_url, or by T-<id> in its title, body or branch name. A merge adds a note to the task; it never closes it.	boone (server-side token)
Repos	boone10/DemoPrep and thoughtspot/tse_demos, set by TRACKER_REPOS.	boone
Views	ThoughtSpot on secloud with a live PostgreSQL connection to Supabase (ThoughtSpot Cloud lists PostgreSQL as a supported connection; no Snowflake mirror). Model Team Tracker and a Liveboard with Team, Pull requests and Stale tabs: demoprep_app/tracker/tml/. Personal view by an Owner Name filter saved as each person's personalized view, or a one-line RLS rule. An AgentSpot App can be generated from the same model later.	boone (ThoughtSpot)
Identity	owner and requester are ThoughtSpot usernames (mike.boone), what ts_username sees in RLS and what the run reports print. The agent passes the caller's name; the store resolves username, email, GitHub login, display name or first name, and refuses anything else.	default
Communication	AgentSpot's Slack bot bound to one public channel; a scheduled Workflow posts a weekday digest.	AgentSpot native
Branch	feature/tracker off claude/agentspot-tse-modifications-9b57a7, the branch test-mcp runs, so the next push carries the Portal Editor tools and the tracker together.	boone
Audience	Mike, Jack, Manny, Gora use it. Gora and Paul get the overall view. Agent shared "Can use", Mike keeps "Can edit".	boone

---

Data model

demoprep_app/tracker/schema.sql, run once in the Supabase SQL editor. Idempotent.

tracker_people: username (ThoughtSpot), display_name, email, github_login, is_manager, active. Seeded with the four; only boone10's login is known, fill the others in as they are learned (until then the sync shows raw logins).

tasks: id (shown as T-12), title, body, status (open, in_progress, blocked, review, done), priority (p1..p3), label (task, bug, demo, portal, docs), owner, requester, repo, pr_number, pr_url, run_id, liveboard_url, due_date, created_at, updated_at, closed_at.

task_notes: id, task_id, author, note, created_at. Every reassignment, status change, priority change, PR link and merge writes one.

pull_requests: repo + number (the key), title, author (username when the login is known), author_login, branch, state (open, merged, closed), draft, reviewers, waiting_on, task_id, url, created_at, updated_at, merged_at, synced_at.

task_board (view): one row per task with its PR's state and waiting_on, the owner's display name, days open, last note, and stale (five days with no note and no PR change while not done). What list_tasks returns and what ThoughtSpot models.

---

MCP tools

All sync functions beside the portal tools, same {status, ...} result shape. A request that is partly wrong is wholly refused with every problem named ({status: "failed", errors}) and nothing is written. No tool deletes.

Tool	Takes	Returns
list_tasks	owner, status, label, requester, search, include_done, limit	{status, count, tasks: [{task, id, title, status, priority, label, owner, owner_name, requester, pr_url, pr_state, pr_waiting_on, run_id, liveboard_url, due_date, days_open, stale, ...}]}
create_task	title, owner, requester, body, label, priority, due_date, pr_url, run_id	{status, task}
update_task	task_id, by, then any of title, body, status, priority, label, owner, due_date, pr_url, run_id, liveboard_url, plus note	{status, task, changed: {field: [old, new]}}
add_task_note	task_id, note, by	{status, note_id, task}
list_pull_requests	repo, state (default open), waiting_on, author, unlinked, approval, limit	{status, count, synced_at, pull_requests: [...]} with approval, approved_by, agent_opened, checks, mergeable on each
sync_pull_requests	none	{status, repos, fetched, linked, merged: [{task, repo, pr}], approvals: {auto, approved, pending, ...}, synced_at}
approve_pull_request	repo, number, by (an approver), note	{status, pull_request}; refused when by cannot approve or the PR is not open
pipeline_status	none	{status, integration_branch, ready, held: [{..., held_because}], awaiting_approval, agent_tasks, last_runs, last_deployments}
list_deployments	space, limit	{status, count, deployments: [{space, branch, sha, pushed_at, pushed_by, health, ping_code}]}
ingest_findings	hours (default 36)	{status, created: [T-ids], updated: [T-ids], findings}

The pickup pipeline behind the last four is docs/development_process.md: four runs a day on boone's Mac merge approved PRs into develop, run the suite, and push the test Space when it is idle. Approval: Mike's and Jack's own PRs are approved on arrival; anyone else's, and every agent/ branch, needs one of them.

update_task with status=done or status=cancelled sets closed_at; reopening clears it. Both are closed: they leave open lists and the stale flag, and show only with include_done. The automatic notes read "reassigned from X to Y", "status open -> done", "priority p2 -> p1", "linked ", with the caller's note appended.

---

Pull request sync

A daemon thread in the MCP server, started in main() when GITHUB_TOKEN is set, runs a sync every TRACKER_SYNC_MINUTES (default 10). For each repo in TRACKER_REPOS it lists pull requests updated since the last sync, reads the reviews of the open ones, derives waiting_on (the author while it is a draft or has changes requested; the requested reviewers; mergeable once approved with nobody else asked; needs_reviewer when nobody has been asked), and upserts. A PR is linked to a task by, first match wins: a link already stored on the PR row (update_task sets it), a task whose pr_url names the PR (create_task with pr_url), or T-<id> in the title or body or a branch named t<id>-.... A task linked by convention learns its pr_url. When a linked PR's state becomes merged, the task gets the note "PR #57 (jack.rayner) merged: