Prompt vs Workflow vs Runbook
Three related ideas, with different jobs to do.
Prompt: the input
A prompt is the instruction or context sent to a model. It may be a one-sentence question or a detailed execution specification. The runbooks produced here are prompts in their delivery format.
Workflow: the sequence
A workflow describes steps and dependencies: inspect, implement, validate, then request approval to publish. It can be performed manually or orchestrated by software. A sequence alone may leave permissions and failure behavior undefined.
Runbook: the operating instructions
A runbook combines the outcome and workflow with boundaries, permissions, stopping conditions, and recovery behavior. For example, “Implement and validate the feature; preserve existing routes; return before deployment; keep completed changes if access is blocked.”
Choose the necessary structure
Use a short prompt for a simple question. Use a workflow when repeatable sequencing matters. Use a runbook when delegating work where ambiguity, scope drift, or failed steps would be costly.