Use a template when
A template is usually enough when:
- one prompt does the whole job
- you only need input substitution
- there is one main output
- intermediate reasoning does not need inspection
- run history matters, but step-by-step history does not
Examples:
- one-off summary generation
- single-pass PR review
- reusable email draft prompt
Use a workflow when
A workflow is the better fit when:
- the task naturally breaks into stages
- later steps depend on earlier outputs
- you want review and export as separate steps
- users need to inspect or rerun one step without rerunning everything
- you want model policy to vary by step
Examples:
- feature brief to engineering plan
- transcript to show notes to title ideas
- interview notes to pain points to product brief
Simple rule
Ask one question:
Would you ever want to inspect or rerun the middle of this process?
If the answer is yes, start with a workflow.
Migration path
A practical pattern is:
- start with a template
- observe where manual follow-up prompts happen
- convert those repeated follow-up prompts into workflow steps
This keeps the system small until a workflow is truly justified.