Refine It

Workflow

1. Identify the artifact and its job.

   • Infer the artifact type, audience, purpose, desired tone, and level of intervention from the prompt and surrounding context.
   • A request naming a specific edit — fix, replace, add, remove, correct — scopes the pass to that edit; refine open-endedly only when asked to.
   • Preserve explicit constraints, factual claims, and decisions. Restructure, merge, reorder, or condense sections when doing so makes the artifact clearer or more useful.
   • Treat operational text — triggers, permissions, labels, statuses, API names, configuration keys, routing and eligibility language — as behavior: polish its wording and grouping, never its meaning.
   • If intent is genuinely ambiguous, ask only the smallest necessary question; otherwise choose the level of intervention that best improves the artifact for its apparent job.

2. Evaluate before rewriting.

   • Look for unclear purpose, weak structure, repetition, vague wording, hidden assumptions, missing context, tone mismatch, overclaiming, and unfinished parts — every section assessed against this list before any rewriting.
   • Check grounding: a concept leaned on before it is introduced is a structural defect that reordering usually fixes. The unit is the concept, not the word — a passage can lean on an idea the reader lacks with no jargon in sight.
   • Separate refinement problems from strategy problems. Improve the current direction decisively without changing the artifact's goal, audience, or operational behavior unless the user asks.
   • If the artifact is already strong for its job, make only light polish or state that no substantive edits are needed; do not invent changes merely to produce a visibly different version.