annotation

Objective

Run a review loop where humans annotate an existing draft and Agents respond block-by-block, then apply the agreed edits directly to the document.

Scope

1. Start only after a draft already exists.
2. Treat this skill as post-draft review handling, not initial document writing.
3. Repeat the same workflow for each review round.

Required behavior

1. Locate the reviewed document (for example PLAN.md) and read the latest full content before editing.
2. Detect three review signals:
   • Added content (new paragraphs or explicit add/insert instructions).
   • Deletion intent (removed text, strike-through text, or explicit delete/remove instructions).
   • Paragraphs containing === markers.
3. Split detected signals into independent review blocks.
4. For each block in the current round, do all of the following:
   • Infer likely intent from surrounding context.
   • Reply with the intended action briefly.
   • Apply the edit directly to the document.
5. Keep unrelated sections untouched.
6. Remove temporary collaboration markers (including ===) after applying edits, unless the user explicitly asks to keep them.
7. Finish the round with a concise per-block response so humans can continue the next review cycle.

Intent inference rules

1. Treat user annotations as guidance, not final wording.
2. Prefer the simplest interpretation that keeps structure, tone, and terminology consistent with nearby sections.
3. If one block is ambiguous, choose a conservative edit that is easy to iterate.
4. If an edit could change critical meaning, keep existing facts and adjust phrasing instead of inventing new claims.
5. When two signals conflict, prioritize:
   • Explicit user instruction.
   • Document consistency.
   • Minimal-risk change.

Per-block response format (each review round)

Use a compact list with one item per block:

• Block: short locator (heading or first words)
• Signal: ADD, DELETE, or ===
• Interpretation: what the user likely wants
• Applied: what was changed in the document

Editing checklist

1. Ensure each detected block has both a response and an applied change.
2. Ensure no accidental edits outside targeted blocks.
3. Ensure no unresolved === marker remains unless explicitly requested.
4. Re-read neighboring paragraphs to keep flow and references consistent.

Fallback

If no review signals are found, report that no ADD/DELETE/=== blocks were detected in this round and wait for the next annotated review.