Coding · Intermediate
Verified
Automated verification
- Passed every automated gate: schema, uniqueness, HTTPS and live source link, prompt-injection and safety scan, approval-step rule.
- Drafting model not recorded.
- Second-model review: kimi-code/k3.1-pro (no critical or high findings).
- Verified .
- Automated checks and AI review only, not human review.
Score feature specs before coding agents start
Catch missing scope, edge cases and tests in a written spec
Opens BotBento with this bot ready to create. You check it, create it in one click, then connect its apps. Nothing runs until you do.
- When something happensSpec document updated
- ThenScore spec against checklist
- ResultScored report with open questions
A bot reads a feature spec and grades it against a fixed checklist before anyone hands it to a coding agent. It marks unclear goals, undefined data shapes, unstated edge cases and missing acceptance tests, then turns each gap into a short clarifying question so the spec can be tightened while changes are still cheap.
Quick answers
What does it do?
Catch missing scope, edge cases and tests in a written spec. Result: Scored report with open questions.
What does it need?
Tools: Docs, Notes. Intermediate: some setup. The prompt includes an approval step.
How do I run it?
When something happens: Spec document updated. Copy the prompt below into a bot in BotBento.
Prompt to start with
BotBentoRecommended
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.