These five prompts cover the core use cases for Beyond Time’s MCP integration with Claude. Each one is ready to copy and adapt.
Prerequisites: the Beyond Time MCP must be set up in Claude Desktop. If you haven’t done that yet, see the setup guide.
Prompt 1: The 90-Second Daily Log
Use this at the end of every workday. Fill in your actual status for each goal — even if it’s zero progress.
End of day log for Beyond Time. Please record each of these:
[Goal name 1]: [what happened — numeric if possible,
e.g. "800 words written" or "no progress — 3 meetings
ate the afternoon"]
[Goal name 2]: [what happened]
[Goal name 3]: [what happened]
Log all entries and note any that look like they might
need attention this week.Why it works: Logging zeros matters as much as logging wins. The weekly summary’s absence-detection can only work if you’ve maintained a consistent record. This prompt keeps sessions under two minutes while building the data foundation you need.
Prompt 2: The Friday Weekly Review
Use this once per week. Replace “this week” with the actual week if you’re running it retroactively.
Pull my Beyond Time weekly summary for this week.
Tell me:
1. Which goals had log entries and which didn't
2. Whether my current pace puts me on track for each
goal's target date
3. Which goal concerns you most based on the data,
and why
Be direct — I want honest pattern analysis, not
encouragement.Why it works: The last line matters. Without it, Claude tends toward polite observations. Asking for honest pattern analysis shifts the response toward the uncomfortable observations that are most useful — the stalled goal, the unrealistic target date, the habit that’s quietly falling apart.
Prompt 3: Milestone Progress Check
Use this when you want to see where you stand on a specific goal before a meeting, review, or key deadline.
Using Beyond Time, show me:
- The milestones for my [goal name] goal
- Which ones are complete and which are still open
- Whether any open milestones are overdue
If I need to reprioritize milestones to hit the target
date, what would you suggest dropping or pushing?Why it works: The last question turns a status check into a decision prompt. You’re not just reviewing the list — you’re asking Claude to reason about trade-offs given your current timeline. That’s a materially different kind of help.
Prompt 4: Cross-Goal Conflict Detection
Use this once a month, after you have four or more weeks of log data.
Pull my full goal list and the past four weeks of log
data from Beyond Time. I want to know:
1. Are any of my goals competing for the same type of
time or energy? (e.g., both require evening focus
time, both depend on the same mental state)
2. Is there a goal that's consistently getting
deprioritized when other goals are active?
3. Based on the data, is there a priority conflict I'm
resolving by default rather than by choice?Why it works: This is the prompt most likely to surface something genuinely uncomfortable — a conflict you’ve been resolving by silently failing one goal rather than making an explicit trade-off. The data from Beyond Time makes the pattern visible; the prompt gives Claude permission to name it.
Prompt 5: Monthly Goal Adjustment
Use this at the start of each month to decide which goals continue, which get revised, and which get archived.
I want to do a monthly goal adjustment. Pull all my
active goals from Beyond Time and assess each one:
1. What's the progress rate over the past 30 days?
2. Is that pace realistic given the remaining time
to the target date?
3. Does the goal definition still make sense, or
has something changed in my actual priorities?
After the assessment, I want to make one of three
decisions for each goal: continue as-is, revise
(timeline or scope), or archive.
Help me work through each one.Why it works: The three-decision structure removes the ambiguity that makes goal reviews drag. You’re not doing open-ended reflection — you’re making a concrete decision about each goal. Claude’s role is to give you the data and a recommendation; the decision is yours.
Adapting These Prompts
These are templates, not scripts. The structure matters; the exact wording doesn’t.
If you find yourself rephrasing them the same way every time, update your version. If Claude consistently misinterprets a prompt and calls the wrong function, add a clarifying phrase (“using my Beyond Time data specifically” or “pull the data before answering”).
The goal is prompts that consistently get you the data and analysis you need in the shortest exchange. Over time, you’ll develop your own variations.
Start here: Copy Prompt 1, adapt the goal names to match your active goals in Beyond Time, and run it tonight.
Related:
- The Complete Guide to Beyond Time MCP
- Beyond Time MCP Full Walkthrough
- The MCP Planning Loop Framework
- Planning with Claude AI
Tags: beyond time MCP prompts, Claude planning prompts, AI goal review prompts, MCP planning templates, weekly review AI prompts
Frequently Asked Questions
-
Do these prompts require any special setup beyond the MCP connection?
No. If the Beyond Time MCP is connected to Claude Desktop, these prompts will invoke the relevant commands automatically. You don't need any additional configuration. -
Can I modify these prompts?
Yes — and you should. Adapt the phrasing to match how you naturally talk about your goals. The structure matters more than the exact words. -
What if Claude doesn't call a Beyond Time function when I use these prompts?
Add explicit framing: 'Using my Beyond Time data...' at the start of the prompt. This signals that you want live data rather than general AI advice. -
Which prompt should I start with if I'm new to the MCP connection?
Prompt 1 (the daily log). It's the lowest-stakes entry point and builds the data foundation that makes the other four prompts useful. -
How often should I use Prompt 4 (conflict detection)?
Monthly. It's most useful after you have four or more weeks of log data to work from. Running it with too little data produces observations that may not reflect stable patterns.