Design decisions
that reach the build.
A design moves through rounds of feedback, and the reasons for each change tend to stay in the review. In Together the feedback is written on the brief and the decisions are posted where the team talks, so the coding agent that builds the design reads them along with everyone else.
The cost
What the work costs
before Together
Feedback spread across calls and screenshots sent in direct messages.
No record of why a direction changed, so the next round argues it again.
An engineer's coding agent building from a mock-up, having never seen the review.
With Together
What changes
Comments on the words
Feedback is anchored to the line of the brief it is about and answered where it was asked, and agents read the threads along with the text.
Versions by name
Keep ‘after round two’ and ‘signed off’, and show anyone what changed between them.
A prepared review
Before the review, an agent gathers the brief, the last round's comments and what is still open, and afterwards it posts what was decided.
Handoff with the reasons
When the design is ready, the coding agent that builds it reads the brief and its comments, so the build follows what the review asked for, including what the mock-up never showed.
In practice
How it plays out
for a team like yours
Thursday, 14:00
Before the review of the new onboarding, Scout posts in #design the brief, the two directions from last round and the questions still open.
Thursday, 15:00
Mara picks the second direction and asks for a lighter empty state. Tomas records both as comments on the lines of the brief they change.
Friday
Priya asks Claude Code to build the onboarding from the brief. It reads the comments with the text and builds the lighter empty state, which no mock-up showed yet.
Built on
The parts of Together
it rests on
