Randall Stillwell 778fe1d321 plans: scaffold daily-driver-finish, saas-hardening, agent-coordination

Three new plan trees that fill in the gaps surfaced during repo review.
Together they map out what remains between the current scaffold-with-stubs
state and a daily-usable, multitenant, agent-coordinated app.

* Plan-daily-driver-finish (P0): turn stubs into real data. Five tasks
  covering the lint/shared-types breakage, hardcoded dashboard mocks,
  AI-page setTimeout placeholder, post-signin landing decision, and a
  cross-browser collab smoke test against the deployed Hocuspocus
  instance.

* Plan-multitenant-saas-hardening (P1): everything multitenant needs
  beyond what Plan-multitenant-cursor-sync already covers. Invites and
  role management, soft-delete + append-only audit log, rate limits on
  the auth + mutation hot paths, and a Vitest + GitHub Actions test
  foundation so PRs can't ship red.

* Plan-agent-coordination (P2): the layer that makes a Task-*.md
  runnable, not just readable. Adds workflow_prompt with task -> epic
  -> plan inheritance, an agent_runs table for auditable sessions, and
  two new MCP tools (claim_task / complete_task) that replace the
  freeform update_object composition agents do today. Includes an
  intentionally-deferred Epic-optional-orchestrator that captures the
  Symphony-shaped runner as a decision point rather than an immediate
  build.

Each task is bead-scale (one focused Cursor session) with explicit
in-scope, out-of-scope, and anti-goal sections so a future agent can
pick up a single Task-*.md and start without scrollback context.

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-06-01 23:52:22 -05:00

1.8 KiB

Raw Blame History

kind	slug	title	plan_slug	status	priority	tenant_id	cursor_epic_id	updated_at
epic	mcp-claim-complete	MCP claim_task and complete_task — atomic lifecycle for agents	agent-coordination	ready	P2	global	null	2026-06-01

Epic objective

Add two MCP tools that give a coding agent a shaped lifecycle for a task: claim_task (status flip + open agent_runs row + return effective workflow prompt) and complete_task (status flip + close agent_runs row with outcome + tokens).

These replace the current freeform composition where an agent has to call update_object repeatedly and pray.

In scope / out of scope

In scope

New MCP tools claim_task and complete_task with zod schemas.
Idempotency rules (don't double-claim).
Integration with the agent_runs table from the previous epic.

Out of scope

A long-running orchestrator (deferred epic).
A pause_task / resume_task tool. Resist; you can model that with two complete_task calls (cancelled + a new claim) until evidence demands it.

Task	Link
MCP claim_task tool	`./Task-mcp-claim-task-tool.md`
MCP complete_task tool	`./Task-mcp-complete-task-tool.md`

Dependencies

Depends on: Epic-task-as-runnable-unit (needs workflow_prompt and agent_runs).

Acceptance criteria

An agent can call claim_task({ workspace, backlogItemId }) and receive the effective workflow prompt + a runId.
An agent can call complete_task({ runId, outcome, tokens, notes }) to finalize.
Double-claim of the same task by the same actor returns the existing open run; by a different actor returns an explicit "already claimed by X" error.

Proposed timeline

Phase	Window	Notes
claim_task	Day 1	Tool + idempotency.
complete_task	Day 2	Tool + run finalization.

1.8 KiB Raw Blame History