Hire an AI weekly priorities and delegation planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• Your tasks in four boxes, your time split and what to drop, hand off or shrink
• Two polite refusals and a one-page agreement for each handoff
• A week built from your roles with the important work booked first
• A review of how the week went and one hour won back

How it does the job well

• Start from the user problem and the evidence for it, then the solution.
• Write decisions down with the reason and the options you rejected.
• Keep scope small enough to ship and learn. Name what is out of scope.
• Define how success will be measured before building.

Mistakes it avoids

• Treating opinions or one loud request as proven demand.
• Specs that skip edge cases, error states or dependencies.
• Roadmaps with dates but no owners or confidence levels.

What a good result looks like

An example, not your task: Your days fill with small urgent jobs and the big work never starts.

• Step 1: Urgent versus important sorter. Your tasks in four boxes, the real split of your hours, what to drop or hand off, and two polite refusals.
• Step 2: Results agreement writer. A one-page agreement for each handoff: the result, limits, help, review times and consequences.
• Step 3: Values-to-week planner. A week built from your roles, with the important work booked first and open space left for people.
• Step 4: Weekly time audit planner. What you chose against what took your time, and one hour won back for next week.
• Hand-back summary. Each step's file, any step not run and why, and every MISSING line in one list.

How the work is checked

• Each step passed its own checks, or the run stopped at the step that failed and says why.
• The steps ran in order, and each one used the result of the one before.
• Nothing was invented to fill a gap. Every gap is a MISSING: line.
• Nothing was sent, published or paid for without a clear yes.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Stephen Covey and Hamilton Helmer would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Urgent versus important sorter. Sorts each task by two questions, counts the hours in each box, traces crises to missing prevention and marks what to drop, hand off or shrink.
• Results agreement writer. Turns a handoff into one page on the result, limits, help, review dates and consequences, with no instructions on how to work.
• Values-to-week planner. Builds the week from your roles, books the important work first and leaves open space.
• Weekly time audit planner. After the week, counts what you chose against what took you and finds one hour to win back.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id weekly-priorities-plan only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/weekly-priorities-plan/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your task list or last week's calendar, with rough hours
• Your roles, goals or values (optional but helps)
• A job you could hand to someone, and who (optional)
• Next week's fixed meetings and duties
• On Friday, that week's calendar and your notes, for the review

Tools and access

• Claude, ChatGPT or Gemini: Sorting items and adding up hours is text work. No files, web access or paid tools needed.
• Your calendar app: Last week's real events give honest hours.
• Any good chat AI: Drafting and tightening a short agreement is text work any strong chat AI does well.
• A shared document: Both sides can read, edit and sign off the same page.
• Any good chat AI: Sorting a calendar into blocks and checks is text work any strong chat AI does well.
• Your calendar app: Put the blocks in as real events so they cannot be booked over.
• Any good chat AI: Sorting and adding up a list of blocks is plain text work.
• Your calendar app's export: A real export is faster and more honest than memory.

Functions and deliverables

• Weekly priorities and delegation planner: Share tasks, roles, available time and commitments. Get a priority sort, proposed handoffs, a weekly schedule and a review after the week.
  • Your tasks in four boxes, your time split and what to drop, hand off or shrink
  • Two polite refusals and a one-page agreement for each handoff
  • A week built from your roles with the important work booked first
  • A review of how the week went and one hour won back
• Urgent versus important sorter: Sort your task list into urgent and important boxes. See where your hours really go, and what to drop, hand off or protect.
  • Each item in one of four boxes, with hours
  • The share of your hours in each box, and what the pattern says
  • Each crisis traced back to the work that would have prevented it
  • A move for each low-value item: drop, hand off, batch or shrink
  • Two polite refusals and a brief for planning your week
• Work expectations agreement writer: Write a results agreement for a job you hand off or a deal you settle. You get one page on results, limits, help, review and what follows.
  • A one-page agreement with results, guidelines, resources, accountability and consequences
  • A choice of how much structure fits the person
  • An exit clause and a trust line for a two-sided deal
  • A say-it-back card of five lines
• Values-based weekly planner: Turn your roles, values and calendar into a values-based weekly plan with quarter goals, protected hours for hard work and set times for messages.
  • A short statement of your roles and values
  • Goals for the quarter and projects for the week
  • Protected hard-work blocks placed in your calendar
  • Message check times, a quiet-season idea and a plan for how to judge it
• Weekly time audit planner: Find where your week went. Paste last week's calendar and get your hours sorted into chosen, taken and habit, plus one protected hour a day.
  • Every block of last week, tagged as chosen, taken by others or taken by habit
  • Hours added up in each pile, with each pile's share of the week
  • Your three biggest takers, with what each cost you and who gains
  • One protected hour a day, tied to a named piece of work
  • Each old 'later' turned into a first step with a day and a time
• Product context file writer: Share product facts, audience and positioning. Get a reviewed context file that other marketing skills can reference.
  • A product marketing context file
  • A summary of what the file already holds
  • A change log of updates
  • Gaps you still need to fill
  Source: Corey Haines.
• Stephen Covey: Plan priorities, handoffs or a hard talk using Stephen Covey’s recorded approach. State the goal, listen first and agree a next step.
  • Your problem worked on the way Stephen Covey would: their questions, their method, their push-back
  • The answer or the work, in Stephen Covey's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Hamilton Helmer: Test a business advantage using Hamilton Helmer’s 7 Powers approach. Find the benefit, what stops rivals copying it and the next move to test.
  • Your problem worked on the way Hamilton Helmer would: their questions, their method, their push-back
  • The answer or the work, in Hamilton Helmer's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• Your days fill with small urgent jobs and the big work never starts.
• You are about to plan the week and want to know what to clear first.
• You want to hand off more but past handoffs came back wrong.

Limits to check before starting

• You have one fixed deadline or a one-off project: use a plain to-do list or the project plan for that job.
• You want to plan only a single day: write a short list of your top three jobs by hand.
• You have no task list and no idea of your roles: write down your jobs and goals first, then come back.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It's a zip with HANDOFF.md plus four skill files, in the order they run: Urgent versus important sorter, Results agreement writer, Values-to-week planner, Weekly time audit planner.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Paste your task list and say what matters to you. Guess your own split before you read the answer.
• Live the week with the plan in view. Note each time a loud job pulled you away.
• On Friday, run the last step with those notes and that week's calendar.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/weekly-priorities-plan for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.