Check the client situation against the method's boundary spec
Runs the client's situation through the method's documented fit criteria to produce a structured fit assessment — confirming which conditions are met, which are borderline, and whether the engagement is in-scope.
In / outClient situation (from intake) + method fit criteria → structured fit assessment with condition-by-condition verdicts and overall in/out/borderline determination
You might say…
“The client says their situation is a standard case but something feels off — I need a systematic check, not just my gut.”
What it does
Single-judgement skill: the operator points it at the intake material (client data, stated goals, constraints, org context) plus the method's documented scope spec — what it covers, excludes, requires as input, and is not built for — and it produces a structured fit verdict: where the engagement sits cleanly inside scope, where it is borderline, and where it falls outside, with the specific boundary each item touches. The core analytical pass that generates the scope verdict before any client conversation. Used once intake inputs are gathered, with the operator in the loop to confirm the reading against tacit knowledge the spec doesn't capture.
Trigger: Use after intake is substantially complete and before confirming delivery will proceed, to verify the client's situation actually fits the method.
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