flower
/
All briefs
idea draft note home-tracker

Ability for the home tracker project specifically to be able to take i

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

    Ability for the home tracker project specifically to be able to take input of what will/would be essentially a new brief. Use case being my wife isn't very tech-ie but is a streamer and is using computers all day - often times she'll express to me an annoyance/issue and I'm like... "We could build something for that..." but never do cause I never remember. Would be nice for her to have a place that she can just issue requests to me/AI that are handled similarly to these briefs - not directly, but similarly. Where possible to handle with a chat/research session - that should be the route. If it's something we'd build - we'd want to expose the ability to push it to a brief in flower for me and you to take over.

    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

  • home-tracker · primary

dogfood · read-only

Agent’s-eye view

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