Documentation Rewrite
Rewrite confusing existing documentation into clear, scannable, task-oriented prose without losing any technical fact: it first audits the current doc to catalog every problem — buried steps, undefined jargon, missing prerequisites, broken structure — and locks a clarity checklist, then rewrites the doc to fix exactly those issues while preserving every accurate instruction. Covers documentation rewrite, doc cleanup, clarify docs, improve README, restructure guide, and technical editing. Auditing before rewriting is the point: a small model that first inventories what is wrong rewrites with intent and preserves the facts, instead of producing a prettier doc that quietly drops a critical step.
How it runs
| # | Step | Who runs it | What happens |
|---|---|---|---|
| 1 | Audit the doc | Reviewer | catalog every clarity defect and lock the fix checklist |
| 2 | Rewrite the doc | Copywriter | rewrite to the target structure, fixing every audited defect |
| 3 | Evaluate | Reviewer | Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap. |
| 4 | Finish | Developer | All acceptance criteria met. Stamp a short summary and report DONE. |
Say something like "rewrite this documentation" or "clarify the docs" or "improve the readme" or "clean up this guide" or "restructure docs" in chat to start it.