From f7022bbd17755b83732ff423fb41e565d8f9b2c5 Mon Sep 17 00:00:00 2001 From: garrytan Date: Thu, 8 Oct 2026 06:20:39 +0000 Subject: [PATCH] fix(office-hours): print the full design doc inline before asking for approval (#879) Tool output collapses in Claude Code, so users were asked to approve a doc they could not see. Port of @RyanAlberts's PR #1116 into the carved design-and-handoff section. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- office-hours/sections/design-and-handoff.md.tmpl | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/office-hours/sections/design-and-handoff.md.tmpl b/office-hours/sections/design-and-handoff.md.tmpl index 9f1f5c68b..f3c88f914 100644 --- a/office-hours/sections/design-and-handoff.md.tmpl +++ b/office-hours/sections/design-and-handoff.md.tmpl @@ -167,6 +167,19 @@ Supersedes: {prior filename — omit this line if first design on this branch} --- +**Before asking for approval, output the full design doc inline.** + +Print the complete contents of the design doc as direct assistant text in the +conversation — do NOT ask the user to open the file, and do NOT rely on a +`Bash cat` or `Read` tool call to show it. Tool outputs are frequently +collapsed in the Claude Code UI, which leaves the user approving a document +they cannot actually see. The one place the full doc is guaranteed to render +is the assistant message itself. + +Format: a short preamble (`Here is the design doc saved to {path} — please +review before approving:`) followed by the verbatim document body. Then +proceed to the AskUserQuestion below. + Present the reviewed design doc to the user via AskUserQuestion: - A) Approve — mark Status: APPROVED and proceed to handoff - B) Revise — specify which sections need changes (loop back to revise those sections)