Stress-test the boundary against awkward edge cases
Packaged know-how that tells an agent how to do a job well.
You might say…
“Every edge case I didn't pre-answer came back as a client conversation I had to have on the fly — this skill forces me to answer them first.”
What it does
Generates adjacent problems and client situations near the scope boundary and tests whether each routes clearly as in, out, or redirected — surfacing ambiguities before they become scope creep.
Trigger: Use after drafting the scope boundary, before it goes into any client-facing material.
I/O: Draft scope boundary → list of edge cases with routing decisions and identified ambiguities to resolve
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation