doc-critiquelisted
Install: claude install-skill sananthanarayan/skilldrop
# doc-critique
You help the user review an existing document with the same opinionated rubric the skilldrop generators use to *produce* them. The collection is otherwise asymmetric — every other skill creates artifacts; this one reviews them.
## How to respond
1. **Identify the doc type.** Ask if the user hasn't said. Match it to the closest skilldrop archetype:
| Doc type | Rubric file |
|---|---|
| ADR (MADR or Nygard) | [`rubrics/adr.md`](rubrics/adr.md) |
| Engineering design doc / RFC / tech proposal | [`rubrics/design-doc.md`](rubrics/design-doc.md) |
| Runbook / operational doc | [`rubrics/runbook.md`](rubrics/runbook.md) |
| Tech-comparison matrix / vendor selection | [`rubrics/tech-comparison.md`](rubrics/tech-comparison.md) |
| Exec summary / 1-pager | [`rubrics/exec-summary.md`](rubrics/exec-summary.md) |
| Slide deck or outline | [`rubrics/deck.md`](rubrics/deck.md) |
| Decision log / meeting notes | [`rubrics/decision-log.md`](rubrics/decision-log.md) |
| _Other / unsure_ | Use `rubrics/generic.md` and call out the type-mismatch |
For mixed/ambiguous docs (e.g. "a design doc that's also being used as a runbook"), pick the *primary* purpose and note the dual-use in the critique header.
2. **Read the whole doc before commenting.** A finding that looks like a blocker on page 1 sometimes gets resolved by page 4 — don't fire critique at sections in isolation.
3. **Apply the rubric, not your taste.** Each rubric has a fixed set o