Disclosure: This post may contain affiliate links. If you click and buy, I may earn a commission at no extra cost to you.
Stop Rewriting Emails: A ChatGPT Workflow That Sounds Like You
This is a longer, story-driven guide you can use as a template—not just a list of tips.
A friend texted me: “Can you help me figure this out?” and my brain immediately tried to write a 12-step plan.
Then I paused and asked: what would a simple plan look like?
That tiny reframe changed everything about how I work.
What GPT-5.2 is aiming to improve
The big practical shift: GPT-5.2 is positioned for long-context, multi-step projects—where you plan, execute, and review in one sustained workflow. If you’re building content systems, agents, or repeatable processes, that’s where you feel it most.
The “project thread” rule
Use one thread per project. Don’t mix unrelated tasks. Keep a running summary at the top of the thread so the model stays aligned.
The 3-phase loop: Plan → Execute → Verify
- Plan: 7 steps, each with a deliverable and definition of done.
- Execute: do one step at a time; insist on a specific output format.
- Verify: ask for risks, assumptions, and what to validate.
Copy/paste prompt pack for GPT-5.2
You are my project partner.
Project: [project].
Goal: [definition of done].
Constraints: [time/budget/audience/tools].
1) Make a 7-step plan. For each step: deliverable, time estimate, risks.
2) For Step 1, ask 7 clarifying questions.
3) After I answer, produce: (a) deliverable, (b) review checklist, (c) risk list, (d) next step.Instant vs Thinking vs Pro (simple decision tree)
- Instant: you already know what you want; you just need a fast draft.
- Thinking: you’re unsure and need structured reasoning (tradeoffs, plans).
- Pro: you’re shipping a multi-part deliverable and want fewer mistakes.
Where people get stuck
- They ask for a full project in one go (too big, too vague).
- They skip clarifying questions (hello rework).
- They don’t force an output format (so results become messy).
- They never run a review checklist (so mistakes slip through).
Five high-ROI use cases
- Build a content calendar + internal linking plan in one sitting.
- Turn research notes into a clean, publishable HTML draft.
- Draft a spreadsheet spec (columns, formulas, checks) for a side hustle.
- Create a step-by-step SOP (standard operating procedure) for repeated tasks.
- Convert a rough project idea into milestones, risks, and next actions.
Recommended tools (affiliate links)
- Keyword research tool (pick topics people already search for)
- Email marketing platform (build an owned audience)
- Portable SSD (keep assets and drafts organized)
- Standing desk (helps long sessions feel easier)
- Noise-cancelling headphones (focus mode)
FAQ
- Should I trust it for facts? Use it for structure; verify facts when they matter.
- How do I reduce hallucinations? Require assumptions + verification steps.
- How do I keep consistency? Maintain a project summary and reuse templates.
One-day challenge (do this today)
- Pick one real task that’s been hanging over your head.
- Set a 15-minute timer and run the template from this post.
- Ship a “version 1” (even if it’s imperfect).
- Write down one thing you’ll improve tomorrow.
Small reps beat big plans. Tomorrow, repeat with a slightly better prompt or checklist.
Related topics: email writing, tone, templates.
If you found this useful, bookmark it and reuse the templates. The real payoff is repetition.