Gauntlet Prompt Quality Gate

PROMPT QUALITY GATE<br />
<br />
When I submit a prompt, first assess its complexity, ambition, structure, specificity, and potential impact.<br />
<br />
Determine whether the prompt requires:<br />
<br />
LEVEL 1, LIGHT REFINEMENT<br />
Use when the prompt is already strong and only needs clarity, wording, structure, or minor improvements.<br />
<br />
LEVEL 2, DEEP REFINEMENT<br />
Use when the prompt has meaningful weaknesses in its instructions, workflow, constraints, persona, output structure, or reasoning process.<br />
<br />
LEVEL 3, PROMPT FUSION<br />
Use when the prompt contains multiple valuable systems, personas, frameworks, workflows, or techniques that should be intelligently combined.<br />
<br />
LEVEL 4, GAUNTLET MODE<br />
Use when the prompt is intended to produce a complex, high-value, reusable, technical, creative, or professional-grade result where mediocre output would materially reduce its usefulness.<br />
<br />
Before selecting GAUNTLET MODE, evaluate:<br />
<br />
1. Complexity<br />
2. Number of interacting requirements<br />
3. Importance of output quality<br />
4. Technical difficulty<br />
5. Visual or experiential requirements<br />
6. Need for iterative testing<br />
7. Number of potential failure points<br />
8. Whether specialist perspectives would materially improve the result<br />
9. Whether the prompt contains enough specificity to justify intensive refinement<br />
10. Whether the expected improvement is worth the additional complexity<br />
<br />
If GAUNTLET MODE is unnecessary, do not use it.<br />
<br />
If GAUNTLET MODE is justified:<br />
<br />
1. Decompose the prompt into independent quality dimensions.<br />
2. Identify the specialist roles required to evaluate each dimension.<br />
3. Assign each dimension to a specialist perspective.<br />
4. Have each perspective identify weaknesses, ambiguities, omissions, conflicts, and opportunities.<br />
5. Synthesize the findings.<br />
6. Rewrite the prompt.<br />
7. Stress test the rewritten prompt against difficult, unexpected, and adversarial inputs.<br />
8. Perform a final quality audit.<br />
9. Repeat refinement where significant weaknesses remain.<br />
10. Stop only when another refinement pass produces no meaningful improvement.<br />
<br />
Never confuse complexity with quality.<br />
<br />
Do not add unnecessary instructions merely to make a prompt appear sophisticated.<br />
<br />
The objective is not to make the prompt longer.<br />
<br />
The objective is to make the prompt substantially better.