GPT

You Are Deliberately Leaving Alone

you are deliberately leaving alone and why) 6. Regression Probe - probe specification: input trajectory or page, expected post-fix behaviour, expected pre-fix behaviour - acceptance criterion (binary, mechanical) -

Prompt text

Original English text. Replace placeholders with your own details.

you are deliberately leaving alone
 and why)

6. Regression Probe
 - probe specification: input trajectory or page, expected post-fix
 behaviour, expected pre-fix behaviour
 - acceptance criterion (binary, mechanical)
 - false-positive guard: a near-miss case where the probe must NOT
 trigger a regression flag

7. Aggregate View (only if multiple trajectories)
 - distribution of failure layers across the batch
 - recommended fix order with expected coverage of total failures
 - explicit warning if planner-rewrite is being proposed for a batch
 dominated by grounding failures

8. Main Risk
 - the single biggest way this diagnosis could be wrong (e.g., the
 trace is missing the accessibility tree so grounding cannot be
 verified, the goal was ambiguous and the plan was actually
 defensible, the trajectory hit a flaky third-party element) and
 the one observation that would resolve it

------------------------------------------------------------------
QUALITY BAR:

- No layer blamed without quoted trajectory evidence. "The plan looks
 bad" is not a diagnosis.
- No grounding blame without showing the intended target AND the actual
 target AND the divergence. Both must be in the trace.
- No replanning blame without identifying the specific divergence signal
 the agent should have observed and the action it took instead.
- No planner blame on a trajectory dominated by grounding failures. The
 literature says grounding is the bottleneck; rewriting the planner
 there moves no metric.
- No fix recommendation without a regression probe that fails pre-fix
 and passes post-fix.
- No simultaneous fixes across all three layers. Pick one, ship it,
 measure, then iterate.
- No diagnosis that ignores upstream causes. Auth walls and prompt
 injection from page content masquerade as agent failures and must be
 ruled out explicitly, not implicitly.
- No batch recommendation that mismatches the failure distribution. If
 62% of failures are grounding, the headline fix is a grounding fix,
 not a planner rewrite, regardless of which layer is more interesting
 to redesign.

Source & attribution

Awesome Prompts · Awesome Prompts

Source-listed license: GPL-3.0. Prompt text is preserved; titles and previews may be shortened for display. Source examples are not NexGateHub test results.

View original source ↗ · Source credits & licenses

Explore more prompts →