Prep That Doc

Review engineering Markdown for its purpose, audience, and destination. Preserve author intent and technical meaning. Style review identifies clarity and information gaps; it does not verify facts or system behavior.

Route The Request

Default to review when no editing intent is given. An explicit request to write, fix, improve, or rewrite authorizes edits within the named scope. Preserve the user's requested report format.

• review: Report findings and questions; leave files unchanged.
• fix: Apply justified edits, verify preservation, and report unresolved issues.
• roast: Critique with evidence; leave files unchanged. Read roast guidance only when requested.

Use the review workflow for detailed guidance.

Infer purpose, audience, destination, and scope from the request, files, and project conventions. State material assumptions. Ask only when ambiguity blocks an action; review can continue.

For a localized typo or wording fix, inspect local context, edit, compare with the original, and give a brief confirmation. Stop there; do not enter the broader review workflow or raise unrelated completeness questions. Scan only if it checks the requested change. Broader work uses the workflow below, scaled to complexity and risk.

Core Checklist