Derive the required-document checklist from the methodology
Packaged know-how that tells an agent how to do a job well.
You might say…
“I ask for documents using the same generic list every time and clients send me things I don't need while missing the two files that actually matter.”
What it does
Derives the specific document and data checklist for this engagement from the method's standard input requirements, mapped against the client's known situation, naming exactly what is needed and why.
Trigger: Use before requesting documents from the client, when you need a precise, client-legible list rather than the full method input catalogue.
I/O: Method's standard input requirements + client context (sector, scope, known data landscape) → specific named document and data checklist for this engagement
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