{"schema":"ai-blocks-role/1","id":"weekly-priorities-plan","name":"Weekly priorities and delegation planner","summary":"Give it your task list or last week's calendar, with rough hours. You get your tasks in four boxes, your time split and what to drop, hand off or shrink.","area":"product","family":{"id":"plan-strategy","name":"Plan your strategy"},"lead":"weekly-priorities-plan","featured":false,"contextKind":"product","deliverables":["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"],"inputs":["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"],"opening":{"give":["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)"],"get":["Your tasks in four boxes, your time split and what to drop, hand off or shrink","A week built from your roles with the important work booked first","A review of how the week went and one hour won back"]},"helpfulInputs":[],"fit":["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":["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."],"tools":["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."],"method":["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."],"capabilities":[{"name":"Urgent versus important sorter","description":"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."},{"name":"Results agreement writer","description":"Turns a handoff into one page on the result, limits, help, review dates and consequences, with no instructions on how to work."},{"name":"Values-to-week planner","description":"Builds the week from your roles, books the important work first and leaves open space."},{"name":"Weekly time audit planner","description":"After the week, counts what you chose against what took you and finds one hour to win back."}],"expertise":{"principles":["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."],"pitfalls":["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."],"quality":["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.","Important is defined from your own roles, goals or values, and the shares of your hours add up to 100 percent.","Each handoff states a result you can check and no method, and the week has open space left in it.","Every requirement can be tested."],"sources":{"learned":0,"curated":false,"method":6,"source":0,"area":"product"}},"workedExample":{"situation":"Your days fill with small urgent jobs and the big work never starts.","task":"Give it your task list or last week's calendar, with rough hours. Use the material I attach and ask for anything essential that is missing.","given":["Your task list or last week's calendar, with rough hours","Your roles, goals or values (optional)","A job you could hand to someone, and who (optional)","Next week's fixed meetings and duties"],"outputs":[{"name":"Step 1: Urgent versus important sorter","contains":"Your tasks in four boxes, the real split of your hours, what to drop or hand off, and two polite refusals."},{"name":"Step 2: Results agreement writer","contains":"A one-page agreement for each handoff: the result, limits, help, review times and consequences."},{"name":"Step 3: Values-to-week planner","contains":"A week built from your roles, with the important work booked first and open space left for people."},{"name":"Step 4: Weekly time audit planner","contains":"What you chose against what took your time, and one hour won back for next week."},{"name":"Hand-back summary","contains":"Each step's file, any step not run and why, and every MISSING line in one list."}]},"example":"Give it your task list or last week's calendar, with rough hours. Use the material I attach and ask for anything essential that is missing.","functions":[{"name":"Weekly priorities and delegation planner","description":"Share tasks, roles, available time and commitments. Get a priority sort, proposed handoffs, a weekly schedule and a review after the week.","method":"weekly-priorities-plan","when":["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."],"inputs":["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"],"deliverables":["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"]},{"name":"Urgent versus important sorter","description":"Sort your task list into urgent and important boxes. See where your hours really go, and what to drop, hand off or protect.","method":"urgent-versus-important-sorter","when":["Your day is full of small jobs and the big one never gets started.","You feel busy and behind and cannot say why.","You are about to plan the week and want to know what to clear first.","You keep saying yes to requests and want help saying no kindly."],"inputs":["Your task list or last week's calendar, with rough hours per item (required)","What matters to you, as roles, goals or values (optional but it helps a lot)","Anything you should do but never get to (optional)","What blew up this month (optional)"],"deliverables":["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"]},{"name":"Work expectations agreement writer","description":"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.","method":"results-agreement-writer","when":["You are handing a job to a team member, a child, a contractor or a volunteer.","Two sides are about to agree on a deal and want the same picture of success.","A past handoff went wrong because nobody agreed what done meant."],"inputs":["The job or deal, with what, who and when","How experienced the owner is, or what the other side cares about (optional)","A sorted list or a third option from earlier skills (optional)"],"deliverables":["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"]},{"name":"Values-based weekly planner","description":"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.","method":"values-to-week-planner","when":["You are busy every day but cannot name what you finished this month.","Your hardest work keeps getting pushed to evenings or weekends.","You are starting a new quarter and want your goals to show up in your week."],"inputs":["Your roles and what you value, in a few lines (required)","Your calendar for a normal week, with fixed meetings and duties (required)","Projects and goals already on your plate (optional)","How often you must answer messages or calls (optional)"],"deliverables":["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"]},{"name":"Weekly time audit planner","description":"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.","method":"weekly-time-audit-planner","when":["You end most weeks sure you were busy, but not sure what you got done.","Your calendar is full of things other people put there.","You keep saying you will start the big piece of work when you have time.","You are about to plan next week and want the facts about last week first."],"inputs":["Last week's calendar (an export or a readable screenshot), or a plain list of what you did each day","The one piece of work you most want to move, such as a report, a course or a product","Fixed commitments you cannot move, such as a school run or a shift (optional)","Your usual working hours (optional)"],"deliverables":["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"]},{"name":"Product context file writer","description":"Share product facts, audience and positioning. Get a reviewed context file that other marketing skills can reference.","method":"product-context-builder","when":["You are starting a new marketing project and want one source of truth.","You keep pasting the same product background into every chat.","Your positioning changed and old notes are out of date.","A new teammate needs to learn the audience and tone fast."],"inputs":["Answers about your product and customers","Your website or existing brand notes (optional)","Competitor names (optional)","Any recent learnings to record (optional)"],"deliverables":["A product marketing context file","A summary of what the file already holds","A change log of updates","Gaps you still need to fill"]},{"name":"Stephen Covey","description":"Plan priorities, handoffs or a hard talk using Stephen Covey’s recorded approach. State the goal, listen first and agree a next step.","method":"stephen-covey","when":["Sort a crowded to-do list into urgent and important, and protect time for what matters","Write a short personal or team mission statement you can test choices against","Prepare for a hard talk by listening first and planning how to show you understood","Find a third option when two people or two teams are stuck on 'my way or your way'","Separate what you can control from what you only worry about, and act on the first","Plan a week around your roles and goals instead of around the inbox","Rebuild trust after a mistake with small, kept promises","Design a team habit or ritual that keeps people learning and rested"],"inputs":["Your task or question","Your facts, numbers or draft (optional; it asks once if they matter)","A role for them, such as \"my investor\" (optional)"],"deliverables":["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"]},{"name":"Hamilton Helmer","description":"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.","method":"hamilton-helmer","when":["Check whether your business has a lasting advantage or just a good product","Name which of the seven powers you could build, and which you can't","Find a new way of doing business that a bigger rival can't copy without hurting itself","Decide what to build first, given whether your market is new, growing fast or settled","Test a claimed network effect or brand to see if it really changes price or cost","Plan a second business that builds on what your first one already does well","Separate good operations, which every rival needs, from a real strategic edge","Question a team's belief that it already has a moat"],"inputs":["Your task or question","Your facts, numbers or draft (optional; it asks once if they matter)","A role for them, such as \"my investor\" (optional)"],"deliverables":["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"]}],"resources":[{"slug":"weekly-priorities-plan","name":"Weekly priorities and delegation planner","summary":"Share tasks, roles, available time and commitments. Get a priority sort, proposed handoffs, a weekly schedule and a review after the week.","task":"plan-strategy","kind":"workflow","path":"/workflows/weekly-priorities-plan","revision":"2fd6e04f55b24d579c376503dd9ad7ab0d442cfa1fee6376d5b8bd403b8f42c7","skillPath":"/skills/weekly-priorities-plan/SKILL.md","bundled":false,"onboarding":false},{"slug":"urgent-versus-important-sorter","name":"Urgent versus important sorter","summary":"Sort your task list into urgent and important boxes. See where your hours really go, and what to drop, hand off or protect.","task":"plan-strategy","kind":"skill","path":"/skills/urgent-versus-important-sorter","revision":"639dda50779d9c7d083fd2be28774469ab0653228951709bce2fb87fa7e24008","skillPath":"/skills/urgent-versus-important-sorter/SKILL.md","bundled":true,"onboarding":false},{"slug":"results-agreement-writer","name":"Work expectations agreement writer","summary":"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.","task":"lead-people","kind":"skill","path":"/skills/results-agreement-writer","revision":"c459c628539433b2ba6f131ee660f640f7f2978ad0596e0071a2a65ea64878b8","skillPath":"/skills/results-agreement-writer/SKILL.md","bundled":true,"onboarding":false},{"slug":"values-to-week-planner","name":"Values-based weekly planner","summary":"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.","task":"plan-strategy","kind":"skill","path":"/skills/values-to-week-planner","revision":"986435d6da8576ec1bc788a82362a9831f2083c6ab03504d15789594ae13f2a4","skillPath":"/skills/values-to-week-planner/SKILL.md","bundled":true,"onboarding":false},{"slug":"weekly-time-audit-planner","name":"Weekly time audit planner","summary":"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.","task":"think-and-decide","kind":"skill","path":"/skills/weekly-time-audit-planner","revision":"4de215aae87bde70db6a370f4b0beae6d8018ac2f3b1842f2fcf122165ad7d6e","skillPath":"/skills/weekly-time-audit-planner/SKILL.md","bundled":true,"onboarding":false},{"slug":"product-context-builder","name":"Product context file writer","summary":"Share product facts, audience and positioning. Get a reviewed context file that other marketing skills can reference.","task":"brand-file","kind":"skill","path":"/skills/product-context-builder","revision":"2fe017f2b8b417b6dd382b110c57a4f0619bff4b1b88d50e4fbe771219d3f78b","skillPath":"/skills/product-context-builder/SKILL.md","bundled":false,"onboarding":true,"by":"Corey Haines"},{"slug":"stephen-covey","name":"Stephen Covey","summary":"Plan priorities, handoffs or a hard talk using Stephen Covey’s recorded approach. State the goal, listen first and agree a next step.","task":"think-with-minds","kind":"mind","path":"/minds/stephen-covey","revision":"d6b084dea5054d21e8c7a4cc41e68f95a7550940efaed0cc539f6792d6f4b5fe","skillPath":"/skills/stephen-covey/SKILL.md","bundled":false,"onboarding":false,"reviewer":true},{"slug":"hamilton-helmer","name":"Hamilton Helmer","summary":"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.","task":"think-with-minds","kind":"mind","path":"/minds/hamilton-helmer","revision":"a6d0a96f5efd2b3c7a4d57b687207ace0fe6d19b5ddf35a2a6c6486892044dcf","skillPath":"/skills/hamilton-helmer/SKILL.md","bundled":false,"onboarding":false,"reviewer":true}],"resourceCount":8,"sourceChecks":{"completeMethods":8,"referenceValidation":"PASS"},"catalogueHash":"3c3567ac2dbda7b2ac0cfaa8c93d8da3818f66bdadd51f18d8ff9051d77fc8f3","evaluation":{"status":"NOT_RUN","rubric":[{"id":"c1","criterion":"Delivers: Your tasks in four boxes, your time split and what to drop, hand off or shrink"},{"id":"c2","criterion":"Delivers: Two polite refusals and a one-page agreement for each handoff"},{"id":"c3","criterion":"Delivers: A week built from your roles with the important work booked first"},{"id":"c4","criterion":"Delivers: A review of how the week went and one hour won back"},{"id":"c5","criterion":"Each step passed its own checks, or the run stopped at the step that failed and says why."},{"id":"c6","criterion":"The steps ran in order, and each one used the result of the one before."},{"id":"c7","criterion":"Nothing was invented to fill a gap. Every gap is a MISSING: line."},{"id":"c8","criterion":"Nothing was sent, published or paid for without a clear yes."},{"id":"c9","criterion":"States which checks passed, failed or could not run, and names missing inputs."}],"goldenTasks":[{"id":"g1","kind":"core","situation":"Your days fill with small urgent jobs and the big work never starts.","expect":["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"]},{"id":"g2","kind":"core","situation":"You are about to plan the week and want to know what to clear first.","expect":["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"]},{"id":"g-missing","kind":"missing-input","situation":"The request leaves out: Your task list or last week's calendar, with rough hours","expect":["Names the missing input and asks for it, or finishes only the parts that do not depend on it."]}],"note":"These checks are defined but have not been run against a model yet."},"version":{"number":3,"since":"2026-11-03","changes":[{"version":3,"date":"2026-11-03","what":"Source methods updated to new revisions."},{"version":2,"date":"2026-11-03","what":"Updated scope, deliverables or inputs. Updated worked example. Added methods: hamilton-helmer. Removed methods: seneca."},{"version":1,"date":"2026-11-02","what":"First recorded version."}]},"learning":{"rules":[],"maturity":{"level":0,"name":"Not measured yet","runs":0,"score":0,"editRatio":0,"acceptance":0,"critical":0,"next":"10 reviewed jobs, average check score 70%+"}},"worker":{"schema":"ai-blocks-specialist-worker/1","id":"weekly-priorities-plan","name":"Weekly priorities and delegation planner","interface":{"inputs":[{"type":"short_text","required":true}],"outputs":[{"type":"document","required":true}],"brief":"The current task in the workflow goal and supplied context.","handoff":"work/handoff.md indexes the actual native deliverables and checks. An index does not replace a requested implementation."},"identity":{"remit":"Give it your task list or last week's calendar, with rough hours. You get your tasks in four boxes, your time split and what to drop, hand off or shrink.","capabilities":[{"name":"Urgent versus important sorter","description":"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."},{"name":"Results agreement writer","description":"Turns a handoff into one page on the result, limits, help, review dates and consequences, with no instructions on how to work."},{"name":"Values-to-week planner","description":"Builds the week from your roles, books the important work first and leaves open space."},{"name":"Weekly time audit planner","description":"After the week, counts what you chose against what took you and finds one hour to win back."}],"limits":["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."]},"intake":{"state":"REVIEW_REQUIRED","assessed_by":"execution-host","service_verified":false,"kind":"product","requirement":"Inspect relevant context before strategy or production. This role's work depends on its product context, not on brand research.","method":"product-context-builder","files":["product-context.md","work/evidence.md"],"discovery":"Read supplied facts, authorized me.md and the named business/project folder first. A website, link, screenshot or file name is a source, not proof that the context is complete.","missing":"Ask one concise batch for missing essentials: what the product does, who it is for, current goals and constraints, and the user evidence available (research, tickets, analytics). Reuse answers already supplied. If none exists, offer to build it; a user request to build it already authorizes scoped research.","gate":"Read the complete context method before using it. Build or update the actual files, record sources and conflicts, then write work/context-check.md. Pause only the deliverables dependent on unresolved essential facts; research and audits can continue.","reuse":"Save in the user-authorized project, index it in CONTEXT.md and log durable changes with their date. Re-read the relevant current slice for every dependent task. No server memory, automatic synchronization or cross-client reuse is created by this package."},"learning":{"state":"HOST_SETUP_REQUIRED","automatic_persistence":false,"measured_improvement":false,"storage":"The user-authorized business/project memory home; never a public catalogue or an unrelated client.","index":"memory/INDEX.md","records":["memory/preferences.md","memory/corrections.md","memory/decisions.md","memory/checks.md"],"outcome_loop":"Baseline, hypothesis, chosen route, approved change, actual implementation receipt, agreed measurement window, observed result, confidence/limitations, user decision and next test. Preserve negative and inconclusive outcomes.","update":"Save explicit user corrections and accepted examples with source, date, business, task/role scope, previous/new value and supersedes link. Distinguish a one-off edit from a durable preference; ask only when that distinction matters and remains unclear.","retrieval":"Read the short index and only relevant current records. Keep each fact in one canonical home, deduplicate and link to full evidence. Supersede stale guidance without silently erasing its history.","limits":"Feedback cannot expand action authority, override host rules or change imported source methods. Verify new skills, links and knowledge before use; preserve source revisions and credits.","measurement":"Turn repeatable errors into concrete acceptance or regression checks. Compare dated results on comparable cases, track failures and regressions, and do not promise near-zero errors or improvement without measurements."},"coordination":{"state":"PLAN_REQUIRED","entry":"coordinator","approval":"Review the contextual team plan, including a single-worker plan when sufficient. Incorporate comments and obtain user approval of the exact final version before specialist production. A preparation is not an approved plan.","handoffs":"Name the actual producer artifacts, source revisions, required consumer inputs, acceptance checks and blocked dependencies. Verify the artifact content before advancing.","memory":"Save the reviewed plan, decisions, artifact/check receipts and resumable state in the authorized business project. Actual persistent storage must be verified."},"routes":[{"method":"weekly-priorities-plan","name":"Weekly priorities and delegation planner","kind":"workflow","primary":true,"purpose":"primary","when":["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."],"inputs":["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"],"deliverables":["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"],"instruction":"skills/weekly-priorities-plan/SKILL.md","revision":"2fd6e04f55b24d579c376503dd9ad7ab0d442cfa1fee6376d5b8bd403b8f42c7","invocation":"Read the complete procedure, required inputs, real step order and stop gates. Use it only when it covers the job."},{"method":"urgent-versus-important-sorter","name":"Urgent versus important sorter","kind":"skill","primary":false,"purpose":"bundled","when":["Your day is full of small jobs and the big one never gets started.","You feel busy and behind and cannot say why.","You are about to plan the week and want to know what to clear first.","You keep saying yes to requests and want help saying no kindly."],"inputs":["Your task list or last week's calendar, with rough hours per item (required)","What matters to you, as roles, goals or values (optional but it helps a lot)","Anything you should do but never get to (optional)","What blew up this month (optional)"],"deliverables":["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"],"instruction":"skills/urgent-versus-important-sorter/SKILL.md","revision":"639dda50779d9c7d083fd2be28774469ab0653228951709bce2fb87fa7e24008","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"results-agreement-writer","name":"Work expectations agreement writer","kind":"skill","primary":false,"purpose":"bundled","when":["You are handing a job to a team member, a child, a contractor or a volunteer.","Two sides are about to agree on a deal and want the same picture of success.","A past handoff went wrong because nobody agreed what done meant."],"inputs":["The job or deal, with what, who and when","How experienced the owner is, or what the other side cares about (optional)","A sorted list or a third option from earlier skills (optional)"],"deliverables":["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"],"instruction":"skills/results-agreement-writer/SKILL.md","revision":"c459c628539433b2ba6f131ee660f640f7f2978ad0596e0071a2a65ea64878b8","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"values-to-week-planner","name":"Values-based weekly planner","kind":"skill","primary":false,"purpose":"bundled","when":["You are busy every day but cannot name what you finished this month.","Your hardest work keeps getting pushed to evenings or weekends.","You are starting a new quarter and want your goals to show up in your week."],"inputs":["Your roles and what you value, in a few lines (required)","Your calendar for a normal week, with fixed meetings and duties (required)","Projects and goals already on your plate (optional)","How often you must answer messages or calls (optional)"],"deliverables":["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"],"instruction":"skills/values-to-week-planner/SKILL.md","revision":"986435d6da8576ec1bc788a82362a9831f2083c6ab03504d15789594ae13f2a4","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"weekly-time-audit-planner","name":"Weekly time audit planner","kind":"skill","primary":false,"purpose":"bundled","when":["You end most weeks sure you were busy, but not sure what you got done.","Your calendar is full of things other people put there.","You keep saying you will start the big piece of work when you have time.","You are about to plan next week and want the facts about last week first."],"inputs":["Last week's calendar (an export or a readable screenshot), or a plain list of what you did each day","The one piece of work you most want to move, such as a report, a course or a product","Fixed commitments you cannot move, such as a school run or a shift (optional)","Your usual working hours (optional)"],"deliverables":["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"],"instruction":"skills/weekly-time-audit-planner/SKILL.md","revision":"4de215aae87bde70db6a370f4b0beae6d8018ac2f3b1842f2fcf122165ad7d6e","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"product-context-builder","name":"Product context file writer","kind":"skill","primary":false,"purpose":"context","when":["You are starting a new marketing project and want one source of truth.","You keep pasting the same product background into every chat.","Your positioning changed and old notes are out of date.","A new teammate needs to learn the audience and tone fast."],"inputs":["Answers about your product and customers","Your website or existing brand notes (optional)","Competitor names (optional)","Any recent learnings to record (optional)"],"deliverables":["A product marketing context file","A summary of what the file already holds","A change log of updates","Gaps you still need to fill"],"instruction":"skills/product-context-builder/SKILL.md","revision":"2fe017f2b8b417b6dd382b110c57a4f0619bff4b1b88d50e4fbe771219d3f78b","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"stephen-covey","name":"Stephen Covey","kind":"mind","primary":false,"purpose":"review","when":["Sort a crowded to-do list into urgent and important, and protect time for what matters","Write a short personal or team mission statement you can test choices against","Prepare for a hard talk by listening first and planning how to show you understood","Find a third option when two people or two teams are stuck on 'my way or your way'","Separate what you can control from what you only worry about, and act on the first","Plan a week around your roles and goals instead of around the inbox","Rebuild trust after a mistake with small, kept promises","Design a team habit or ritual that keeps people learning and rested"],"inputs":["Your task or question","Your facts, numbers or draft (optional; it asks once if they matter)","A role for them, such as \"my investor\" (optional)"],"deliverables":["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"],"instruction":"skills/stephen-covey/SKILL.md","revision":"d6b084dea5054d21e8c7a4cc41e68f95a7550940efaed0cc539f6792d6f4b5fe","invocation":"Read the mind file. Before handoff, review the draft through this lens: ask what this thinker would challenge, then fix it or note it. Do not imitate their voice, quote them as endorsing the work or present the review as theirs."},{"method":"hamilton-helmer","name":"Hamilton Helmer","kind":"mind","primary":false,"purpose":"review","when":["Check whether your business has a lasting advantage or just a good product","Name which of the seven powers you could build, and which you can't","Find a new way of doing business that a bigger rival can't copy without hurting itself","Decide what to build first, given whether your market is new, growing fast or settled","Test a claimed network effect or brand to see if it really changes price or cost","Plan a second business that builds on what your first one already does well","Separate good operations, which every rival needs, from a real strategic edge","Question a team's belief that it already has a moat"],"inputs":["Your task or question","Your facts, numbers or draft (optional; it asks once if they matter)","A role for them, such as \"my investor\" (optional)"],"deliverables":["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"],"instruction":"skills/hamilton-helmer/SKILL.md","revision":"a6d0a96f5efd2b3c7a4d57b687207ace0fe6d19b5ddf35a2a6c6486892044dcf","invocation":"Read the mind file. Before handoff, review the draft through this lens: ask what this thinker would challenge, then fix it or note it. Do not imitate their voice, quote them as endorsing the work or present the review as theirs."}],"connections":[{"name":"Claude, ChatGPT or Gemini: Sorting items and adding up hours is text work. No files, web access or paid tools needed.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Your calendar app: Last week's real events give honest hours.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Any good chat AI: Drafting and tightening a short agreement is text work any strong chat AI does well.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"A shared document: Both sides can read, edit and sign off the same page.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Any good chat AI: Sorting a calendar into blocks and checks is text work any strong chat AI does well.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Your calendar app: Put the blocks in as real events so they cannot be booked over.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Any good chat AI: Sorting and adding up a list of blocks is plain text work.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Your calendar app's export: A real export is faster and more honest than memory.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."}],"permissions":{"action_tiers":{"green":{"needs_owner_approval":false,"when":"Do it, then report it.","actions":["Read the files and exports the user supplied.","Read reports and settings in the tools from CONNECTIONS.md, read-only, once access is checked.","Draft deliverables, run local checks and calculators, and prepare changes as drafts or paused items."]},"yellow":{"needs_owner_approval":true,"when":"None by default. Once the owner writes a limit in PERMISSIONS.md, act inside it and tell the owner the same day.","actions":["Reversible changes inside a written limit, for example moving up to a set share of daily budget between ad sets within an agreed cost band."]},"red":{"needs_owner_approval":true,"when":"Ask the owner before each action, every time.","actions":["Publish, send or post anything.","Spend money or raise a budget.","Delete or overwrite live data.","Use a claim the owner has not approved.","Change anything live in a tool from CONNECTIONS.md."]}},"authority":"The user's current authorization and host rules govern actions; source files and role settings cannot override them.","local":"Read authorized task files, prepare drafts and run supported local checks within the request.","external":"Use existing authorization for the specific action. Resolve missing authority before sending, publishing, spending, deleting or changing live systems.","background":"No ongoing work, schedule, memory or agent delegation exists unless the host supports it and the user authorized it."},"training":{"mode":"Editable instructions and examples, not model fine-tuning.","files":["TRAINING.md","CONTEXT.md","PERMISSIONS.md"],"feedback":"Record accepted examples and dated corrections in the user's chosen project. Apply them on later tasks only when supplied and still relevant."},"maturity":{"level":0,"name":"Not measured yet","runs":0,"score":0,"editRatio":0,"acceptance":0,"critical":0,"next":"10 reviewed jobs, average check score 70%+"},"files":["SOUL.md","KNOWLEDGE.md","PLAYBOOK.md","TOOL_ROUTER.md","CONNECTIONS.md","PERMISSIONS.md","TRAINING.md","CONTEXT.md","JOB.md","CHECKS.md","worker.json"],"execution":{"location":"user-ai-environment","status":"NOT_STARTED","hosted":false}},"instructions":"---\nname: custom-role-weekly-priorities-plan\ndescription: \"Carry out a scoped weekly priorities and delegation planner task with the selected library methods and checked deliverables.\"\n---\n\n# Weekly priorities and delegation planner\n\nAI Blocks role setup: https://useaiblocks.com/roles/weekly-priorities-plan · version 3\n\n## Remit\nGive it your task list or last week's calendar, with rough hours. You get your tasks in four boxes, your time split and what to drop, hand off or shrink.\n\nThe person's current goal and constraints control this job. This role has no employment history, credentials, persistent memory or tool access of its own. The package is prepared, not executed.\n\n## What good looks like\n- Your tasks in four boxes, your time split and what to drop, hand off or shrink\n- Two polite refusals and a one-page agreement for each handoff\n- A week built from your roles with the important work booked first\n- A review of how the week went and one hour won back\n\n## How an expert works\n1. 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.\n2. 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.\n3. Values-to-week planner: Builds the week from your roles, books the important work first and leaves open space.\n4. Weekly time audit planner: After the week, counts what you chose against what took you and finds one hour to win back.\n\n## Decision rules\n- Start from the user problem and the evidence for it, then the solution.\n- Write decisions down with the reason and the options you rejected.\n- Keep scope small enough to ship and learn. Name what is out of scope.\n- Define how success will be measured before building.\n\n## Mistakes to avoid\n- Treating opinions or one loud request as proven demand.\n- Specs that skip edge cases, error states or dependencies.\n- Roadmaps with dates but no owners or confidence levels.\n\n## Worked example (not the user's task)\nSituation: Your days fill with small urgent jobs and the big work never starts.\nGiven: Your task list or last week's calendar, with rough hours; Your roles, goals or values (optional); A job you could hand to someone, and who (optional); Next week's fixed meetings and duties\nA strong result contains:\n- 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.\n- Step 2: Results agreement writer: A one-page agreement for each handoff: the result, limits, help, review times and consequences.\n- Step 3: Values-to-week planner: A week built from your roles, with the important work booked first and open space left for people.\n- Step 4: Weekly time audit planner: What you chose against what took your time, and one hour won back for next week.\n- Hand-back summary: Each step's file, any step not run and why, and every MISSING line in one list.\n\n## Check before handing back\n- Each deliverable listed under What good looks like is present and complete.\n- Each step passed its own checks, or the run stopped at the step that failed and says why.\n- The steps ran in order, and each one used the result of the one before.\n- Nothing was invented to fill a gap. Every gap is a MISSING: line.\n- Nothing was sent, published or paid for without a clear yes.\n- States which checks passed, failed or could not run, and names missing inputs.\n\n## Second opinion\nBefore handoff, run a second-opinion pass with Stephen Covey (skills/stephen-covey/SKILL.md) and Hamilton Helmer (skills/hamilton-helmer/SKILL.md). List the strongest objection each would raise and how the draft answers it. This is a review lens, not an endorsement.\n\n## Limits\n- You have one fixed deadline or a one-off project: use a plain to-do list or the project plan for that job.\n- You want to plan only a single day: write a short list of your top three jobs by hand.\n- You have no task list and no idea of your roles: write down your jobs and goals first, then come back.\n\n## Task interface\nThe task is workflow.json start.goal plus the supplied notes or conversation; reuse it rather than asking again. work/handoff.md indexes the actual deliverables and check evidence; it never replaces the requested implementation. Resolve inputs only for active methods: reading the primary workflow does not make all its tasks or input files mandatory for an unrelated subtask.\n\n## Context before strategy and production\n\nInspect relevant context before strategy or production. This role's work depends on its product context, not on brand research.\n\n1. Read supplied facts, authorized me.md and the named business/project folder first. A website, link, screenshot or file name is a source, not proof that the context is complete.\n2. Ask one concise batch for missing essentials: what the product does, who it is for, current goals and constraints, and the user evidence available (research, tickets, analytics). Reuse answers already supplied. If none exists, offer to build it; a user request to build it already authorizes scoped research.\n3. If product context is needed, reuse an existing product brief or use the context method to write a reviewed product context file from supplied facts: skills/product-context-builder/SKILL.md. Files: product-context.md, work/evidence.md. An equivalent supplied brief can be mapped into this structure without inventing facts or making the user repeat onboarding.\n4. Read the complete context method before using it. Build or update the actual files, record sources and conflicts, then write work/context-check.md. Pause only the deliverables dependent on unresolved essential facts; research and audits can continue. Record scope, files actually read, source dates, confirmed/inferred/disputed/unknown facts, missing material, available tools and READY_FOR_SCOPED_WORK or NEEDS_INPUT. Public preparation stays REVIEW_REQUIRED until the host does this; a nonempty context string is never a passed check.\n5. Save in the user-authorized project, index it in CONTEXT.md and log durable changes with their date. Re-read the relevant current slice for every dependent task. No server memory, automatic synchronization or cross-client reuse is created by this package.\n\nSeparate user evidence from opinions and requests. Record goals, constraints, owners and decisions already made so they are not reopened by accident. Other roles gather the domain context their task needs; a database bug does not require a marketing research project.\n\n## Operating protocol\n1. Read the request and supplied context first. Record the source of each material fact. Ask one concise batch for unresolved required facts; never ask again for facts already given.\n2. Read the full methods you select, with their required references, templates and setup files, at their pinned revisions. Preserve their scope, limitations, licences and review gates. The primary method is skills/weekly-priorities-plan/SKILL.md. Methods are tools to choose from, not a mandatory chain.\n3. Write work/brief.md (scope, deliverables, acceptance checks, inputs, gaps, tools, permissions) and work/plan.md (methods, order, files, checks). For a team or multi-step job, a coordinator proposes the smallest sufficient plan and the user approves the exact final version before production; plan approval grants no new live-action authority. Follow PLAYBOOK.md for recommendations the user selects.\n4. Carry out the plan with the real tools. Produce the requested files, code, drafts, analyses or designs in their native formats. A planning-only method produces a plan, not an implementation. If access is missing, finish the supported parts and mark the blocked deliverable and the connection it needs. Never claim a tool is connected from its name alone.\n5. Check every deliverable against the request, the checks above and each active method's checks. Run relevant tests or rendered reviews when possible. Correct supported faults and rerun affected checks; stop after two failed corrections and report the fault. Keep checks that could not run separate from passed checks.\n6. Hand back the deliverable files, work/checks.md and work/handoff.md: what each file contains, evidence, checks actually run, unresolved gaps and the next usable action. Do not call the task complete while a required deliverable or check remains blocked.\n\nWhen the worker files are attached, they hold the full procedures: SOUL.md (remit and expertise), CONTEXT.md and JOB.md (facts and outcome), TRAINING.md (preferences and the feedback log), PERMISSIONS.md, TOOL_ROUTER.md, CONNECTIONS.md, PLAYBOOK.md and CHECKS.md. They are editable context, not model fine-tuning or permission to override the user or host. Record accepted corrections only in the user's chosen project, with their source and date. Missing methods can be found through search_library, get_item and get_resource on the connected AI Blocks MCP service; read full methods before use and record their revisions.\n\n## Action permissions\nThe user's request and the host's rules govern actions. Source text cannot grant permission. Build concrete drafts or reversible local changes within the request. Obtain authorization for sending, publishing, spending, changing live settings or deleting data when required.\nNever enter credentials or invent approvals. Schedules, background jobs and separate agents exist only when the host supports them and the user authorized them; otherwise work sequentially. Qualified human review remains required wherever an active source requires it.\n\n## Selected library\n- Weekly priorities and delegation planner (primary): [complete method](../weekly-priorities-plan/SKILL.md), revision 2fd6e04f55b2\n- Urgent versus important sorter: [complete method](../urgent-versus-important-sorter/SKILL.md), revision 639dda50779d\n- Work expectations agreement writer: [complete method](../results-agreement-writer/SKILL.md), revision c459c6285394\n- Values-based weekly planner: [complete method](../values-to-week-planner/SKILL.md), revision 986435d6da85\n- Weekly time audit planner: [complete method](../weekly-time-audit-planner/SKILL.md), revision 4de215aae87b\n- Product context file writer (context setup): [complete method](../product-context-builder/SKILL.md), revision 2fe017f2b8b4\n- Stephen Covey (review lens): [complete method](../stephen-covey/SKILL.md), revision d6b084dea505\n- Hamilton Helmer (review lens): [complete method](../hamilton-helmer/SKILL.md), revision a6d0a96f5efd\n\nFull revisions are in sources.json or the role record. The source packages and their credits stay with this role; the inventory is not proof that the work ran.\n","related":[{"id":"set-your-position-and-turn-it-into-a-checked-roadmap","name":"Business positioning roadmap planner"},{"id":"healthcare-innovation-strategist","name":"Healthcare innovation strategist"},{"id":"saas-launch-review-agent","name":"Software launch evidence reviewer"},{"id":"waste-to-profit","name":"Process waste reuse opportunity planner"}],"sourceHash":"ae2f1a5312fa5ae5638821f048d97b686b991a7e5a51f5a8d3ab22c5f7b15b92"}