---
name: google-doc-polisher
description: Create, rewrite, or polish Google Docs, intake docs, playbooks, client docs, briefs, questionnaires, SOPs, and review documents with professional formatting, real heading hierarchy for the left-side Google Docs outline, scannable sections, tables/checklists when useful, and clean executive-ready structure.
---

# Google Doc Polisher

Use this skill when creating or improving any Google Doc, especially when the user asks for better formatting, headers/headings, a left-side outline, a client-facing doc, an intake form, a questionnaire, a playbook, or a polished business document.

## Core outcome

Produce a document that is easy to skim, easy to answer, and professional enough to send to a customer, partner, client, or collaborator.

The document must have:

1. A clear title.
2. Real heading hierarchy: `Title`, `Heading 1`, `Heading 2`, and `Heading 3` where appropriate.
3. Left-side Google Docs outline support by using actual headings, not just bold text.
4. Short sections with useful spacing.
5. Bullets/numbered lists instead of walls of text.
6. A clear “what to do next” or “quick response” section when the recipient needs to respond.
7. Confidentiality / approval / scope notes when the doc requests sensitive material.

## Formatting standards

### Heading hierarchy

Use this structure by default:

- Document title: one `Title` only.
- Major sections: `Heading 1`.
- Questions or subsections: `Heading 2`.
- Subcategories/examples: `Heading 3`.

Do not fake headings by only making text bold. The left-side outline only works reliably when headings are applied as paragraph styles.

### Section design

Prefer this order for intake/request docs:

1. Purpose / what we are trying to build.
2. Time-saving instruction: what to focus on if the recipient has limited time.
3. Priority 1 — required / most valuable inputs.
4. Priority 2 — useful if available.
5. Priority 3 — advanced / optional.
6. Quick response format.
7. Confidentiality / boundaries.
8. What we will do with the input.

### Scannability rules

- Keep paragraphs under 4 lines when possible.
- Use bullets for lists of examples.
- Use numbered lists for steps, priorities, scoring rubrics, or response formats.
- Use bold only for emphasis, not as a substitute for headings.
- Put the most important request near the top.
- Include examples, but label them as examples.
- If asking a busy person for input, separate “must-have” from “nice-to-have.”

## Google Docs execution rules

When creating or editing a Google Doc through the browser:

1. First draft the content locally in Markdown or HTML.
2. Convert the structure into heading-friendly content.
3. Paste/insert into Google Docs.
4. Verify the left-side outline has headings.
5. If the outline says “Headings you add to the document will appear here,” the doc is not done.
6. Fix by applying Google Docs paragraph styles to headings.

### Applying heading styles manually

If pasting formatted text does not create real Google Docs headings:

1. Select the document title and apply `Title`.
2. Select each major section and apply `Heading 1`.
3. Select each subsection/question and apply `Heading 2`.
4. Select lower-level categories and apply `Heading 3`.
5. Re-check the left outline.

Keyboard shortcuts in Google Docs are usually:

- Title: use the Styles dropdown.
- Heading 1: `Cmd+Option+1` on Mac.
- Heading 2: `Cmd+Option+2` on Mac.
- Heading 3: `Cmd+Option+3` on Mac.
- Normal text: `Cmd+Option+0` on Mac.

Use the Styles dropdown if keyboard shortcuts do not work.

## Recommended output sections

For a polished intake doc, use:

```markdown
# [Document Title]

## Quick Context
Short explanation of the goal.

## If You Only Have 15 Minutes
The exact 3–5 things to provide first.

## Priority 1 — Most Valuable Inputs

### 1. [Input Type]
What to provide, why it matters, and examples.

### 2. [Input Type]
What to provide, why it matters, and examples.

## Priority 2 — Helpful If Available
...

## Quick Response Format
1. ...
2. ...

## Confidentiality Note
Do not share private/proprietary information unless allowed.

## What Happens Next
How the input will be used.
```

## Quality checklist before saying done

Before finalizing a doc, verify:

- The title is clear and specific.
- The left-side outline shows meaningful headings.
- No long wall-of-text sections remain.
- The recipient can answer without a meeting if needed.
- The most important asks are near the top.
- Sensitive/confidential material has guardrails.
- Any shared doc has the right editors/viewers.
- If emailed/shared, delivery is verified.

## Bundled helper

Use `scripts/md_to_polished_doc_html.py` to convert Markdown into clean HTML for pasting/importing. It improves spacing and heading visual hierarchy, but still verify that Google Docs created real heading styles afterward.