I used to start each workday by staring at my editor for 15 minutes, figuring out what to do first. Then I'd waste another 20 minutes in standup trying to articulate my progress. By evening, I'd close my laptop with a vague sense of having done things but no idea what I actually accomplished.
That changed when I stopped using ChatGPT as a question-answer tool and started using it as a day-structure tool. Here's the exact workflow I built — and the prompts behind each step.
6:30 AM — Morning Structure
Before I open any code, I run one prompt that sets up my entire day:
Here are my top 5 tasks for today: [paste tasks]
Here are my meetings: [paste times]
My energy level right now: [1-10]
Generate a time-blocked schedule. Put the hardest task during my peak energy window. Include 15-minute buffers between meetings.
The key insight: don't ask ChatGPT to tell you what to do. Tell it what you need to do and ask it to organize it. The model is great at scheduling constraints — it handles buffer times, energy matching, and meeting conflicts better than any calendar app I've tried.
I keep 15 variations of this prompt in a pack I built — each one targets a different morning scenario (heavy meeting day, deep work day, deadline day, etc.).
9:00 AM — Standup Prep
My standups used to be rambling updates that wasted everyone's time. Now I run:
Here is my git log from yesterday: [paste]
Here are the tickets I worked on: [paste]
Generate a 3-sentence standup update: what I did, what I'm doing, what's blocked.
Three sentences. That's it. My team stopped asking follow-up questions because the updates became clearer.
10:00 AM — Code Review
This is where the biggest time save happened. Instead of writing vague "looks good LGTM" comments, I paste the diff and run:
Review this PR diff. Rate each section:
- 🔴 Must fix (will cause bugs)
- 🟡 Suggested (improves quality)
- 🟢 Nitpick (style preference)
Only flag 🔴 and 🟡 items. Explain why.
My PR reviews went from 10 minutes of skimming to 2 minutes of targeted feedback. Reviewers on my team started asking what tool I was using.
2:00 PM — Deep Work Sprint
After lunch, I do a single 90-minute deep work block. Before starting:
I'm working on: [describe the feature/bug]
Here's my current approach: [paste code or approach]
Generate: 1) Three things that could go wrong, 2) Two edge cases I should test, 3) One alternative approach that might be cleaner.
This prompt catches about 60% of the bugs I would have discovered later during testing. Not perfect, but significantly better than my previous "just start coding" approach.
5:30 PM — Shutdown Ritual
Before closing my laptop, I run a wind-down prompt:
Here's what I planned to do today: [paste morning plan]
Here's what I actually did: [paste git log + completed tickets]
1) What did I accomplish?
2) What carried over?
3) One thing I'm proud of today
4) One thing I'll do differently tomorrow
This 2-minute ritual replaced the "I feel like I did nothing" anxiety with a concrete sense of progress.
Sunday — Weekly Reset
Every Sunday evening, I do a 15-minute review:
Weekly review:
- Tasks completed: [paste]
- Tasks that carried over: [paste]
- Energy patterns: when did I feel most/least productive?
- What should I change about next week's schedule?
Generate a weekly summary and next week's priority list.
This single prompt caught the pattern that I was most productive between 9-11 AM on coding tasks — and almost useless between 2-3 PM (post-lunch crash). I restructured my schedule around that and gained roughly 2 productive hours per week.
The Boring Practical Details
- I use ChatGPT (GPT-4o) for structured prompts like scheduling and code review. Claude for creative tasks like writing and brainstorming. The model choice matters less than prompt specificity.
- I keep a text file with my 15-20 go-to prompts. Not 500. Not a database. A text file. I copy-paste the relevant one and fill in the brackets.
- The whole routine takes about 20 minutes total across the day. The return is easily 2+ hours of recovered time from better scheduling, faster reviews, and fewer "what am I doing" moments.
- It took about two weeks to make this habitual. The first three days I forgot to run the morning prompt and the whole day felt unstructured again.
Where to Find More
I've collected all the prompts I use daily — morning routine, workday standups, code review templates, evening reflection, weekly resets — into organized packs. They're at my store if you want the full collection. The Weekly Reset ($2.99) is the cheapest entry point if you just want to try the Sunday ritual.
The point isn't the prompts themselves — it's the structure. Having a repeatable system for starting, executing, and closing each day removes the decision fatigue that kills most developer productivity.
What does your daily workflow look like? I'm curious what other people have automated.
Top comments (0)