Short version: this prompt interviews you first, then hands back one clean, reusable prompt built to your exact specs.
u/Chance-Pen-5684 shared it on r/PromptEngineering, and it fixes a problem most of us hit constantly: staring at a blank chat window trying to describe what we actually want. Instead of guessing at phrasing, you fill in a short form. The model does the writing for you. If you’ve ever typed three different versions of the same request because none of them sounded quite right, this is built for that exact moment.
How It Works 🧩
The prompt sets up ten fields: GOAL, INPUT, OUTPUT, ROLE, MUST INCLUDE, MUST AVOID, FORMAT, QUANTITY, STYLE, and CREATIVITY. Leave anything unclear as “AUTO” and the model picks a sensible default. Fill in what matters, skip what doesn’t. Most people end up filling six or seven fields and leaving the rest on AUTO, which is exactly how it’s meant to work.
Under the hood, it’s doing three things well.
- Turning vague answers into instructions. You don’t need perfect wording, the model converts your rough notes into clear, operational language. Type “make it sound less corporate” and it turns that into an actual tone constraint the model can follow, instead of a vibe it has to guess at.
- Building in priority order. MUST AVOID beats MUST INCLUDE, which beats FORMAT and QUANTITY, which beats GOAL. That order keeps the final prompt from contradicting itself. Say you tell it MUST AVOID bullet points but also list “structured format” under FORMAT, the avoid rule wins, and the output prompt reflects that instead of leaving the conflict for you to catch later.
- Locking the output. The instructions tell the model to output exactly one prompt, no explanation, no alternatives, no commentary. That’s what makes it copy-paste ready!
That output discipline is the part worth stealing for your own meta-prompts. A lot of prompt-generators ramble on with “here’s your prompt, and here’s why I chose this approach.” This one refuses to do that on purpose, and the result reads like something you’d actually want to reuse. No cleanup pass, no trimming a paragraph of preamble before you can paste it somewhere useful.
Use Cases
- Repetitive prompt writing. If you build the same style of prompt weekly (reports, ad copy, code reviews), this turns a ten-minute writing session into a two-minute form fill. Over a month, that’s real time back.
- Prompt libraries for a team. Feed it your team’s constraints once, and everyone gets prompts that follow the same structure. New hires stop reinventing phrasing that already exists somewhere in a Slack thread.
- Teaching prompt engineering. The field list doubles as a checklist for anyone learning what a well-built prompt actually needs. Hand someone this template before they write their first prompt and they’ll skip half the mistakes everyone else makes on attempt one.
- Client or stakeholder handoffs. If you’re writing prompts other people will run without you in the room, this format forces you to spell out constraints you’d normally carry around in your head.
One commenter, u/Due-Working4505, joked that this is “a form that makes you fill out another form before you can fill out the first form. we’ve gone full recursion now.” Fair point, but the recursion pays off. You fill out one structured form instead of rewriting the same paragraph five different ways trying to nail the phrasing.
Prompt of the Day
PURPOSE
Turn my idea into exactly one polished, reusable prompt that I can copy into an AI model.CUSTOMIZE
GOAL: {{What should the AI accomplish?}}
INPUT: {{What will I give the AI?}}
OUTPUT: {{What should it produce?}}
ROLE: {{Expert/persona needed | AUTO}}
MUST INCLUDE: {{Required elements}}
MUST AVOID: {{Forbidden elements/behaviors}}
FORMAT: {{List, prose, code, image prompt, etc. | AUTO}}
QUANTITY: {{1, N, AUTO}}
STYLE: {{Tone/style | AUTO}}
CREATIVITY: {{Low, medium, high | AUTO}}
EXTRA RULES: {{Anything else | NONE}}OPERATIONS
Create exactly one executable prompt from my configuration.
Convert vague requirements into clear, operational instructions without changing my intent.
Turn reusable/changeable information into {{PLACEHOLDERS}}.
Where I specify AUTO, choose the most appropriate setting.
Do not invent requirements where information is unnecessary.
Prioritize instructions in this order:
1. MUST AVOID
2. MUST INCLUDE
3. FORMAT and QUANTITY
4. GOAL
5. Other preferencesQUALITY CONTROL
The resulting prompt must:
– Have a clear purpose.
– Define required inputs and outputs.
– Make mandatory and forbidden behavior explicit.
– Remove unnecessary ambiguity.
– Be reusable by changing placeholders.
– Include enough constraints for reliable execution without overengineering.
– Handle missing information without guessing.
– Be immediately copy-pasteable.OUTPUT
Output exactly one completed prompt.
Do not execute it.
Do not explain it.
Do not provide alternatives or examples.
Do not add commentary before or after it.
Save this one. Drop it into your model of choice, fill in the fields, and you’ll have a working prompt before your coffee gets cold. Bookmark it too, because the second and third time you use it, filling in the fields takes under a minute.
Check out the full thread for more reactions, including a few readers debating whether a prompt-for-a-prompt counts as progress or just extra homework.
Do you need a prompt to make a prompt?
by u/Chance-Pen-5684 in PromptEngineering