
Calibrate support responses using fictional cases
Compare independent first replies against a shared rubric for acknowledgment, useful questions, safe next steps, and promise limits.

Compare independent first replies against a shared rubric for acknowledgment, useful questions, safe next steps, and promise limits.

Turn an ambiguous requirement into ordinary, boundary, and counterexamples with explicit conditions and expected results.

Label prerequisite inputs, expose circular waiting, and separate necessary dependencies from a preferred order of work.

Explain an effort range through scope, dependencies, and unknowns before turning it into a scheduling commitment.

Trace each claim to its origin, keep contradictory observations visible, and identify what the available evidence cannot establish.

Trace a small diff through normal, boundary, and failure cases, then record what the code and tests do not yet explain.

Test a draft through independent paraphrase, record the exact misunderstandings, and verify revisions with a fresh reader.

Keep the map identity, recovery file, responsibilities, and acceptance checks together so a handoff does not become a filename guessing game.

Make an outdoor break area feel distinct while keeping its paths, seats, and return route practical.

Define task coverage, evidence states, and issue severity before asking two people to judge whether a map is ready.

Try a bounded working practice, compare concrete observations, and return to the previous routine when the trial does not help.

Separate visual occlusion from blocked movement before adjusting an object or its surrounding layers.