Stress-test checklist for gaps and edge cases
Packaged know-how that tells an agent how to do a job well.
You might say…
“The checklist looked complete until a beta tester hit a fork in step 6 that the checklist didn't mention — this finds those forks before real users do.”
What it does
Reviews a drafted checklist against likely failure points and edge cases, flagging missing steps, ambiguous instructions, and conditions that break the sequence.
Trigger: Use after drafting a checklist and before distributing it, to surface gaps and ambiguities while fixes are still cheap.
I/O: Draft checklist → annotated checklist with gap flags, ambiguity notes, and missing-step callouts
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