RISE Prompt Framework
RISE = Role, Input, Steps, Execution. A structured framework for prompts that require step-by-step output. Define who the AI is, what the input material is, what steps to follow, and how the output should be formatted.
When to Use RISE
Use the RISE framework when:
- The task requires ordered, sequential output — tutorials, how-to guides, runbooks, or SOPs.
- You are producing project plans, onboarding documents, or sprint planning guides where phase order matters.
- The AI needs to work through a specific sequence of subtasks rather than produce a single block of content.
- Process documentation for teams — where each step needs to be discrete and actionable.
When Not to Use RISE
- Quick, single-output tasks — use the TAG framework instead.
- Tasks needing full situational context — use COAST when background and scenario constraints drive the output.
- Educational explanations — use the RACE framework for teaching and explanatory content.
RISE Framework Template
Example: Project Planning
Before (weak prompt):
After (structured prompt):
Example prompt:
Act as a senior agile project manager. I am launching a mobile app with a 12-week timeline. The team includes 4 engineers, 1 designer, and 1 QA engineer. Define the project phases, break each phase into weekly milestones, and identify key dependencies and risks. Format the output as a numbered phase plan with week-by-week breakdown and a risk table at the end.
Example: Onboarding Documentation
Before (weak prompt):
After (structured prompt):
Example prompt:
Act as a technical writer specializing in developer docs. Write an onboarding guide for a REST API with authentication, three main endpoints (users, events, reports), and an SDK in Python and JavaScript. Structure it as: introduction, authentication setup, first API call walkthrough, endpoint overview, SDK quickstart. Use numbered sections with code blocks. Target audience is junior developers. Keep each section under 200 words.
How to Write a RISE Prompt — Step by Step
- Define the Role. Describe the AI persona or area of expertise it should bring to the task.
- Provide the Input. Specify what material, data, or information the AI is working with.
- Specify the Steps. Describe the specific sequence of steps or phases the AI should follow.
- Define the Execution. State how the output should be formatted — structure, depth, tone, and ordering.
Frequently Asked Questions
What does RISE stand for in prompt engineering?
RISE stands for Role, Input, Steps, Execution. It is a four-part prompt framework designed for tasks that require step-by-step output — such as tutorials, project plans, SOPs, and process documentation.
When should I use RISE instead of ROLE?
Use RISE when the output itself needs to be a sequence of ordered steps or phases. Use ROLE when the task requires an expert persona and constraints but does not specifically need step-by-step output structure.
Is RISE good for writing tutorials?
Yes, RISE is well-suited for tutorials, how-to guides, and process documentation. The Steps component ensures the AI structures the output as a sequence, and the Execution component lets you control the depth and format of each step.
Try the Prompt Generator →Also see: All AI Prompt Frameworks · AI Prompt Optimizer