Rewrite and standardize a set of docs in a folder
Update docs for tone, style, and consistency across a folder.
Last tested Feb 25, 2026
Access Scope
Local Folders
Permitted Actions
Why these permissions? Read access to audit and process documents; write access to save revised versions alongside originals. Rename and delete are not granted — original files are always preserved.
Workflow Steps
Audit current docs for style issues
Start read-only. List issues before making any changes.
Define the style guide
Tell Cowork the exact style rules to follow.
Rewrite the first document as a test
Start with one document to verify the output before processing all.
Save the approved version and continue
After approving the test, Cowork processes the remaining documents.
Create a changelog
Document what changed for future reference.
Cowork Prompt Pack
Cowork-readyRead all documents in my folder (read-only). Audit each for tone, style, and formatting issues. List problems per document. Do not make any changes.
Verification Checklist
0 of 4 verified
Why this workflow matters
Documentation is rarely consistent. Different authors use different styles, heading levels, formatting conventions, and tone. A single folder of docs might have some in Markdown, some in plain text, some with inconsistent capitalization or punctuation. Fixing that manually means reading every file multiple times and making the same edits repeatedly.
With Cowork, you set one style guide and let Claude apply it uniformly across all documents. Tone becomes consistent, heading hierarchy standardizes, formatting unifies. You end up with professional-looking docs that are easier to maintain, search, and update.
This is ideal for:
- • Documentation teams onboarding new writers or consolidating older docs
- • Product teams standardizing API docs, guides, and release notes
- • Legal/compliance ensuring templates and forms follow consistent formatting
- • Any team with docs written by multiple people over time
Creating your style guide
Before running this workflow, write down your style rules. The more specific, the better Claude's output. Here's what to include:
Style guide checklist:
- • Tone: Formal, friendly, technical, conversational?
- • Heading hierarchy: H1 for title, H2 for sections, H3 for subsections?
- • Lists: Bullet points or numbered? How many levels?
- • Capitalization: Title Case or sentence case for headings?
- • Formatting: Bold for emphasis, code blocks, quoted sections?
- • Length: Prefer short paragraphs or longer prose?
- • Terminology: Specific terms that must be used consistently?
Step-by-step process
1. Audit first (read-only)
Start with the safe prompt to see what style issues exist. Don't modify anything yet. This gives you confidence before making changes and confirms which files need work.
2. Test on one document
Pick a small, non-critical document. Ask Cowork to rewrite it using your style guide. Review the output carefully. Does it match your expectations? Make adjustments to your guide if needed.
3. Review before bulk processing
Once the test doc looks right, ask Cowork to show you a preview of changes for 2-3 more documents. Verify the pattern is consistent before processing the entire folder.
4. Process all documents
Once approved, Cowork processes the remaining docs. Original files are preserved (with -revised suffix), so you can compare before committing to the new versions.
Tips for best results
Be specific about tone: "Friendly but professional, avoid jargon" is more useful than "professional." Give examples of good vs. bad tone.
Preserve originals: Always keep the original files. The -revised versions let you compare and rollback if needed. Never delete originals until you're certain.
Handle special sections carefully: If some docs have code blocks, tables, or special formatting, tell Cowork which sections to preserve as-is.
Iterate on examples: Show Cowork an example of a "before" section and an "after" version. This helps it understand your style better than descriptions alone.
Common questions
What if my documents are in different formats?
Cowork can standardize docs in mixed formats (Markdown, plain text, PDF excerpts), but it works best when all inputs are text-based. If you have Word docs with complex formatting, consider exporting them as plain text first.
Can I standardize just headings or just tone?
Yes. Tell Cowork exactly what to change: "Fix only the tone. Do not touch headings or structure." This gives you fine-grained control over what gets updated.
How do I handle documents that shouldn't change?
Don't put them in the folder. If they must be included, label them clearly: "Do not modify LICENSE.md or CHANGELOG.md." Cowork can skip specific files if you ask.