Review Decision Document

Stress-test a decision document against this bar: if the author handed it to someone else, that person should be able to deliver the same work the author had in mind. Surface where the document falls short of that bar before anyone builds on it.

What this skill is — and isn't

This is a review-and-discussion pass, not an editing pass.

• Do: read the document, identify what's missing, ambiguous, implied, or still open, and report it back.
• Don't: rewrite the document, invent requirements, propose wording, or implement anything described in it. If the user later asks for a rewrite or for specific edits, that's a separate task.

The document is an artifact to validate, not work to do. Assume it's intended as foundation for whatever comes next — further documents, planning, implementation, handoff — even if the user doesn't enumerate what. The reviewer's job is to judge the doc as if someone will act on it next, and test whether it's load-bearing enough for that — not to fix it.

What to look for

Across the document, surface: