Requirements quality checklist

--strict validation proves a spec is well-FORMED; it doesn't prove it's well-SPECIFIED. This skill generates a tailored checklist and grades the change against it, so gaps in clarity or coverage surface before code — not in review.

When to use

• At the sdd-feature-flow human approval gate, to decide whether to approve the spec.
• Before /opsx:apply or launching implementation on any non-trivial change.

Procedure