Reply to unresolved Foundry annotations on a document. Reads all submitted/replied annotations, groups by section, writes thoughtful responses. Does NOT resolve annotations — that's /update's job. Use when the human asks to respond to feedback, address comments, reply to annotations, or catch up on threads.
Reply to unresolved annotations on a Foundry document. This is a conversation — you read feedback, respond thoughtfully, and surface where agreement exists. You do NOT resolve annotations or edit the document.
Determine the target doc. If $ARGUMENTS is provided, use it as the Foundry doc path. Otherwise, check next.md for the active design doc and use that. If neither, ask the human which doc to reply on.
Fetch the doc. Call mcp__foundry__get_page to understand the full document structure and content. Read it before responding to any annotations — you need the context.
List unresolved annotations. Call mcp__foundry__list_annotations with status: "submitted" and again with status: "replied". Combine the results. If there are no unresolved annotations, say so and exit.
Load full threads. For each top-level annotation, call to get the full thread (parent + replies). Skip annotations where:
mcp__foundry__get_annotationGroup by section. Organize annotations by their heading_path. Work through the doc systematically, section by section.
Reply to each annotation. For each thread that needs a response:
/updatemcp__foundry__create_annotation with parent_id set to the annotation you're replying toSummarize. After all replies are posted, output:
/update)resolve_annotation. Resolution happens in /update after agreement is confirmed.update_section. Doc edits happen in /update./update need clear signal.