RASCEF Framework: Role, Action, Steps, Context, Examples, Format

What Is the RASCEF Framework?

RASCEF stands for Role, Action, Steps, Context, Examples, Format. It is a six-component prompt framework that gives the AI a complete roadmap for a task: who to be, what to do, how to proceed, what situation applies, what good output looks like, and how to structure the result. It builds on fundamentals outlined in OpenAI's prompt engineering documentation.

Introduction

The R.A.S.C.E.F. Framework expands on simpler prompt frameworks by adding two critical components that most others miss: Steps (a structured sequence for the AI to follow) and Examples (concrete references that calibrate quality expectations). This makes RASCEF particularly powerful for complex tasks where you need the AI to follow a specific process and produce output that matches a particular standard.

While frameworks like RACE provide four components and APE provides three, RASCEF's six components leave virtually no room for ambiguity. The result is consistently higher-quality outputs, especially for:

• Technical documentation requiring step-by-step precision
• Instructional design where process matters as much as content
• Complex analytical reports needing structured methodology
• Creative campaigns that must follow a specific strategic approach
• Professional deliverables where format and presentation are critical

Origin & Background

The RASCEF framework emerged from the prompt engineering community's recognition that even well-structured four-component frameworks sometimes produce outputs that miss the mark on process and format. Two common problems inspired its creation:

• Role and Action define WHAT needs to happen
• Steps define HOW it should happen
• Context defines WHERE and WHY
• Examples calibrate the quality standard
• Format ensures the output is immediately usable

How R.A.S.C.E.F. Compares to Other Frameworks

• The task requires a specific methodology or sequence of steps
• Output quality must match a known standard or reference
• The deliverable needs precise formatting (reports, proposals, documentation)
• Complex tasks that benefit from breaking down the approach into stages
• You want maximum control over both process and output

• Quick, simple requests (use APE, 3 components)
• When the AI's default methodology is fine (use RACE, 4 components)
• Creative tasks where rigid structure may limit output (use ROSES)

R.A.S.C.E.F. Framework Structure

1. Role

Assigning a specific professional identity activates the relevant domain knowledge, vocabulary, and reasoning patterns. Be specific: include years of experience, specialization, and industry context.

• Senior data scientist with 12 years of experience in healthcare predictive modeling
• Technical writer specializing in API documentation for developer audiences
• Brand strategist with expertise in challenger brand positioning for B2B SaaS

• Expert (too vague)
• Writer (no specialization)
• Analyst (undefined domain)

2. Action

State the primary goal using clear, directive verbs. The action should be specific enough that success is measurable but broad enough to allow the Steps to define the approach.

• Create a competitive positioning analysis comparing our product against three named competitors
• Develop a 90-day onboarding curriculum for new sales engineers
• Write a technical RFC proposing a migration from monolith to microservices architecture

• Help with marketing (undefined scope)
• Write something about our product (no specific deliverable)
• Analyze things (no target or purpose)

3. Steps

This is what sets RASCEF apart. Instead of letting the AI choose its own methodology, you define the exact process. Number your steps for clarity, and ensure each step builds on the previous one.

• Identify and profile three primary competitor products
• Map feature comparisons across five key categories
• Analyze pricing strategies and positioning
• Identify gaps and opportunities in the competitive landscape
• Synthesize findings into strategic recommendations

• Use numbered lists for sequential processes
• Keep each step focused on one clear action
• Ensure steps flow logically from research to analysis to synthesis
• Include any specific methodologies or frameworks to apply at each step

4. Context

Supply the information the AI needs to tailor its response to your specific situation. Include constraints, audience characteristics, technical requirements, and any relevant history.

• Target audience demographics and expertise level
• Business constraints (budget, timeline, team size)
• Technical environment or platform specifications
• Industry-specific regulations or requirements
• Previous attempts or existing work to build upon

• Irrelevant background that doesn't change the output
• Excessive detail that buries the important constraints
• Assumptions the AI can't verify

5. Examples

Examples are the most underused component in prompt engineering. Providing a reference point, even a brief one, dramatically improves output consistency. You can reference well-known examples, describe a style, or provide a sample snippet.

• Reference examples: "Write in the style of Stripe's API documentation"
• Quality benchmarks: "Match the analytical depth of a Gartner research note"
• Structural references: "Follow the format of a Harvard Business Review case study"
• Tone examples: "Use a conversational yet authoritative tone, similar to Paul Graham's essays"
• Direct samples: Provide a paragraph or section that demonstrates the desired quality

6. Format

Tell the AI exactly how to present the final output. This includes document structure, formatting elements, length requirements, and any specific presentation needs.

• Document structure (sections, headers, sub-headers)
• Formatting elements (bullet points, tables, numbered lists, bold text)
• Length requirements (word count, page count, number of items)
• Visual elements (tables, comparison matrices, flowcharts described in text)
• Delivery format (executive summary, detailed report, presentation outline)

Example Prompts Using R.A.S.C.E.F.

Example 1: Technical Documentation

Role: Act as a senior technical writer with expertise in developer-facing API documentation and a background in software engineering.

Action: Write comprehensive API documentation for our new user authentication endpoint.

Steps:
1) Start with a brief overview of what the endpoint does and when to use it
2) Document all request parameters with types, requirements, and constraints
3) Provide response schemas for success and all error cases
4) Write at least three practical code examples in different languages
5) Include a troubleshooting section addressing common integration issues

Context: This is a REST API endpoint for a fintech platform. Our developers range from junior to senior level. The authentication uses OAuth 2.0 with refresh tokens. We support JSON request/response format only. Rate limiting is 100 requests per minute per API key.

Examples: Model the documentation structure after Stripe's API docs: clear, scannable, with inline code examples and a right-side code panel approach.

Format: Structure as a single-page reference with: H1 title, overview paragraph, "Request" section with parameter table, "Response" section with JSON schemas, "Code Examples" section with tabbed language selector (Python, JavaScript, cURL), and "Errors" section with table of error codes and resolutions.

Example 2: Strategic Business Analysis

Role: Act as a management consultant with 15 years of experience in digital transformation strategy for mid-market companies.

Action: Develop a digital transformation roadmap for a traditional manufacturing company looking to modernize operations.

Steps:
1) Assess current digital maturity across five operational areas
2) Identify quick wins achievable within 90 days
3) Map medium-term initiatives for months 4-12
4) Define long-term strategic capabilities for year 2-3
5) Create a resource and investment plan for each phase
6) Identify key risks and mitigation strategies

Context: The company is a 50-year-old manufacturer with 800 employees, $120M annual revenue, and minimal digital infrastructure. They currently use spreadsheets for inventory management, paper-based quality control, and legacy ERP from 2010. The CEO has allocated $2M over three years for digital transformation. Key pain points are inventory accuracy (currently 78%), production scheduling delays, and inability to provide real-time order status to customers.

Examples: Structure the roadmap similar to McKinsey's digital transformation frameworks: phased approach with clear milestones, ROI projections per initiative, and a digital maturity scorecard that shows progress over time.

Format: Present as a professional consulting deliverable with: 1) Executive summary (1 page), 2) Current state assessment with maturity scores, 3) Transformation roadmap visual (described as a timeline), 4) Detailed initiative cards for each project (description, timeline, investment, expected ROI), 5) Risk register table, 6) Success metrics dashboard design.

Common Mistakes to Avoid

1. Skipping Steps and Letting the AI Choose Its Own Process

2. Generic or Missing Examples

3. Vague Format Specifications

4. Overloading Any Single Component

5. Role-Steps Mismatch

Best Use Cases for R.A.S.C.E.F.

Technical Documentation

• API references and developer guides
• System architecture documents
• Standard operating procedures
• Training manuals and onboarding guides

Business Strategy

• Market analysis and competitive intelligence
• Business plans and pitch decks
• Quarterly business reviews
• Digital transformation roadmaps

Content Creation

• Long-form blog posts and whitepapers
• Case studies with specific narrative structure
• Email campaign sequences
• Social media campaign strategies

Educational Content

• Course curriculum development
• Tutorial and how-to guides
• Workshop facilitation plans
• Assessment and evaluation frameworks

Bonus Tips for Mastering R.A.S.C.E.F.

• Start with Steps: When planning a RASCEF prompt, define your Steps first. They clarify what Role, Context, and Examples you need
• Use Examples strategically: Even a brief reference ("like Stripe's docs" or "similar to a TED talk structure") dramatically improves output quality
• Iterate on Format: If the first output isn't formatted right, refine your Format specification rather than rewriting the entire prompt
• Save your best prompts: RASCEF prompts are reusable templates, so build a library of your most effective ones
• Combine with other frameworks: Use RASCEF for the main task and APE for quick follow-up refinements

Conclusion

The R.A.S.C.E.F. Framework is the most comprehensive prompt engineering framework available, giving you control over not just what the AI produces, but how it gets there and what quality standard it targets. Its six components (Role, Action, Steps, Context, Examples, Format) leave virtually no room for ambiguity.

• The task is complex enough that methodology matters
• You have a specific quality standard or reference in mind
• The output format needs to be precise and professional
• You want repeatable, consistent results across similar tasks

• Start by converting your existing prompts to RASCEF format. You'll immediately see quality improvements
• Build a library of effective Steps sequences for common task types
• Collect reference examples that represent your quality standards
• Create reusable RASCEF templates for recurring workflows