When should you use it?
- A project has a deadline that feels padded and you want to see where the time goes
- A personal goal, such as a job search or a side business, keeps slipping
- You want to separate tasks that are genuinely slow from tasks stuck waiting on someone
Not for: Work with fixed physical or legal lead times, such as shipping, permits or curing, that no plan can shorten; Setting deadlines for other people without their input; Promising a customer the fastest possible date; it is a thinking tool, not a commitment
What do you need, and what do you get?
You need
- The project and its current deadline
- Honest answers about each task and what it is waiting on
You get
- A list of every task with its no-waiting duration
- Your current timeline beside it with the gap for each task
- The three biggest gaps, each labeled waiting, permission, fear or real work
- A one-page plan to close the largest gap this week
How does it work, step by step?
- Fill in the project lineReplace the bracketed placeholder with what you want finished and the date you are aiming for.
- Answer one question at a timeLet the assistant build the task list. Say plainly when a task is waiting on a reply, an approval or your own decision.
- Read the gap tableLook for tasks where the gap is large but the real work is small; those are usually queues or approvals.
- Pick one gapUse the one-page plan to remove the biggest gap this week, for example by booking the approval meeting now.
- Recheck next weekRun it again with updated answers to see whether the timeline moved.
The prompt
The original prompt by @free_ai_guides, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in ChatGPT, Claude, Gemini and others. Values in lime are placeholders.
Original prompt by @free_ai_guides
You are my speed of light coach, using Jensen Huang's rule at Nvidia: measure every plan against what is physically possible, with no waiting and no queues. My project: [what you want finished and your current deadline] Ask me one question at a time until you can list every task it takes. For each task, ask how long it would take if nothing was waiting on anyone. Then give me: 1. The speed of light timeline, with every task at its fastest possible time 2. My timeline next to it, with the gap in days for each task 3. The three biggest gaps and what causes each one: waiting, permission, fear or real work 4. A one page plan that closes the biggest gap this week Rules: never compare me to how long it took last time or how long it takes other people.
Exactly as published by @free_ai_guides in X post: a speed of light coach prompt for finishing any project.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
Act as a planning coach for our team project: {project_and_deadline}. Team members: {team}. Ask one question at a time until every task is listed with an owner. For every task, find out its duration if nothing and nobody were holding it up. Treat each handoff between people as its own line. Then show: the fastest possible timeline; our current timeline beside it with the gap in days per task; the three largest gaps, each labeled waiting, approval, hesitation or real work; and a one-page plan to close the largest gap this week, with who does what. Do not compare us with past projects or other teams, and mark any lead time that cannot be shortened.
What can go wrong?
- Treating the fastest timeline as a promise. It is a benchmark that shows where delay comes from, not a schedule.
- Answering optimistically about your own work. Be honest about tasks that need real effort so they are not mislabeled as waiting.
- Ignoring other people. Gaps caused by approvals need a conversation, not just a faster plan on paper.
- Pasting confidential project details into a personal AI account without checking your company's rules.
Our take
Most project plans are built by adding up how long things took last time, which quietly bakes old delays into new deadlines. This prompt flips that by starting from the fastest a task could go if nothing were waiting, then showing your real plan beside it. The useful part is the diagnosis. Labeling each big gap as waiting, permission, fear or real work turns a vague sense of being behind into something you can act on, and very often the answer is an approval or a reply rather than effort. Asking one question at a time also matters, because it stops the assistant from inventing a task list for a project it knows nothing about. Keep the output in perspective. A fastest possible timeline is a benchmark, not a deadline to promise anyone, and some lead times cannot be compressed. For teams, we added a variant that names an owner per task and counts handoffs separately. In our dry run on a fictional website relaunch, the biggest gap turned out to be eight days of waiting for legal sign-off, not the design work.
Where the time goes back: Seeing each task next to its no-waiting duration shows at a glance which delays come from queues and approvals rather than real effort, so you fix the one gap that moves the deadline instead of working harder on everything.
FAQ
Who wrote the prompt?
Does it work for team projects?
Which assistant should I use?
Source and credit
The original prompt on this page is by @free_ai_guides, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- X post: a speed of light coach prompt for finishing any project
- Creator
- AI Guides (@free_ai_guides)
- Published on
- X
- Original date
- Nov 13, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Custom agent
- AI dry run
- Nov 13, 2026: passed. Dry-run tested by our AI test agent on sample input. One question at a time, correct gap arithmetic, causes labeled, actionable plan for the largest gap.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 13, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.