What is the CRISPE Framework?
CRISPE is a structured prompt engineering framework developed to produce comprehensive, high-quality outputs for complex content, research, and communication tasks. It consists of six components that ensure the model has all necessary context before beginning its work:
| Letter | Component | What it provides |
|---|---|---|
| C | Capacity and Role | The model's expertise, identity, and capabilities for this task |
| R | Role (in context) | Reinforces the specific perspective or authority the model brings |
| I | Insight | Background context, data, or knowledge the model must consider |
| S | Statement | The specific task, question, or request to be completed |
| P | Personality | The tone, voice, style, or communication register to use |
| E | Experiment | A request for multiple variations, approaches, or options |
What distinguishes CRISPE from other frameworks is the explicit Insight component (background context that the model must internalize) and the Personality component (tone and voice specification). These two additions make CRISPE particularly powerful for content creation, communications, and research tasks where context and voice are as important as the instructions themselves.
When to Use the CRISPE Framework
Content Creation
Blog posts, thought leadership articles, social media content — where voice, audience, and insight context all matter.
Marketing Communications
Email campaigns, product copy, press releases — where brand personality and market context must be encoded upfront.
Research Assistance
Literature reviews, market research, expert analysis — where the model needs substantial background insight to reason correctly.
Executive Communications
Investor updates, board reports, executive summaries — high-stakes documents where tone, authority, and precision are non-negotiable.
Creative Projects
Scripts, narratives, creative briefs — where multiple variations via the Experiment component help explore creative directions.
Educational Content
Course materials, explainer content, learning resources — where the right pedagogical voice and learner context are essential.
How to Build a CRISPE Prompt
- 1
C/R — Define Capacity and Role
Establish the model's expertise and authority for this task. Include specialization, experience level, and the type of organization they work for. This is the same as a detailed Role Prompt — it primes the model's knowledge and communication patterns.
- 2
I — Provide Insight (background context)
Share the context the model needs to do the task well: the company's positioning, the target audience's characteristics, key market facts, a style guide, or any data the model would otherwise have to guess. This is the component most commonly missing from naive prompts.
- 3
S — State the task precisely
Make the core request. Use a clear action verb and specify the deliverable, scope, and any structural requirements (sections, length, format).
- 4
P — Define Personality
Specify tone, voice, and style explicitly. "Authoritative but approachable", "conversational and energetic", "formal and precise" — these adjectives meaningfully shift the output. If you have a style guide, summarize its key principles here.
- 5
E — Request Experiments (optional)
Ask for 2–3 variations of the output if you want options to choose from. "Generate 3 versions: one that leads with data, one that leads with a story, and one that leads with a provocative question." The Experiment component turns one request into a creative exploration.
Prompt Examples
Capacity and Role: You are a veteran B2B SaaS marketing strategist with 15 years of experience building category-defining narratives for developer tools companies. You have written for publications like HackerNews, The Pragmatic Engineer, and company engineering blogs. Insight: Prompt Edit is a free macOS app that lets developers save and reuse AI prompt templates with dynamic variables. It stores everything locally (no cloud, no account). The target audience is developers and technical PMs who use AI daily and are frustrated by prompt repetition and lack of organization. The biggest competitor behavior is keeping prompts in Notion or text files. Statement: Write an 800-word thought leadership article titled "Why Your AI Prompts Deserve Version Control" for the Prompt Edit blog. Personality: Opinionated, direct, and slightly irreverent. Use developer analogies. Avoid marketing buzzwords and vague superlatives. Write as if explaining to a smart peer at a conference, not selling to them. Experiment: Provide 2 versions of the opening paragraph: Version A: starts with a frustrating scenario the reader recognizes Version B: starts with a bold, counterintuitive claim
Capacity and Role: You are an experienced startup communications advisor who has helped 50+ founders write investor updates. You write with clarity, honesty, and appropriate confidence. Insight: Monthly metrics: MRR $42k (+18% MoM), churn 3.2% (down from 4.1%), CAC $280, LTV $1,800. Hired 2 engineers. Launched enterprise tier. One major deal ($120k ARR) in final negotiation. Runway: 14 months. Statement: Write a monthly investor update email covering: metrics highlights, key wins, main challenge, and what help we need. Personality: Confident but not overconfident. Transparent about challenges without being alarming. Professional and concise. Founders who write updates their investors actually read. Experiment: Provide the challenge section in 2 tones: Version A: matter-of-fact and analytical Version B: solution-oriented and proactive
Pros and Cons
| 🟢 Pros | 🔴 Cons |
|---|---|
| Explicit Insight component prevents context-free outputs | 6 components make it heavier than simpler frameworks |
| Personality component ensures brand voice consistency | Insight section can become very long for context-heavy tasks |
| Experiment component generates creative options efficiently | Less suited for pure task execution vs RISEN's Step-focused approach |
| Excellent for content, communications, and research tasks | Experiment adds token cost if you don't need multiple variations |
Frequently Asked Questions
What is the CRISPE framework?
CRISPE is a structured prompt engineering framework with six components: Capacity and Role (the model's expertise and identity), Insight (background context the model needs), Statement (the specific task or question), Personality (the tone, style, or voice to use), and Experiment (a request for multiple variations or options). Together, these produce highly contextual, well-calibrated outputs for complex content and research tasks.
What does CRISPE stand for?
CRISPE stands for: C — Capacity and Role, R — Role (combined with C), I — Insight, S — Statement, P — Personality, E — Experiment. The C and R are sometimes treated as one combined component defining who the model is and what expertise it has.
How does CRISPE differ from RISEN?
Both are structured prompt frameworks, but with different emphases. CRISPE includes Insight (background context) and Personality (tone/voice) as explicit first-class components, making it better suited for content creation, communications, and research assistance. RISEN is more task-execution-focused with Steps and explicit End Goal. CRISPE's Experiment component also uniquely asks for multiple output variations, which RISEN lacks.
When should I use CRISPE?
CRISPE excels for content creation (articles, social posts, scripts), research assistance, high-stakes communications (executive reports, investor updates), creative writing, and any task where tone, voice, and background context are as important as the task instructions. If you find yourself frequently specifying 'write this in the voice of...' or 'keep in mind that...', CRISPE formalizes those elements.
What is the Experiment component in CRISPE?
The Experiment component asks the model to produce multiple versions, variations, or approaches to your request. Instead of one answer, you get 2–3 options with different angles, tones, or approaches — allowing you to choose, combine, or use them as inspiration. This is particularly valuable for creative and communication tasks where there is no single 'correct' output.
Can I skip some CRISPE components?
Yes — treat CRISPE as a checklist of what to consider, not a rigid form to complete. For many tasks, Personality can be included in the Role definition, and Experiment is optional if you only need one version. The components that add the most value and are most often missing in naive prompts are Insight (context) and Personality (voice), so prioritize those.
Is CRISPE good for technical prompts?
CRISPE works for technical tasks but RISEN may be a better fit due to its explicit Steps component. For technical content creation (developer documentation, technical blog posts, architecture explainers), CRISPE's Personality and Insight components add meaningful value. For pure code generation or analysis tasks, RISEN or a simple Role + Instruction prompt is often more efficient.