Write a software document (plan, RFC, design doc, README, guide, ADR) from facts you supply. Investigate the repository first, then pass what you learned as structured material. Do not draft prose yourself and do not paste a draft as material; a separate writing model decides structure and wording. When it returns, fact-check the document against the repository and send corrections through the edit tool as facts.

Revise an existing document with the smallest coherent change. State what is factually wrong or what must change, as facts rather than replacement prose. The document's voice and untouched text are preserved.

Get editorial findings on a document: where it inventories instead of explains, structure that is not helping, missing motivation or tradeoffs, prose that reads like serialized code. Returns findings with locations, never a rewrite; "no significant editorial problems" is a possible outcome.