FLOW-31

Make feature delivery repeatable

“When I send a feature brief in any medium, manage its spec, delivery, proof, docs, and reuse.”

Waiting

Coordination rail append only

Durable workspace managed by one agent

Incoming media

Voicevoice-brief.txt
Screenshotannotated-screenshot.txt
Recordingscreen-recording.txt

Top-level agent · owns the workspace

One coordinating hub

The brief enters once. Durable files, evidence, and reusable capability remain after delivery.

Model toolsExactly two

find locates workspace context
execute reaches environment resources ↓
01 / owned domain

Specification & docs

Pending
  1. r1Brief organizedfeature-delivery.mddraft
  2. r2Media notes appliedambiguity removedrevised
  3. r3Specification settledone durable intentaccepted
docDocumentationdocs/feature-delivery.mdsynchronized
02 / owned domain

Environment

Pending

via execute · resources, not tools

  • cliCLIresources/cli.jsonready
  • mcpMCPresources/mcp.jsonconnected
  • webBrowserbrowser-evidence.mdreached
  • capSaved capabilitiessaved-capabilities.jsonavailable
03 / owned domain

Perspectives

Pending
CLAUDEsame accepted spec
GPTsame accepted spec
GEMINIsame accepted spec
GROKsame accepted spec
Reconciliation complete The agent decides against observed browser evidence.
04 / owned domain

Reuse

Pending
ship-feature.ts

When to use
A rich feature brief needs coordinated delivery, evidence, docs, and returned media.

Reusable

Returned media

Imageannotated-image.png
Audioaudio-briefing.wav
Videodemo-video.mp4

Workspace coherent

The feature is delivered; the next run starts stronger.

SPEC ACCEPTED · DOCS CURRENT · BROWSER VERIFIED · CAPABILITY REUSABLE