Claude Prompts for Productivity: Plan, Focus, and Review

The best Claude prompts for productivity turn a real task list and available time into a short plan, then compare that plan with what actually happened. Ask for one useful outcome, a first action, and a clear stopping point. Avoid asking the assistant to fill every minute or decide your commitments for you.

fenbs can keep the prompts, progress checkpoint, and lessons outside a single chat, so your next session can continue the same work. If you need a short introduction to the assistant, see what Claude is. The templates here focus on your working day rather than on a particular app feature.

What should you give Claude before it plans your day?

Supply the tasks you are choosing between, real deadlines, fixed commitments, dependencies, and time you can actually use. Mark estimates as estimates. A polished schedule built on imaginary availability is still an imaginary schedule, even if its time blocks look convincing.

Anthropic’s prompting guidance↗ (opens in a new tab) recommends clear constraints and a specific output format. Tell Claude whether you want help deciding, breaking down work, or reviewing a plan. Asking for all three at once often creates more material than you need to start.

• Daily input prompt: My available work periods are [times], with these fixed commitments: [list]. My candidate tasks are below, each with a deadline, rough effort estimate, dependency, and reason it matters. Identify missing facts that could change the order.
• Output rule: Propose a short plan and explain the tradeoffs. Label uncertain estimates. Do not invent deadlines, commitments, stakeholder preferences, or permission to drop an obligation. Leave the final priority choice to me.

Use general task descriptions if a plan would otherwise expose client, employee, or personal details. You rarely need the complete source document to decide that reviewing its first section is the next action. Keep sensitive content in the appropriate work system.

How do you choose a priority without a giant ranked list?

Ask Claude to show a small set of choices with consequences. You might have a proposal to revise, an internal update to write, and a blocked expense question. The useful output explains which task protects a deadline or unblocks someone, rather than assigning arbitrary scores to every item.

• Priority prompt: From this task list, propose one main outcome for today, one smaller supporting task, and one task to defer. Explain the deadline or dependency behind each choice. Show what would change your recommendation. Ask me to approve the tradeoff.
• Overload prompt: Compare these tasks with my available time. If they do not fit, show the conflict plainly. Propose options to reduce scope, change sequence, or ask a person about a deadline. Do not silently compress every estimate until the plan fits.

Turn the chosen outcome into a visible artifact: a reviewed introduction, a tested calculation, or a list of unresolved questions. Finish proposal is too broad to guide the next half hour. Review three client comments and draft responses makes progress easier to recognize and easier to resume.

What prompt helps you start a focused work block?

Give one task a narrow boundary and define what finished means for this block. Include necessary inputs, an opening action, and a stopping rule. The assistant should help you enter the work, not produce another planning exercise that consumes the time reserved for it.

• Focus prompt: Help me prepare a [duration]-minute work block on [task]. The output I want is [artifact]. Give me the first physical action, the materials I need, three steps at most, and a definition of sufficient progress. Put unrelated ideas in a later list.
• Scope prompt: If this outcome is too large for the block, propose a smaller useful result. Preserve the review step. State what will remain unfinished so I do not confuse a partial draft with completed work.

Use your own timer and calendar for the work period. A written prompt does not itself create a reminder or move a meeting. If a plan depends on an external action, such as asking a colleague for a file, treat that as a separate action you must perform or explicitly authorize.

How do you restart after an interruption?

Write a small checkpoint before you leave when possible: the artifact, last completed step, unresolved question, and next action. When you return, ask Claude to rebuild the starting point from that record. Do not ask it to guess what happened during time it cannot see.

• Restart prompt: Here is my last checkpoint and what changed while I was away. Separate completed work from intended work. Give me one action to verify the current state and one action to continue. If the checkpoint conflicts with new information, show the conflict first.
• Stuck prompt: I have tried [actions] and observed [results]. Help me distinguish missing information, an unclear decision, and a task that is too broad. Suggest one small diagnostic action for each plausible cause, then ask which I want to try.

Anthropic’s guidance on reducing hallucinations↗ (opens in a new tab) supports giving the assistant room to acknowledge missing information. An honest request for the current draft is more useful than an invented account of what you finished. In fenbs, Where we left off keeps a saved starting point connected to the work.

What should an end-of-day review produce?

Ask for a factual comparison between the plan and the outcome. Keep completed artifacts, failed checks, waiting decisions, and tomorrow’s first action distinct. The review should leave you with a smaller amount to remember, rather than a narrative that praises the day regardless of the evidence.

• Review prompt: Compare my original plan with these actual results. List completed work, partial work, blockers, and promises still outstanding. Use only the evidence I provide. Draft a checkpoint with the next action and anything waiting on another person.
• Lesson prompt: Identify one specific mismatch between the plan and what happened. Suggest a practical change I can test next session. Do not infer a permanent personality trait from one day, and do not turn a suggestion into an approved rule.

For example, if a review needed a missing reference, tomorrow’s adjustment may be to gather sources before opening the draft. Test that change before making it a permanent routine. Save observations separately from decisions, so a later assistant can see what happened and what you actually chose to change.

How to do this with fenbs

1. Create a free account and add one active project. Add the tasks that matter to that project instead of importing every possible future commitment.
2. Save the priority, focus, and review templates you want to test in Skills and prompts. Keep required inputs and expected outputs with each one.
3. Connect Claude through the relevant integration guide. Ask it to read the project context and the selected template before helping with today’s plan.
4. Before stopping, save actual task progress and Where we left off. Record a lesson when you have evidence for a useful change; let a person decide any continuing rule.

fenbs is not the right fit if all you need is a timer or calendar alarm. Its value here is the work record you reuse across sessions. Keep browsing bounded too: system prompt examples, the separate Claude system prompt guide, and the AI prompts collection cover reusable instruction formats when you need them.