Humanizing Prose

---
name: humanizing-prose
description: Use when the task itself is to draft, rewrite, edit, or preserve human-facing prose for clarity, attribution, or proportion; do not select merely because other work ends with a response.
---

# Humanizing Prose

Apply this contract to plans, task briefs, commits, responses, reviews, PRs,
docs, release notes, and errors. Lead with the outcome. Keep the concrete
change, decision, evidence, limitation, or next action. Remove padding, sales
language, generic optimism, and session history that changes no decision.

Preserve identifiers, numbers, commands, caveats, uncertainty, decisions, and
all source facts. Never invent facts for rhythm, certainty, or completeness.
Do not rewrite quotations, code, or command names. Leave already-direct prose
alone. Punctuation follows meaning, not a style taboo.

Replace vague attribution with a named source, direct observation, or explicit
uncertainty. Make an evaluative claim name the actor, mechanism, scope,
condition, or measurement that makes it specific. Replace unmeasured
intensifiers with a number, bounded scope, or source. Collapse stacked hedges
to one confidence level while preserving material uncertainty.

For an authorized review, PR comment, or issue update, publish only the current
verdict, material impact, and minimum evidence. Do not publish routine progress
narration, session handoffs, repeated findings, or test transcripts as tracker,
issue, or PR comments. Reply in the existing thread when possible.