v0.8.1 — /design external-review-handoff option
Patch — additive only, no breaking changes. Adds an external-review-handoff option as an alternative to the block-by-block inline review in the /design skill.
Dogfood-driven amendment from plan #6's first real design exercise (MemoryVault, authored 2026-05-15): the 6-chunk inline walk of a ~7200-word design surfaced a real UX gap. Antigravity IDE's native inline-comment UI + Gemini-applies-comments pattern is dramatically better for review-style work on long content; this option lets operators reach for that workflow.
What's new
Three skill points get the new option:
/design authorStep 5 — alternative to "Ready for review" inline transition/design authorStep 6 — alternative to per-section Approve/Revise/Skip walk onStatus: reviewdocs/design translateStep 4 — alternative to inline Reshape commands on proposed part split
Mechanics
- Pre-handoff snapshot at
<target-doc>.pre-handoff-<ts>.md— Claude diffs against this on resume to detect what changed. - Transfer-context file at
<project>/.harness/transfer/<doc-slug>-<ts>.mdfrom the new template atskills/design/templates/transfer-context.md. Inlines operator intent, recent decisions to honor, dev-flow conventions, doc-type-specific guardrails, and explicit MUST-NOT rules. - Handoff prompt output to operator with explicit Antigravity steps: open target doc + transfer-context, comment via Antigravity's native UI, ask Gemini to apply per the transfer-context. Gemini revises + writes change-summary log at
<target-doc>.diff.md. - Resume flow (
/design author <slug> --resume-external-reviewor natural "review complete on "): Claude reads revised doc + change-summary, diffs against snapshot, surfaces findings (applied changes / frontmatter modifications / "Recent decisions" overrides / Gemini's adjacent-issue suggestions), asks Accept / Iterate / Discard.
Paired release
Paired with agentic-harness v2.3.1, which adds the same option to the harness /plan phase. Shared transfer-context template, shared workflow shape, shared cleanup discipline across both repos.
Design rationale
ADR 0004 amendment (2026-05-16) covers:
- Rejection of the comment-marker-convention alternative (Antigravity has native inline-comment UI; inventing a marker convention adds friction; Gemini-in-Antigravity handles application natively).
- Pre-handoff snapshot as the silent-drift safety net.
- Multi-round iteration support via transfer-context regeneration.
- 4 load-bearing assumptions with explicit re-audit triggers (after first 3 handoffs / first multi-round cycle / first 5 handoffs / at retrospective #12).
How to use
See the new Scenario 4 in Use-The-Design-Skill for the end-to-end worked flow + decision rubric (when to pick external vs. inline).
Pattern
First dogfood-driven amendment to a shipped toolkit skill. Pattern: ship v1, dogfood on a real exercise, surface gaps, ship a small patch with the amendment captured in the ADR. Re-audit triggers in the amendment fire after the next 3-5 real external-review handoffs.