ShipUntilDead.
All projectsBuilds From the Underground
Give-AI-what-it-needs zine coverInside the project

Better questions. Better builds.

Give-AI-what-it-needs

A requirement elicitation engine for image and video generation. It takes an idea apart, helps pin down what matters, and turns the answers into platform-specific prompts.

Visit project

An example from my own workflow

Same idea. A clearer direction.

Before / After

The first image came from my initial prompt. After using the tool to refine the prompt, I generated the anime-style result. The setting, lighting, character styling, and mood now follow a much more specific direction.

Initial result: a child in a green sweater holding a large gold coin on a sunlit forest path, rendered in a photographic style.
Before the tool

The initial result

A daylight forest, photographic styling, and a large coin as the focal point.

Refined result: an anime-style girl holding a glowing coin on a misty forest path beneath a crescent moon, with mountains in the distance.
After the tool

The refined result

Anime styling, a moonlit forest, distant mountains, and a small glowing coin.

The tool helps clarify the prompt; the images are generated separately. Select either image to see it at full size.

The idea

Ask first. Generate with intent.

A generation can look impressive and still miss the brief. The wrong format, an unspecified camera movement, or a forgotten detail means another paid attempt. This project puts a short clarification loop before generation, so the tool receives a more complete description of what you actually want.

What it does

The moving parts.

Questions grounded in your idea

The AI identifies the subjects and setting in your description, then asks focused questions about each. An idea about a barista pouring a latte can become separate questions about the barista, drink, café, and scene. Multi-select answers allow compatible details to coexist.

One prompt for each platform

Answers become a coherent description, then deterministic compilers add the platform-specific structure. Image targets include Midjourney, DALL·E, and Higgsfield; video targets include Higgsfield, Veo 3, and Runway.

Visible gaps before you spend

A completeness meter counts unanswered required fields. You can fill them in or explicitly choose to compile anyway. Technical choices such as aspect ratio and duration remain direct controls.

A way to test the idea itself

After copying a prompt, you can record whether the result worked first time, needed more attempts, or was abandoned. Local statistics compare complete and incomplete specs. Reduced regeneration is a hypothesis being measured, not a promised result.

How it works

From idea to action.

  1. Describe the idea

    Choose image or video and enter what you want to make. Set the practical constraints and any non-negotiable details.

  2. Fill in what matters

    Use the fixed form, or connect your provider and let the question engine break down the subjects. Answer the questions that help define the result.

  3. Compile and take it with you

    Review missing requirements, then copy a prompt into your generation platform. Return afterward to record the outcome.

In practice

Before you dive in.

The app prepares prompts; it does not generate the final images or videos. The current implemented domains are image and video. Coding and broader requirement graphs remain future work.

The Next.js app lives in spec-compiler-mvp. Install its dependencies and run npm run dev to use it locally. MCP integrations expose elicit_spec and compile_spec for compatible assistants.

Specs and outcomes persist in the browser. Provider keys are stored locally; Anthropic requests are browser-direct, while other supported providers use a same-origin pass-through proxy that does not store the key. AI questions require a key; the fixed form remains available without one.

Go deeper

Straight from the source.

Explore the original documentation for setup instructions and the latest changes.