Canonical: https://botbento.com/usecases/draft-executable-feature-specs-before-any-code/
Format: Markdown representation of the public HTML page.

# Draft executable feature specs before any code is generated

[Coding](https://botbento.com/usecases/coding/) · Intermediate

Turn a rough feature request into a reviewable spec file

A bot turns a rough feature request into a structured spec file. The spec covers scope, data inputs, edge cases and acceptance checks. Implementation then starts from a fixed target instead of drifting as requirements get renegotiated mid-build.

## Quick answers

**What does it do?** Turn a rough feature request into a reviewable spec file. Result: Spec file posted for review.

**What does it need?** Tools: GitHub, Docs, Notes, Chat. Intermediate: some setup. The prompt includes an approval step.

**How do I run it?** When you ask: Feature request arrives. Copy the prompt below into a bot in BotBento.

## How it works

1. When you ask: Feature request arrives
2. Then: Draft spec sections and open questions
3. Result: Spec file posted for review

## Prompt to start with

```text
Read the incoming feature request and produce a spec with sections for goal, scope, data inputs, edge cases, acceptance checks and open questions. Ask the user to resolve ambiguities before finalizing, and flag any requirement that contradicts an earlier one rather than silently picking a side. Keep the spec in a versioned file so revisions stay diffable, and treat every draft as provisional until a person signs off. Posting the spec to a shared channel, opening issues, merging or deleting anything must wait for explicit approval.
```

## Tools it uses

GitHub, Docs, Notes, Chat

## Works with

BotBento

## Tags

specification, codegen, planning, review, workflow

## Source

[Show HN: Specification First Agentic Development Plugin and Prove](https://news.ycombinator.com/item?id=50260571) — Hacker News · checked 2026-11-13

Summarized in our own words. Any results described there are the authors’ own, not measured by BotBento.

Verified 2026-11-13: passed every automated gate and a second-model review (kimi-code/k3.1-pro). Automated, not human review. [How verification works](https://botbento.com/usecases/verification/)

By BotBento Editorial · Added 2026-11-13 · Updated 2026-11-13 · [Suggest a correction](https://botbento.com/contact/)

## Related use cases

- [Plan supervised code changes in a repository](https://botbento.com/usecases/plan-supervised-code-changes-in-a-repository/) — Restate a feature request, draft a plan, and review edits before commit
- [Score feature specs before coding agents start](https://botbento.com/usecases/score-feature-specs-before-coding-agents-start/) — Catch missing scope, edge cases and tests in a written spec
- [Breaking down feature scopes into iterative code tasks](https://botbento.com/usecases/breaking-down-feature-scopes-into-iterative-code/) — Turn broad engineering requirements into small subtasks and execute code modifications incrementally
