What problem does it solve? A Markdown deliverable lives in git, but its reviewer works only in Google Docs. This Skill runs that review as numbered rounds without letting the Doc become the source of truth: each round is a fresh Doc built from the repo file, the reviewer's direct edits and margin comments are read back and applied to the file, and the reply to their comments opens the next round. ## Core Features & Use Cases - Round text generation: scripts/round_text.py builds each round from the repo file, stripping license comments and DRAFT markers, and prepending a Doc-only header, a Review status checkbox block, an optional Decisions needed block, and a What-changed reply section. - Read-back diffing: scripts/doc_diff.py compares the Doc read-back against the repo Markdown, normalizing Google Docs conversion artifacts (escaped underscores, smart quotes, synthesized table headers, flattened code blocks) so only the reviewer's real edits, deletions, comment threads, and ticked checkboxes are reported. - Title-based state machine: Doc titles carry bracketed statuses ([DRAFT — your turn], [processed → r<N+1>], [CLOSED → path]) so a flat Drive folder shows whose turn it is, with superseded rounds archived. - Use Case: You finish a spec in docs/2026-09-01-api-design.md and your manager only reviews in Google Docs. The Skill publishes r1 as a Doc, reads back their edits and comments a week later, applies them to the repo file, and publishes r2 with a What-changed reply — repeating until they tick Approved as-is. ## Quick Start Review docs/2026-09-01-api-design.md with my manager in a Google Doc and publish round 1.
