Derive role-type and skill requirements from workstreams
Packaged know-how that tells an agent how to do a job well.
You might say…
“Before we talk headcount, I need to know what kinds of people this engagement actually needs — not job titles, actual capability requirements.”
What it does
Reads the delivery-approach workstreams and names the functional role type plus specific skills and domain knowledge each demands, producing a structured role-requirements list.
Trigger: Use right after the delivery plan is drafted and before any headcount or scheduling discussion, to translate the approach into role requirements.
I/O: Workstream list with method and deliverable definitions → structured role requirements list (role type + skills + domain knowledge per workstream)
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