name: proofread
description: "Polish any PM document for grammar, clarity, structure, and professional impact. Routes to the grammar-check skill."
argument-hint: "[paste the document you want reviewed, or describe what you're writing and share a draft]"

Proofread

This skill routes to grammar-check, which provides expert-level PM writing review across grammar, clarity, logic, structure, and document-type-specific best practices.

When to use this:
- Before sending a PRD, strategy doc, or email to engineering, design, or leadership
- Polishing a pitch deck, executive summary, or board update
- Reviewing release notes, change logs, or customer-facing documentation
- Strengthening a career document: LinkedIn summary, promotion write-up, performance review

Quick review depth guide:
- Quick grammar and spelling pass → grammar-check handles this as part of any review
- Full clarity and structure review → grammar-check applies BLUF (Bottom-Line-Up-Front), Minto Pyramid, and document-type standards
- Executive communication → grammar-check applies executive writing principles: lead with the recommendation, data first, no burying the lede
- PM document (PRD, spec, brief) → grammar-check applies document-type-specific structure checks (problem before solution, metrics before design, non-goals explicit)

What grammar-check covers:
- 7-dimension review: grammar/mechanics, clarity, conciseness, active voice, PM tone calibration, logic/flow, precision
- Document-type-specific standards:
- PRD: problem statement quality, metric placement, non-goals, passive voice, vague requirements
- Executive email/memo: BLUF structure, "so what" clarity, length for the audience
- Strategy document: Minto Pyramid logic structure, recommendation first, evidence second
- Release notes: customer-centric language, benefit-first framing, version clarity
- Customer communication: tone calibration (formal vs. casual), jargon removal, call to action clarity
- Before/after rewrites for weak sections — not just identifying problems but showing fixes
- Anti-patterns by document type with examples
- Data presentation: numbers with context, percentages vs. absolute numbers, comparing to benchmarks
- Passive voice detection and active voice rewrites
- Vague language audit: "some," "many," "soon," "better," "significant" — replaced with specifics

The skill will:
1. Ask for the document (or the type if text is not yet provided)
2. Identify the document type and apply the relevant standards
3. Review grammar, clarity, conciseness, and active voice
4. Check logical structure and flow using BLUF or Minto Pyramid as appropriate
5. Deliver specific, line-level feedback — not generic commentary
6. Rewrite the most impactful sections to show the improved version
7. Flag any tone mismatches (too casual for an exec, too formal for a dev team)

Load the full skill: grammar-check

Apply your document to: $ARGUMENTS