COSTAR: Context, Objective, Steps, Tools, Actions, Reflection
Irrelevant context confuses the model; a reflection step makes it grade its own work before you see it.
Context: only relevant background ('B2B SaaS for marketing managers at mid-market firms; LinkedIn in Q4; 40% churn trial-to-paid'). Objective: the success condition (raise trial-to-paid; position the CEO; capture emails). Steps: numbered reasoning - analyse pain points, identify benefits, create emotional hooks, structure the argument, write CTAs - self-reasoning improves output. Tools: frameworks, data, formats (McKinsey framework, HTML template, SWOT). Actions: the output spec ('5 email templates with subject lines, preview text and send timing'). Reflection: 'before finalising, check brand consistency, clear value proposition and a compelling CTA, and suggest one improvement per email'. Worked example in Claude: project-management SaaS losing 65% of trials; five emails (welcome, three-click setup, team momentum, pro tip, first win) with self-scores; 'consider the brand voice to be that of Asana'. Note: this differs from the published CO-STAR (Style, Tone, Audience, Response).
Saves iterations and bakes in a quality check.


