The RTCF Framework: Role, Task, Context, Format

Why RTCF Works

Most weak prompts omit one dimension. Role sets expertise and tone. Task states the action unambiguously. Context supplies audience, stack, and constraints. Format defines how the answer must look. Add Constraints for what to avoid.

Minimal Template

ROLE: You are a ...
TASK: ...
CONTEXT: Audience, stack, deadline, ...
CONSTRAINTS: Do not ...
FORMAT: Return markdown with H2 sections ...

Example — Technical Writer

ROLE: B2B SaaS technical writer.

TASK: Rewrite this error message so users know what to do next.

CONTEXT: Audience is non-technical admins; product is billing portal.

CONSTRAINTS: Under 40 words; no jargon; no blame.

FORMAT: One improved message + two alternates in a table.

Common Mistakes

Role without task ("act as expert" then nothing). Task without format (wall of text). Context that is actually the entire document with no question. Fix by filling every section in order.

Tool on SlashGit

Use the free Prompt Optimizer to expand a rough sentence into a full RTCF brief, or switch to Orchestrator/Swamp structures for agent workflows.