Write the definition-of-done for each deliverable
Packaged know-how that tells an agent how to do a job well.
You might say…
“We've argued about whether a deliverable is 'done' twice on the last project — I want every output to have a line everyone can read.”
What it does
For each named deliverable, drafts a one-line definition of done — scope, format, and intended use — so every output has an unambiguous boundary before sequencing begins.
Trigger: Use immediately after the workstream list is named, to make each deliverable concrete and unambiguous before timeline or resourcing discussions.
I/O: Named deliverable list → per-deliverable definition of done (scope + format + intended use)
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