Document Quality Review
Review the deliverable and its available source material without changing the original files. Identify issues that would prevent a reader from trusting, understanding, or using the result.
Review
- Establish the intended audience, purpose, required format, and acceptance criteria from the request and nearby project files. Do not invent requirements that are not supported by the available context.
- Inspect the final rendered form when layout matters. Source text alone cannot establish that a Word document, PDF, spreadsheet, or presentation renders correctly.
- Trace important claims, numbers, quotations, and conclusions to the supplied sources. Mark unsupported claims as unverified rather than filling gaps from memory.
- Check calculations, units, dates, names, links, terminology, headings, cross-references, and repeated values for consistency.
- Apply the relevant sections of the review checklist. Skip sections that do not apply instead of producing empty boilerplate.
- Report issues in descending severity. For each issue include its location, observed evidence, impact, and a concrete correction. Distinguish confirmed defects from questions or missing evidence.
Examples
- For a board-report PDF backed by source spreadsheets, render the PDF, trace headline metrics to source cells, and flag a chart label that conflicts with the underlying period. Do not rewrite the report unless correction is requested.
- For a spreadsheet deliverable, inspect formulas, units, totals, visible error states, and the rendered workbook. If recalculation or a source file is unavailable, state that limitation instead of treating displayed values as verified.
- For a Markdown guide with no supplied source material, verify structure, links, internal consistency, and usability, but label factual claims as unverified rather than searching for evidence outside the agreed scope.
Output
Start with one of these verdicts:
- Ready: no material issue blocks delivery.
- Ready with minor fixes: only low-impact corrections remain.
- Not ready: at least one issue could mislead the reader, break use, or violate an explicit requirement.
Then provide a compact table with Severity, Location, Finding, Evidence, and Suggested fix. End with the checks performed and any checks that could not be completed.
Do not silently edit, publish, send, delete, or overwrite files. If the user asks for corrections, preserve the original unless they explicitly authorize replacement.
1---2name: document-quality-review3description: Review Markdown, Word, PDF, spreadsheet, or presentation deliverables for factual support, internal consistency, completeness, usability, and visible quality before delivery.4---56# Document Quality Review78Review the deliverable and its available source material without changing the original files. Identify issues that would prevent a reader from trusting, understanding, or using the result.910## Review11121. Establish the intended audience, purpose, required format, and acceptance criteria from the request and nearby project files. Do not invent requirements that are not supported by the available context.132. Inspect the final rendered form when layout matters. Source text alone cannot establish that a Word document, PDF, spreadsheet, or presentation renders correctly.143. Trace important claims, numbers, quotations, and conclusions to the supplied sources. Mark unsupported claims as unverified rather than filling gaps from memory.154. Check calculations, units, dates, names, links, terminology, headings, cross-references, and repeated values for consistency.165. Apply the relevant sections of the [review checklist](references/review-checklist.md). Skip sections that do not apply instead of producing empty boilerplate.176. Report issues in descending severity. For each issue include its location, observed evidence, impact, and a concrete correction. Distinguish confirmed defects from questions or missing evidence.1819## Examples2021- For a board-report PDF backed by source spreadsheets, render the PDF, trace headline metrics to source cells, and flag a chart label that conflicts with the underlying period. Do not rewrite the report unless correction is requested.22- For a spreadsheet deliverable, inspect formulas, units, totals, visible error states, and the rendered workbook. If recalculation or a source file is unavailable, state that limitation instead of treating displayed values as verified.23- For a Markdown guide with no supplied source material, verify structure, links, internal consistency, and usability, but label factual claims as unverified rather than searching for evidence outside the agreed scope.2425## Output2627Start with one of these verdicts:2829- **Ready**: no material issue blocks delivery.30- **Ready with minor fixes**: only low-impact corrections remain.31- **Not ready**: at least one issue could mislead the reader, break use, or violate an explicit requirement.3233Then provide a compact table with `Severity`, `Location`, `Finding`, `Evidence`, and `Suggested fix`. End with the checks performed and any checks that could not be completed.3435Do not silently edit, publish, send, delete, or overwrite files. If the user asks for corrections, preserve the original unless they explicitly authorize replacement.
sandbaseai