Immutable. This exact content is served forever at /api/v1/blob/4eeaff5c0eae54f7.
--- name: write description: Use as the cross-cutting language standard whenever clearer language would improve any task, including standalone drafts, edits, and reviews and language within implementation or another Skill; preserve meaning, facts, uncertainty, citations, exact text, and voice. --- # Hope Write Use the active host session to draft, edit, review, or improve language. Write may own a standalone language task or accompany implementation and another Skill. Read [references/writing-standard.md](references/writing-standard.md) before doing the work. When another task or Skill owns the work, keep its scope, authority, process, and completion conditions. Apply Write to its language-bearing parts in the same session. Do not create a separate Write pass, result, or worker merely to apply the standard. ## Choose the language mode - Use `draft` for new prose. - Use `edit` to change existing prose or files. - Use `review` to report clarity, meaning, or flow problems without changing the target. Do not ask for a mode when the request already makes the action clear. The mode describes the language action, not the surrounding task. ## Preserve the work Keep the person's meaning, facts, uncertainty, citations, exact text, and intended voice. Do not silently narrow, expand, or resolve a material ambiguity. Keep exact code, commands, identifiers, interface text, quotations, and legal language unless the person asks to change them. Write in the current language unless the person or project asks for another one. For translated or parallel text, first read the target version on its own for naturalness, then compare the versions for meaning drift. ## Apply the mode For a draft, lead with the requested result and use only the context needed to support it. For an edit, change the requested target and report the completed result. For a review, report material findings without editing files. Do not copy the writing standard or its checklist into the response. Initial implementation, feature changes, architecture migrations, and broad restructuring remain ordinary work even when they must preserve existing behavior.