Situation · Purpose · Expected Output · Context · Style
Detail-oriented and precise. The Expected Output field eliminates guesswork and is ideal for complex technical tasks.
The current state or problem that needs to be addressed.
Why this task matters — the business or personal goal behind it.
An exact description of what the output should contain, formatted as, and deliver.
Constraints, background, relevant data, or domain-specific information.
The voice, format, and presentation style for the output.
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.
SPECS stands for Situation, Purpose, Expected Output, Context, and Style — a high-detail framework ideal for complex technical and professional tasks.
The Expected Output field forces you to define exactly what success looks like before you ask the AI, preventing vague or misaligned responses.
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.
All 9 frameworks are built in. Write, optimize with your own LLM, dispatch to 25+ AI models, and run consensus analysis — free, no account required.
Join the Waitlist