What is the COAST Framework?
COAST is a structured prompt engineering framework built around five components: Context, Objective, Actions, Scenario, and Task. Unlike purely instruction-driven frameworks, COAST includes a dedicated Scenario component that places the prompt inside a realistic, specific situation — making the AI's output far more contextually relevant.
- C — Context: Set the Background
- O — Objective: Define the Goal
- A — Actions: List the Steps
- S — Scenario: Ground it in a Situation
- T — Task: Specify the Deliverable
The framework is particularly powerful for content that needs to feel lived-in: training materials, customer service scripts, roleplay simulations, case studies, and any deliverable where the situational environment shapes the appropriate response.
Think of COAST as the difference between asking "write a sales email" and providing the full situation — who the buyer is, what's at stake, what has already happened — so the AI can craft something that would actually work in that specific moment.
When to Use the COAST Framework
Roleplay & Simulation
Set the scene for negotiation practice, customer service training, interview prep, or conflict resolution scenarios with full situational context.
Training Content
Create realistic learning scenarios for onboarding, compliance training, or skill development where the situation determines the correct response.
Case Studies
Develop detailed case studies for business education, marketing, or internal reviews with full situational grounding and concrete deliverables.
Scenario-Based Writing
Draft emails, proposals, reports, and communications that must account for a specific situation, relationship history, and contextual pressures.
Customer Journey Mapping
Map realistic customer scenarios across touchpoints, with specific personas, pain points, and goals that shape how communications should be written.
Organizational Planning
Develop situationally-aware plans for hiring, restructuring, product launches, or crisis response where the specific organisational context drives the output.
How to Use the COAST Framework
- C
Context — Set the Background
Describe the environment, organisation, or situation the AI needs to understand before doing any work. Include size, industry, recent history, constraints, and any other background that shapes what good output looks like. This is the "who we are and where we are" section.
- O
Objective — Define the Goal
State the overarching goal clearly in one or two sentences. What outcome are you trying to achieve? The Objective is the "why" behind the Task — it tells the AI what success looks like at a strategic level, even before the specific deliverable is named.
- A
Actions — List the Steps
Break the work into numbered, concrete actions you want the AI to take. This is your instruction set — it removes ambiguity about scope and sequence. Actions should be specific enough that the AI knows exactly what to produce at each step.
- S
Scenario — Ground it in a Situation
Describe the specific, realistic situation the output must address. Who are the people involved? What is their background, relationship, and current state? What pressures or constraints exist? The Scenario transforms generic output into something that could only work in this exact situation.
- T
Task — Specify the Deliverable
State exactly what you want the AI to produce: a document, a list, a script, a plan. Be specific about format, length, and structure. The Task is your final instruction — everything above exists to inform this output.
Prompt Examples
Role: You are a corporate trainer designing onboarding materials. Context: Our company is a 200-person SaaS startup that recently shifted to fully remote work. New hires often feel isolated and struggle to understand internal processes during their first 30 days. Objective: Create a structured 30-day onboarding plan that helps new hires build relationships, understand company processes, and become productive quickly. Actions: 1. Outline week-by-week milestones for the first 30 days. 2. Include daily check-in rituals and async communication norms. 3. Specify who the new hire should meet in each week. 4. Add recommended tools, docs, and internal resources for each phase. Scenario: A new mid-level software engineer joins the team on Monday. They have strong technical skills but no prior remote-first experience. Their manager is in a different time zone. Task: Produce a day-by-day 30-day onboarding calendar with owners, resources, and success checkpoints for each week.
Role: You are a customer success manager at a B2B analytics platform. Context: Our platform helps e-commerce companies track conversion funnels. A long-standing enterprise client (3-year relationship, $180K ARR) has missed two check-in calls and their product usage dropped 40% over the last 60 days. Objective: Re-engage the client, identify the root cause of disengagement, and create a recovery plan that prevents churn. Actions: 1. Draft an outreach email that is warm but direct about the usage drop. 2. Prepare five discovery questions for the re-engagement call. 3. Propose three concrete value-add offers (e.g., feature workshop, custom report). 4. Define success metrics for the next 30 days post-call. Scenario: The client's primary champion recently left the company. The new point of contact is a VP of Marketing who is unfamiliar with your platform and skeptical of analytics tools. Task: Deliver the outreach email, the discovery question list, and a one-page recovery plan I can present internally before the call.
Pros and Cons
| 🟢 Pros | 🔴 Cons |
|---|---|
| Scenario component produces situationally-aware, realistic output | Five components make it verbose — overkill for simple factual queries |
| Actions section removes scope ambiguity and structures the work | Scenario writing requires effort to be specific without being overly constraining |
| Works exceptionally well for training, roleplay, and case-study content | Less suited for purely analytical or data-processing tasks |
| Flexible — components can be reordered or omitted for simpler tasks |
Frequently Asked Questions
What does COAST stand for?
COAST stands for Context, Objective, Actions, Scenario, and Task. Each component layers critical information: Context sets the background, Objective defines the goal, Actions list concrete steps, Scenario grounds the prompt in a realistic situation, and Task specifies the exact deliverable you need.
How is COAST different from other structured prompt frameworks?
The distinguishing feature of COAST is the Scenario component. While frameworks like RISEN or CRISPE focus on role and instructions, COAST explicitly grounds the prompt in a realistic, situational setting. This makes it particularly powerful for training content, roleplay, case studies, and any task where situational nuance matters.
When should I use the COAST framework?
Use COAST when your task requires situational realism — onboarding plans, customer service scripts, negotiation training, policy walkthroughs, or any scenario-based content. If your task is purely analytical or data-driven without a situational setting, a simpler framework like RISEN or APE may be more efficient.
Can I skip components of COAST if they are not relevant?
Yes. The Scenario component is the most frequently optional one — if your task is abstract rather than situational, you can omit it. However, the more components you include, the more precisely the AI can tailor its response. At minimum, Objective and Task should always be present.
How detailed should the Scenario section be?
The Scenario should include enough situational detail to remove ambiguity about the setting: who is involved, what their background is, what constraints or pressures exist. Two to five sentences is usually sufficient. Avoid over-specifying details that are not relevant to the output you need.
Does COAST work well for creative writing and roleplay?
Yes — COAST excels here. The Scenario component naturally sets the stage for roleplay, fiction, and immersive training simulations. You can use it to write customer service dialogues, negotiation scripts, interview prep scenarios, or even fictional short stories grounded in a specific setting.
How does COAST compare to the RISEN framework?
RISEN (Role, Instructions, Steps, End Goal, Narrowing) is more execution-focused and procedural. COAST adds a Scenario component that RISEN lacks, making COAST better for situationally-grounded content. RISEN is stronger for precise, multi-step technical instructions where situational context is less important.