# Spec Review Checklist

## Intent
- [ ] The problem is understandable without the original chat or meeting.
- [ ] The desired outcome is explicit.
- [ ] Non-goals prevent obvious scope creep.

## Behavior
- [ ] Important user/system behavior is defined.
- [ ] Business rules are explicit.
- [ ] Failure and empty states are addressed where relevant.
- [ ] Important edge cases are visible.

## Boundaries
- [ ] Architecture, security, privacy, or compatibility constraints are captured.
- [ ] The spec does not prescribe implementation details without a reason.
- [ ] AI-generated assumptions have been reviewed by a human.

## Verification
- [ ] Acceptance criteria are observable and testable.
- [ ] Criteria do not contradict each other.
- [ ] A reviewer can tell whether the implementation satisfies the spec.

## Readiness
- [ ] Open questions that block implementation are resolved.
- [ ] Remaining open questions are clearly identified.
- [ ] The spec is proportional to the risk and size of the change.