Role-Based Prompt Template
Use this template when you are creating content that needs to sound like it comes from a specific perspective, role, or expertise level — or when you want AI to approach the task the way a particular type of expert would approach it.
Template
[ROLE FRAMING — optional but useful for specialized tasks]
Approach this as a [role or expert type — e.g., experienced product manager / B2B SaaS marketer / senior technical writer / operations lead with a background in process design].
TASK
[What needs to be created or accomplished?]
CONTEXT
[Background information about the situation, company, project, or decision]
AUDIENCE
[Who is this for? Role, experience level, what they care about]
GOAL
[What should this output accomplish? What action or understanding should the reader come away with?]
PERSPECTIVE TO BRING
[What lens or expertise should shape the output?
Examples: prioritize risk clarity / think like a procrastinating user who needs motivation / frame everything as operational impact / write from a technical-accuracy-first standpoint]
TONE
[How should it feel?]
FORMAT AND LENGTH
[Structure, organization, approximate length]
AVOID
[What to exclude — topics, language, framing styles]
When to use role framing
Role framing is useful when:
- The task requires domain expertise (e.g., write like someone who understands B2B sales dynamics)
- You want the output to reflect a specific professional perspective (e.g., approach this as a first-principles thinker)
- You want to simulate how a specific type of stakeholder would frame something (e.g., write this the way a cautious legal team would want it worded)
Role framing is not needed for most general tasks. Use it when the specialized perspective genuinely changes what the output should say.
Example: Product manager writing for engineering
Approach this as an experienced product manager who works closely with engineering teams and is skilled at translating business requirements into technically useful context.
TASK
Write a feature spec overview for a new bulk export functionality in our reporting module.
CONTEXT
The feature allows users to export multiple reports at once as a single zip file. It was requested by enterprise customers who currently have to export reports one at a time. This is a Q3 priority.
AUDIENCE
The engineering team who will scope and implement this feature. They need enough context to understand the problem and constraints, but do not need business justification — they already know the feature is approved.
GOAL
Give engineers a clear, unambiguous description of what the feature needs to do, what edge cases matter, and what success looks like from a user's perspective.
TONE
Precise and practical. No fluff.
FORMAT
Short overview paragraph, then a bulleted list of functional requirements, then a short list of edge cases and open questions.
AVOID
Marketing language. Vague statements like "seamless experience." Anything that would create ambiguity for implementation.
Tips for using this template
- The role framing should be grounded. "Approach this as a brilliant visionary" is too vague. "Approach this as an experienced customer success manager who has worked with enterprise clients" gives AI something useful to work from.
- The perspective section is distinct from tone. Perspective is about what the expert knows and cares about. Tone is about how the writing feels.
- After running this template, check whether the role framing actually changed the output. If not, the role was too generic or not needed for this task.