Blocker/question aggregation queue

done priority 2 estimate M

workspace-dashboard/002 · created 2026-08-05 · updated 2026-08-12 · blocked by workspace-dashboard/001

What to do

Build the “what needs Kris?” queue — the dashboard’s core feature per overview.md’s constraint 5. Note: this task’s scope shrank significantly during this same session — the “exact structured format for agent-written blockers/questions” that overview.md originally listed as an open question is now answered by the project-wide Question object (epics/<epic-id>/questions/NNN-slug.md, see epics/README.md), built for other reasons this session. This task is now “build a view over the existing mechanism,” not “invent a new format.”

Scope addition from Kris (2026-08-04), verbatim intent: the dashboard must answer, at a glance, “are there any tasks ready for AI agents to work on, and if not, what are the blockers?” — he asked an agent exactly this question today and the answer required grepping every epic’s status.md by hand. So the queue is not only open questions: it must also surface, across all epics, anything agent-ready, anything in review waiting on Kris, and anything needs-human-decision — i.e. the tag/next fields that already exist, aggregated into one view.

Definition of done

A view (can start as the already-built /questions site page) that aggregates every status: open question across every epic — plus the at-a-glance answer to “what’s agent-ready / what’s waiting on Kris” described above (epic tags + next lines aggregated, not just questions).

Built 2026-08-04 — in review

Shipped as /now (first item in the site nav; /questions redirects there; /questions/index.json unchanged). Sections in queue order: Waiting on my review (tasks in review, each with its review_artifact path as copyable text) → Open decisions → Ready for agents → Blocked-and-why (epic next: lines). Supporting changes shipped alongside: new derived epic tag needs-review (a task in review no longer hides an epic as “blocked”), new optional task field review_artifact:, gold “needs Kris” chips on the epic board, epic next: lines on the index cards, and a build timestamp in the footer (stale stamp = dead deploy watcher). Prioritisation rule used (assumption — the Q001 this file used to reference was never actually created): review first, then questions oldest-first, then ready, then blocked. Kris reviews the live page and moves this to done if it answers his question.

Where the work lands

site/ in this workspace repo.

Docs to read first

epics/README.md (the Question schema); the site’s existing /questions page, if built by the time this task is picked up.

View source in repository · also available as raw markdown.