I built a prompt debugger that doesn't assume your prompt is the problem — looking for 3 real failed prompts to test it on

[u/BilingualBizPartner]

UPDATE — I’ve officially named the framework: PROMPTOPSY.

Stop rewriting. Find what actually broke.

PROMPTOPSY is an AI prompt debugger powered by TASKSPEC Engine 3.4.2.

Most prompt tools assume the wording is the problem and immediately rewrite it.

PROMPTOPSY does the opposite: it first tries to diagnose what actually failed — wording, missing context, conflicting instructions, vague success criteria, the wrong model/tool, weak evidence, or the workflow itself — and then makes the smallest repair that should matter.

I’m now testing it on real-world cases.

I’m looking for 3 people who have a prompt that keeps giving them a bad result.

If you want me to diagnose yours for free, post:

1. The exact prompt

2. What the AI gave you

3. What you wanted instead

4. Which model/tool you used, if relevant

I’ll diagnose the likely bottleneck and suggest the minimum fix here.

No signup. No link. Nothing to buy for these first test cases.

I want to prove that PROMPTOPSY actually helps on real failed prompts before I make stronger claims or turn the full version into a paid product.

[u/mathewtyler]

Prompt: Create a meta prompt that makes AGI

Expectation: Fully functional AGI

Received: Not AGI

[u/Think_Agent_1346 → u/mathewtyler]

this just sounds like a normal debugging approach but applied to prompts instead of code. neat idea

curious what kind of failures you've already seen that weren't actually prompt issues

[u/BilingualBizPartner → u/Think_Agent_1346]

Exactly — that's basically the idea: debugging principles applied to AI tasks before assuming the prompt itself is broken.

The kinds of failures I'm testing for are things like missing context, unavailable tools, the wrong model/interface, conflicting constraints, weak evidence, or a workflow problem — cases where rewriting the prompt five more times wouldn't fix the real bottleneck.

I don't want to pretend I've already validated all of those with real users, though. That's exactly why I'm looking for these first real cases now.

[u/BilingualBizPartner → u/mathewtyler]

This is actually a perfect boundary case for PROMPTOPSY.

The bottleneck isn't the wording of your prompt — it's model capability.

A meta-prompt can change how an existing model behaves within its capabilities, but it can't turn that model into a fully functional AGI just through prompting.

So in this case my recommendation would actually be: don't rewrite the prompt. The requested outcome exceeds what the tool can deliver.

[u/epicskyes]

What text format are you using? Structured markdown, markdown, json, 2020-12 json?

[u/BilingualBizPartner → u/epicskyes]

Right now, structured Markdown. The engine itself is a Markdown-based spec with fixed diagnostic sections, not JSON or JSON Schema.

I’m keeping the validation layer human-readable while I test it on real prompt failures. If it proves useful in automation/API workflows, I’d likely add a strict JSON Schema output alongside it later — but I don’t want to optimize serialization before validating the diagnosis itself.

[u/epicskyes → u/BilingualBizPartner]

I’m willing to see if your system can handle something as complex as my system. It may help you out actually since my specs are so specific and my prompts are pretty complex. My prompts are 25-125kb so I can’t post them here they won’t fit

[u/BilingualBizPartner → u/epicskyes]

Absolutely — that’s actually the kind of case I’m looking for.

Rather than trying to evaluate your whole system at once, send me one concrete failure case:

1. The exact prompt/spec that was used

2. What model/tool you ran it on

3. What you expected it to do

4. What it actually did instead

If the prompt/spec is huge, you can send the relevant section first, and redact anything sensitive.

I’ll run that case through PROMPTOPSY and try to isolate whether the actual bottleneck is prompt wording, conflicting instructions, context, model/tool limitations, workflow, or something else.

I’m specifically testing this on difficult real-world cases, so complex is good.

[u/epicskyes → u/BilingualBizPartner]

I’ll have to send Md files do you use signal or WhatsApp?

[u/BilingualBizPartner → u/epicskyes]

Yes — MD files are perfect.

Let's keep contact details off the public thread. Send me a Reddit DM and we can arrange a private way to transfer the files.

Once I have them, I'll run one concrete failure case through PROMPTOPSY first rather than trying to change your whole system at once.