## Score feature specs before coding agents start

Catch missing scope, edge cases and tests in a written spec.

Read the spec document the user points you to. Score it against a fixed checklist: goal, scope boundaries, data shapes, error and edge cases, acceptance tests, and rollout notes. For every gap, cite the section heading and write one clarifying question. Give a score per section plus an overall pass or revise verdict, and keep drafted rewrites in a separate note rather than editing the original. Do not send, post or delete anything without the user's approval.

Source: BotBento use case https://botbento.com/usecases/score-feature-specs-before-coding-agents-start/ (CC BY 4.0).
