Review Studio
The Review Studio is where a draft gets marked up and made better. Bring in a document, flag the sections that need work with margin comments, and Quill rewrites exactly those sections in the document's own voice — polished prose that drops back in under your name. Or hand the whole draft to the team for a panel review, where each specialist reads it from their lane and comes back with a verdict.
Two ways to review, one studio. Drive it yourself — comment, then let Quill apply your feedback as clean rewrites — or get friction from the panel, where Cassandra, Kai, Finn and the rest each push back only where they would, phrased the way they'd actually say it. Either way the output is edits to the document, not a chat about it.
❝ Inline comments
Flag any passage with a margin note and a severity — note, concern or blocker.
❝ Rewrites in your voice
Quill applies each comment as document prose, preserving your facts and register.
❝ A panel of experts
The team reads it from their specialties and returns a verdict with margin notes.
❝ Sessions that persist
Park a review mid-stream and pick it back up exactly where you left off.
/review in the composer, or click the Open chip — or jump straight back into a saved session.What it is#
The Review Studio treats a document the way a good editor does: read it, mark the specific spots that need work, and fix those spots without disturbing the rest. It's built around inline feedback — comments anchored to real passages — and it closes the loop by turning that feedback into actual edits, either yours (via Quill) or the team's (via a panel). The result is a revised document, not a list of suggestions you still have to apply by hand.
Bringing in a draft#
Bring in a document — paste it, or pull in a Google Doc — and it opens in the studio ready to mark up. You can open the studio from chat, run /review, or ask Sage to send a draft you've been working on straight into it. From there everything happens on the document itself.
Flagging sections#
Select a passage and leave a margin comment on it — as specific as you like. Each comment carries a severity, so the important ones stand out from the nitpicks:
Comments are anchored to the exact text they mark, so they stay attached to the right spot as you work — and a comment whose anchor text has changed is held back from driving a rewrite until it's re-anchored, so feedback never lands on the wrong paragraph.
Rewriting in your voice#
Once you've flagged what needs work, Quill rewrites only the flagged sections, applying each comment precisely. The cardinal rule: a rewrite is document prose, not a reply — it reads as if you wrote it in one sitting, flowing naturally from the paragraph before into the one after. So a comment that asks "is this true?" gets answered inside the narrative in the document's declarative voice, never with a question or a "here's a tighter version". Facts, numbers and names are preserved unless a comment says otherwise, and each rewrite stays roughly the length of the original unless you asked to expand or tighten.
A panel review#
When you want outside pressure on a draft, run a panel review: the team reads the document and each specialist reviews it strictly from their lane — Cassandra on the data model, Kai on the rollout, Finn on the cost, and so on. Each leaves margin comments only where they'd genuinely push back — risks, errors, unstated assumptions, sharp questions the author must answer before it ships — phrased the way that person would actually say it. They're told to disagree where warranted: you want friction, not applause. Each reviewer returns a verdict and a one-line take:
Comments are verbatim-anchored to the passages they mark and kept tight (a handful per reviewer, blockers reserved for genuine vetoes), so a panel review reads like a real design review — pointed, in-margin, and honest.
Saving & resuming#
Reviews save themselves. A session — the document, your comments, the rewrites — persists on its own, so you can park one mid-review and pick it back up later from the studio's list of saved sessions. Long documents and multi-pass edits don't have to happen in one go.