SPECS Framework
Situation · Purpose · Expected Output · Context · Style
Detail-oriented and precise. The Expected Output field eliminates guesswork and is ideal for complex technical tasks.
- Definition
- The SPECS framework (Situation · Purpose · Expected Output · Context · Style) is a prompt engineering structure that breaks your AI request into 5 discrete fields. It is best suited for complex technical analysis and research tasks.
The 5 Fields
Situation
The current state or problem that needs to be addressed.
Purpose
Why this task matters — the business or personal goal behind it.
Expected Output
An exact description of what the output should contain, formatted as, and deliver.
Context
Constraints, background, relevant data, or domain-specific information.
Style
The voice, format, and presentation style for the output.
Real Example
Scenario: Producing a technical specification document
Situation: We need an API integration between our CRM and email platform. Purpose: Automate lead nurturing workflows. Expected Output: A 500-word technical spec with endpoint list, auth method, and error handling requirements. Context: REST APIs, OAuth 2.0, 10k contacts. Style: Technical, structured with headers.
When to Use SPECS
- ✓Complex technical analysis and research tasks
- ✓Tasks with precise output requirements
- ✓Scenarios where the AI needs extensive context
- ✓Professional deliverables with defined specifications
- ✗Quick everyday tasks (use APE or RTF)
- ✗Creative tasks where open-endedness is valuable
- ✗Tasks with a natural step-by-step flow (use RISEN)
Frequently Asked Questions
What does SPECS stand for?
SPECS stands for Situation, Purpose, Expected Output, Context, and Style — a high-detail framework ideal for complex technical and professional tasks.
What makes the Expected Output field unique?
The Expected Output field forces you to define exactly what success looks like before you ask the AI, preventing vague or misaligned responses.
How is SPECS different from CO-STAR?
SPECS focuses on defining output requirements precisely; CO-STAR focuses on controlling voice, tone, and audience. Use SPECS for technical deliverables, CO-STAR for content.