How to Plan with Claude AI: A Step-by-Step Guide

If you’ve tried asking Claude “help me plan my day” and gotten a generic list of time-management tips, the problem wasn’t Claude — it was the setup.

Claude’s planning quality scales directly with the context you give it. This guide walks you through the full setup: a working Claude Project, a configured system prompt, and your first real planning conversation.

Step 1: Get the Right Access Level

Claude’s free tier supports individual conversations, which is enough to try planning. But for sustained, recurring planning, you need Claude Projects — a feature available on the Pro plan at claude.ai.

Projects give every planning conversation persistent context: your goals, your role, your constraints. Without it, you’re re-explaining yourself every session.

If you’re evaluating whether Claude is worth the subscription for your workflow, complete steps 2 and 3 in a single free conversation first. That’ll give you enough of a signal.

Step 2: Create Your Planning Project

Log into Claude.ai and click “New Project” in the left sidebar.

Name it something clear: “Weekly Planning,” “Work Planning,” or “[Your Role] Planning.” You’ll return to this Project every time you plan, so a descriptive name matters.

You’ll see two areas: Project Instructions and Project Files (Knowledge). Both matter.

Step 3: Write Your Project Instructions

This is the highest-leverage step in the whole process. Spend ten minutes here and every future planning session improves.

The instructions field accepts free-form text. Here’s a structure that works:

You are my planning partner. Key context about me:

Role: [your title and main function]
Team/org: [brief description — solo, team size, industry]

Current goals (this quarter):
1. [Goal 1]
2. [Goal 2]
3. [Goal 3]

Standing constraints:
- [Recurring meetings or commitments]
- [Hard deadlines this period]
- [Energy patterns: e.g., "I'm sharpest 8–11am, avoid scheduling creative work after 3pm"]

Planning preferences:
- Always ask me for my energy level before suggesting today's priority order
- Tell me when I'm overcommitting — I consistently underestimate meeting drain
- Format weekly plans as a table: Day | Focus Block | Tasks | Admin
- Be direct. I don't need encouragement, I need accurate sequencing.

Adjust every line to match your actual situation. Generic instructions produce generic plans.

Step 4: Upload Reference Documents (Optional but Powerful)

In the Knowledge section, upload documents Claude should reference:

• Your current OKRs or goals doc
• A project brief for your largest active project
• A running “context doc” you update each quarter with role changes, new priorities, and constraints

Claude will reference these in every conversation. A founder who uploads their one-pager gets planning advice that reflects their actual strategic priorities, not a generic to-do prioritization.

Keep documents focused. A 50-page strategy deck is less useful than a two-page summary of current priorities.

Step 5: Run a Setup Verification

Before your first real planning session, test that Claude has the context right.

Open a new conversation inside the Project and ask:

Without me telling you anything more, summarize what you know about my role, goals, and planning constraints. Then tell me: what are the 3 planning failure modes most likely to bite someone in my position?

If the summary is accurate and the failure modes are specific to your situation, the Project is working. If the response is generic, your instructions need more specificity.

Step 6: Run Your First Weekly Plan

With the Project configured, run your first real planning conversation. Do this on Sunday evening or Monday morning.

It's [day, date]. Here's my week:

Calendar commitments: [paste from your calendar — event names and durations are enough]
Key deadlines this week: [list]
Carry-over from last week I haven't finished: [list]
My energy this week feels: [low / medium / high, and why if relevant]

Build me a weekly plan. Format it as an Artifact: one row per day, columns for Focus Block, Priority Tasks, and Admin/Comms window. Flag any day where I'm overloaded.

This prompt gives Claude the raw materials it needs: your actual calendar, your real deadlines, your carry-over, and your energy forecast.

The explicit request for an Artifact produces a formatted table rather than prose. That matters — a planning document should look like a planning document.

Step 7: Review and Adjust Before Committing

Claude’s first weekly plan will be a good draft. It won’t be perfect.

Read through it and ask yourself:

• Does the focus block assignment match when I’m actually sharpest?
• Are there days where the task list is unrealistically long?
• Did Claude catch the dependency between [task A] and [task B]?

Then reply with corrections:

Good draft. A few adjustments:
- Tuesday's focus block should be the proposal, not the code review — the proposal is due Thursday
- Wednesday afternoon is actually a half-day for me, remove two items from that list
- Add a 30-minute buffer before the Friday board call

Revise the Artifact with these changes.

The Artifact updates in place. You’re not regenerating — you’re editing.

Step 8: Run the Daily Check-in

Each morning, open the same Project and run a quick check-in:

Daily check-in. Today is [date].

My plan for today was: [paste today's row from the weekly plan]
What's changed since I made that plan: [any surprises, new fires, shifted deadlines]
My energy right now: [1-10 or descriptor]

What should I actually focus on this morning?

This takes two to three minutes. It keeps your daily execution connected to the weekly plan without forcing you to re-derive priorities from scratch every morning.

What to Do When Plans Fall Apart

They will. Weekly plans rarely survive contact with Tuesday.

When your week derails, don’t abandon the system — update it.

My plan fell apart today because [reason]. I have [X hours] left. Here's what's still undone: [list].

What do I actually do with the rest of today? And what from this week's plan needs to move to next week?

This is where the planning conversation earns its keep. Claude can do rapid triage without the emotional weight of deciding what to abandon — it just looks at the constraints and the list.

The setup described here takes about fifteen minutes. After that, each planning conversation takes five to fifteen minutes. The discipline isn’t in the setup — it’s in running the conversations consistently.

Start now: Open Claude.ai, create a Project called “Weekly Planning,” and write your system instructions using the template in Step 3. Don’t plan — just configure. The plan can happen tomorrow morning.

Related: The Complete Guide to Planning with Claude AI · The Claude AI Planning Framework · 5 Claude Prompts for Planning · Complete Guide: Daily Planning Ritual with AI

Tags: how to plan with Claude AI, Claude Projects planning, AI daily planning, Claude weekly plan, planning workflow