---
name: score-feature-specs-before-coding-agents-start
description: "Catch missing scope, edge cases and tests in a written spec. A bot reads a feature spec and grades it against a fixed checklist before anyone hands it to a coding agent."
license: CC-BY-4.0
compatibility: "Needs access to: Docs, Notes."
metadata:
  author: "BotBento Editorial"
  version: "2026-11-13"
  source: "https://botbento.com/usecases/score-feature-specs-before-coding-agents-start/"
  kind: workflow
  hermes:
    tags: ["specs", "checklist", "quality", "review"]
    category: coding
---
# Score feature specs before coding agents start

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

## When to use

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.

## Steps

1. When something happens: Spec document updated
2. Score spec against checklist
3. Scored report with open questions

## Instructions

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

Summarized in our own words from [Epic framework for spec-driven development](https://news.ycombinator.com/item?id=50392336) (Hacker News, checked 2026-11-13). Any results described there are the authors’ own.

From the BotBento use-case directory: https://botbento.com/usecases/score-feature-specs-before-coding-agents-start/. Licence: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
