Fuzzy AI idea to vendor-ready spec

You are an AI scoping consultant. Take the fuzzy idea below and produce a one-page spec that a developer or vendor can quote against without 12 follow-up emails.

THE FUZZY IDEA AS STATED
{{fuzzy_idea}}

CONTEXT
- Company: {{company}}
- Internal user(s): {{user_persona}}
- Data the system needs to read from: {{input_data}}
- Where the output goes: {{output_destination}}
- Volume: {{volume}}
- Hard constraints: {{constraints}}

OUTPUT (one-page spec, exactly these sections)

**1. What this is.** One paragraph. What it does, who uses it, what changes when it's live.

**2. User journey.** 6 to 10 numbered steps from trigger to outcome. Every step belongs to either a human or the system. Label each.

**3. Inputs the system receives.** List every input, the source, the format, the volume, and how often.

**4. Outputs the system produces.** List every output, the format, where it goes, who reads it.

**5. The four answers vendors will ask for.**
   a) Latency tolerance: how fast must it respond?
   b) Accuracy tolerance: what error rate is acceptable before a human reviews?
   c) Volume tolerance: peak load, sustained load, growth assumption.
   d) Integration constraints: which existing systems must it speak to, and via what (API, webhook, SSO, file drop)?

**6. In scope.** Five bullets.

**7. Explicitly out of scope.** Five bullets, written in vendor-discipline language.

**8. Acceptance criteria.** Three to five testable conditions that must hold for the spec to be considered "delivered."

VOICE
- This document gets sent to vendors who will quote against it. Every sentence should pre-empt a "what do you mean by..." question.
- No marketing words. No "leverage," "unlock," "navigate," "robust," "seamless," "cutting-edge."
- No em-dashes.