PARA / RTSCEN
When to use
- Analyzing data or problems; need structured, thorough output.
- High-stakes or complex tasks (RTSCEN).
- Problem diagnosis and recommendations (PARA).
When not to use
- Simple content creation → CORE/CREATE.
- Storytelling → DARE.
- Choosing between options → ROAD.
Template
Copy/paste template
ROLE: You are [expertise]. TASK: [Specific action and deliverable] SPECIFICS: [Constraints, requirements, scope] CONTEXT: [Background that changes the output] EXAMPLES: [If format/style matters] NOTES: [Edge cases, audience, preferences] (PARA: PROBLEM → ANALYSIS → RECOMMENDATION → ACTION)
Example
ROLE: Cybersecurity risk analyst. TASK: Assess security risks for multi-cloud data migration; prioritized mitigation plan. SPECIFICS: GDPR/HIPAA/SOC2, $500K budget, 6 months. CONTEXT: 50TB from on-prem to AWS/Azure; board concerned about breach risk. NOTES: Legal focused on EU residency; avoid vendor lock-in.