Foundry-specific conventions for reviewing and annotating documents. How to refine docs via Foundry's annotation system — highlighting, threading, resolving. Use when refining a Foundry doc, reviewing annotations, or when the /refine command targets a Foundry page.
When refining or reviewing a document in Foundry, follow these conventions for annotations. This skill is invoked automatically by /refine when the target is a Foundry doc.
quoted_text to reference the specific text you're commenting on. Annotations without highlighted text are harder to trace back to the content.parent_id rather than creating new top-level annotations. Keep the conversation attached to the original concern.resolve_annotation. Don't leave resolved items as submitted — it clutters the view.get_page to understand the complete doc before commenting. Don't skim-review.submit_review to group your annotations into a coherent review batch.quoted_text)section field to anchor the annotationlist_annotations before starting — don't duplicate feedback that's already been given.resolve_annotationparent_id)| Context | Focus | Tone |
|---|---|---|
| Design doc refinement | Architecture, scope, assumptions, risks | Challenging — poke holes |
| Story review | Acceptance criteria, completeness, clarity | Precise — is this implementable? |
| QA report | Evidence, coverage, edge cases | Factual — show the receipts |
| Code review (via Foundry) | Intent, approach, alternatives | Constructive — suggest, don't just criticize |