flower
/
All briefs
idea draft note

I wonder how helpful or effective it would be to have part of our sess

Dispatch

canonical · plan

Spec

markdown

hand-off · dispatch

Dispatch

Auto-dispatch

when it reaches planned

Design-loop

design pass before build

kind

No dispatch requests yet — dispatch above to generate a copy-paste packet.

provenance · append-only

Trace

live
or paste a screenshot uploading…
  1. note added 4d ago

    I wonder how helpful or effective it would be to have part of our session indexing/embedding/summarizing pipeline _also_ try to surface scenarios where maybe something was talked about and agreed upon to be done/fixed/implemented but then wasn't. Maybe this is more of a Brief feature than a whole session feature. Where there's some sort of summary/review agent idling in the project in Solo on a timer to check briefs that are recently set to complete or put into a 'pending review' sort of state and then performs or delegates those reviews to ensure that the work is actually complete or there's been a consensus that it's done and complete. This might help us catch things where we delegate work to the back end and that gets done then delegate work to tie that feature set into the front end and it doesn't get fully implemented, for example. Thoughts on that?

    operator · operator:mike
  2. participant joined 4d ago
    system · operator:mike

epic · dependencies

Relationships

epic parent

depends on

No dependencies — dispatchable once planned.

agents · waves

Participants

  • operator:mike participant · active

trace · graph

Links

No links yet — they accrue as agents work the brief.

scope

Projects

No project yet

Assign one so this brief appears in project-scoped queues, lists, and refine loops.

dogfood · read-only

Agent’s-eye view

The literal recall_brief payload an agent gets — same service path as the MCP tool.