Prompts to try with your AI assistant

Real requests that make your assistant plan your day, triage the inbox, run a project, write notes, make flashcards and track a budget in Prior.

Each request below uses several of Prior's tools in a row. Say it the way you would to a colleague, and name the project or the note you mean. Your assistant adapts, so treat the wording as a starting point.

To see how your assistant works, start with a request that only reads, such as "What is overdue?". When a recipe changes something, ask to see the plan first. Four of the five built-in prompts do it by default: see Every tool and prompt.

#Plan your day and week

Plan my day. I have 5 hours, and the quote for Maison Dubois must go out before 5 pm.

The assistant reads your day: overdue tasks, those due or planned today, your habits and your working hours. It proposes an order with a time for each task, and says what it would move to another day. After you agree, it writes the time on each task. It sees the calendars you made in Prior but not Google calendars, so mention those meetings yourself.

What is overdue? Propose new dates for what still matters and tell me which ones you would drop.

It lists the late tasks, groups them, proposes new dates and a short list to abandon. You decide which changes it applies.

Run my weekly review.

It reads the tasks you completed this week, what slipped, how your habits went, and proposes three priorities for next week and the changes that follow: dates to move, tasks to drop, tasks to add.

#Capture and sort

Go through my inbox and ask me about what is unclear.

It reads the tasks in your inbox and your projects, and shows a table with a project, a priority and, only when needed, a date for each. You answer its questions, and it updates the tasks and moves them to Next action.

Here are my notes from the call with the client: [paste]. Create the follow-up tasks in Website launch, assign the design ones to Léa, due next Friday.

It finds the project and its members, then creates the tasks in one batch, with assignees and a due date. Léa is notified of her tasks.

#Run a project

Create a project for the website launch on 15 January, with milestones and tasks small enough to do in one sitting.

It looks first for an existing project or area that fits. Then it proposes milestones, tasks, sub-tasks, priorities and durations, and creates everything in a single call once you agree.

Write a status update for Website launch: what is done, what is blocked, what is next. Save it as a note in the project.

It reads the project, its tasks and its activity, and writes a note. In a shared project the note is shared, so everyone sees it.

Plan the next sprint of Mobile app: pick about 30 story points from the backlog, oldest first, and put them in the sprint.

It reads the sprint and the backlog, picks tasks that add up, and moves them into the sprint. Scrum sprints are a Pro feature of the project owner.

Start a Planning Poker session with the tasks of Mobile app that have no estimate.

It opens a session with those tasks, and the project's members are told to join. Planning Poker is also a Pro feature of the owner.

#Notes and documents

Write the meeting notes in the shared note of Website launch, and create a task for each decision.

It adds the notes to the project's shared note with one small edit, so teammates reading it keep their place, then creates the tasks.

In my Pricing note, add a table comparing the three plans and a chart of the monthly revenue by plan.

It reads the note, adds a table and a chart as plain text, and shows the result. Tables and charts in Prior are text, so the assistant can write them.

Find every note that mentions the supplier "Nord Compagnie" and list what each says about delivery.

It searches your tasks and notes, opens the matches and summarizes them. It changes nothing.

#Learn

Turn this course into flashcards, one deck per chapter: [paste, file or URL].

The make_flashcards prompt does this. The assistant reads the card-writing guide, builds a pack with one sub-deck per chapter, writes the cards section by section, draws figures where the knowledge is visual, then checks the deck for gaps. In Claude Code, type /mcp__prior__make_flashcards.

My Biology exam is on 12 December. Set a study plan on the Biology pack, and tell me if some chapters have too few cards.

It sets the exam date as the pack's study plan, then reads each deck and compares the number of cards.

#Money

Add this quote to the budget of the Kitchen project: [paste]. Mark the first two lines as ordered.

It reads the quote, adds the lines with their prices, statuses and categories, and reports the new total. Amounts are handled in cents, so a price of 12.50 is stored as 1250.

What is still to buy in the Kitchen project, and how much of the envelope is left?

It reads the budget and answers with the totals. It changes nothing.

#Teams

What did I miss? Show the comments that mention me and mark them as read.

It lists the comments that mention you, with the tasks they are on, and marks them read once you have seen them.

Ask Léa for an update on the login task, in a comment, and mention her.

It finds the task and Léa in the project's members, and posts the comment as you. She is notified.

Invite sam@example.com to Website launch as an editor.

It checks the address with you, then sends the invitation. An email goes out, and Sam joins after confirming. Your plan limits how many people a project can hold.

#Habits and clean-up

Create a habit to stretch every weekday at 8:00, and check off reading for yesterday.

It creates the habit with its schedule, and checks off the other for the day you name.

Find the tasks that have no project, file them in the right project, and list the ones you are unsure about.

It reads your projects and tasks and proposes a project for each. It leaves the unsure ones to you.

#Write good requests

• Name things. "The Kitchen project", "the Pricing note" help more than "my project".
• Ask to see the plan first for anything that changes many items: "Show me what you would change before you do it."
• Work in batches when a list is long: "Do the first 20."
• Keep deletions and invitations on confirm. Your assistant should ask before it deletes or reaches other people: see Keep your connection safe.
• Tell it what it cannot see, such as Google calendar meetings or emails.

Updated 5 November 2026