778fe1d321
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>
53 lines
1.6 KiB
Markdown
53 lines
1.6 KiB
Markdown
---
|
|
kind: epic
|
|
slug: task-as-runnable-unit
|
|
title: Task as runnable unit — workflow prompts and a runs table
|
|
plan_slug: agent-coordination
|
|
status: ready
|
|
priority: P2
|
|
tenant_id: global
|
|
cursor_epic_id: null
|
|
updated_at: "2026-06-01"
|
|
---
|
|
|
|
# Epic objective
|
|
|
|
Every backlog item can carry a workflow prompt; every agent session against a task gets recorded in a `runs` table. These two changes are the foundation that `claim_task` / `complete_task` build on.
|
|
|
|
## In scope / out of scope
|
|
|
|
**In scope**
|
|
|
|
- Schema additions for workflow prompts.
|
|
- New `runs` table + tRPC router.
|
|
- Minimal UI for editing the prompt and viewing recent runs.
|
|
|
|
**Out of scope**
|
|
|
|
- The actual MCP tools (next epic).
|
|
- Orchestrator process (deferred epic).
|
|
|
|
## Related tasks
|
|
|
|
| Task | Link |
|
|
|------|------|
|
|
| Add workflow prompt to backlog items | `./Task-add-workflow-prompt-to-backlog-items.md` |
|
|
| Runs table and tRPC router | `./Task-runs-table-and-trpc-router.md` |
|
|
|
|
## Dependencies
|
|
|
|
- Depends on: `Plan-daily-driver-finish` (don't extend stubs).
|
|
- Blocks: `Epic-mcp-claim-complete`.
|
|
|
|
## Acceptance criteria
|
|
|
|
- [ ] A task row can store an optional workflow prompt that overrides the epic/plan default.
|
|
- [ ] A `runs` row captures `started_at`, `finished_at`, `actor_user_id`, `outcome`, `tokens_input`, `tokens_output`, and `notes`.
|
|
- [ ] Minimal UI lets an operator read a task's effective prompt and recent runs.
|
|
|
|
## Proposed timeline
|
|
|
|
| Phase | Window | Notes |
|
|
|-------|--------|-------|
|
|
| Schema + procedures | Day 1 | Columns, table, tRPC router. |
|
|
| UI surfacing | Day 2 | Inline prompt editor, recent-runs panel. |
|