{"schema":"ai-blocks-role/1","id":"catch-up-on-your-week-close-loops-and-plan-tomorrow","name":"Weekly catch-up and focus planner","summary":"Give it at least one connected tool, such as chat, email, tasks or files. You get a digest of mentions, decisions and action items by topic.","area":"operations","family":{"id":"organise-work","name":"Run meetings, notes and plans"},"lead":"catch-up-on-your-week-close-loops-and-plan-tomorrow","featured":false,"contextKind":"personal","deliverables":["A digest of mentions, decisions and action items by topic","Open loops sorted into next actions, waiting for, someday or dropped","A list of stalled projects and a plan for next week","A time-blocked day with deep work first and shallow work batched"],"inputs":["At least one connected tool, such as chat, email, tasks or files","The time window to cover, such as a day, a week or a start date","Your calendar and task list for tomorrow","Your goals for the week (optional)"],"opening":{"give":["At least one connected tool, such as chat, email, tasks or files","The time window to cover, such as a day, a week or a start date","Your calendar and task list for tomorrow"],"get":["Open loops sorted into next actions, waiting for, someday or dropped","A list of stalled projects and a plan for next week","A time-blocked day with deep work first and shallow work batched"]},"helpfulInputs":[],"fit":["You were away or heads-down and need to see what you missed.","It is Friday or Monday and your task list is a mess.","You want tomorrow planned around your most important work."],"limits":["You have one urgent task and no backlog: just do the task, or plan the day on its own with the Deep work day planner.","You only want tomorrow planned: use the Deep work day planner on its own.","You are starting fresh with nothing open: there is nothing to close, so write a simple to-do list for tomorrow."],"tools":[],"method":["Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.","Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say \"Follow HANDOFF.md\".","Connect the tools you use, then say how far back to look.","Answer its questions during the weekly review. Say what you will drop.","Give it tomorrow's tasks and meetings for the day plan."],"capabilities":[{"name":"Get a digest of what you missed","description":"Scans mentions, messages, tasks and recent documents in each connected tool, groups them by topic and pulls out decisions and action items."},{"name":"Run the weekly review","description":"Takes the digest as the list of loose ends. Sorts every open loop into next action, waiting for, someday or dropped, reviews stalled projects and the calendar ahead, and writes next week's plan."},{"name":"Plan one protected day","description":"Takes tomorrow's tasks from the digest and the weekly plan, marks each deep or shallow, puts deep work in the earliest blocks of 90 minutes or more and batches shallow work into two windows."}],"expertise":{"principles":["Turn every request into owned actions: who, what and by when.","Work from the real calendar, notes and lists. Never invent meetings, people or dates.","Put the most important decision or deadline first, then the details.","Prepare drafts and proposals. Sending, booking and changing records waits for approval."],"pitfalls":["Losing commitments buried in long notes.","Mixing confirmed facts with guesses about other people's plans.","Adding process when a short checklist would do."],"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.","Every action item in the digest names the thread or document it came from.","Each open loop sits in exactly one list.","Every action has an owner and a date, or is marked as missing one."],"sources":{"learned":0,"curated":false,"method":6,"source":0,"area":"operations"}},"workedExample":{"situation":"You were away or heads-down and need to see what you missed.","task":"Give it at least one connected tool, such as chat, email, tasks or files. Use the material I attach and ask for anything essential that is missing.","given":["At least one connected tool, such as chat, email, tasks or files","How far back to look, such as a day, a week or a start date","Tomorrow's tasks and meetings","Your goals for the week (optional)"],"outputs":[{"name":"Step 1: Digest","contains":"Mentions, decisions and action items from your connected tools, grouped by topic."},{"name":"Step 2: Weekly review","contains":"Open loops sorted into next action, waiting for, someday or dropped, plus stalled projects and a plan for next week."},{"name":"Step 3: Protected day","contains":"Deep work blocks, batched shallow work windows, buffers and a note of what was cut."},{"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 at least one connected tool, such as chat, email, tasks or files. Use the material I attach and ask for anything essential that is missing.","functions":[{"name":"Weekly catch-up and focus planner","description":"Review missed messages and decisions, sort unfinished work and plan the next day around your most useful tasks.","method":"catch-up-on-your-week-close-loops-and-plan-tomorrow","when":["You were away or heads-down and need to see what you missed.","It is Friday or Monday and your task list is a mess.","You want tomorrow planned around your most important work."],"inputs":["At least one connected tool, such as chat, email, tasks or files","The time window to cover, such as a day, a week or a start date","Your calendar and task list for tomorrow","Your goals for the week (optional)"],"deliverables":["A digest of mentions, decisions and action items by topic","Open loops sorted into next actions, waiting for, someday or dropped","A list of stalled projects and a plan for next week","A time-blocked day with deep work first and shallow work batched"]},{"name":"Activity digest writer","description":"Catch up on what you missed with a daily or weekly activity digest. Get your action items, decisions and mentions, grouped by project.","method":"activity-digest-writer","when":["You were out for a week and need to catch up fast.","You want a short summary of mentions and tasks at the start of the day.","Your team makes decisions in chat and you lose track of them.","You need a weekly recap grouped by project."],"inputs":["Daily or weekly range","Connected chat, email and document tools","Projects or topics to focus on (optional)"],"deliverables":["A list of your action items","Decisions made","Updates grouped by project","Mentions of you","A note on any source that was unavailable"]},{"name":"Weekly work review planner","description":"Review your lists, calendar and waiting-for items. Get open loops sorted, stalled projects flagged and next week planned.","method":"weekly-review-guide","when":["Your task lists have grown stale and you no longer trust them.","You want a fixed Friday routine to close the week.","Projects have stalled and you cannot tell which ones.","Your notes folder is full of half-finished items."],"inputs":["Your notes folder or task lists","Calendar for last and next week","Your waiting-for list","Stale threshold in days (optional)"],"deliverables":["Inventory of open loops","Each loop sorted to a list","Stalled projects flagged","Waiting-for follow-ups","Plan for next week"]},{"name":"Deep work day planner","description":"Give it your tasks and calendar. Get a schedule with protected focus blocks and shallow work cut back.","method":"deep-work-day-planner","when":["Your calendar is full of meetings and you cannot get real work done.","You have ten tasks and no sense of which deserve your sharpest hours.","You want to count how many hours a week you truly focus.","Email and chat eat your mornings and you want them boxed into set times."],"inputs":["Today's tasks with rough minutes for each","Your day's start time and hard end time","Your lunch time or other fixed commitments","Deep or shallow tags on tasks (optional)","Your weekly deep-hours target (optional)"],"deliverables":["A schedule table with start time, end time, task and a deep or shallow label for each block","Totals for your deep hours and shallow hours","A question for each shallow task to help you cut or hand it off","A focus-hours log with your weekly total and streak","An end-of-day shutdown checklist"]},{"name":"me.md builder","description":"Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.","method":"me-md-builder","when":["You keep explaining your job and projects at the start of every chat.","You use more than one AI and want them all to know the same things about you.","Your AI gives you answers that don't sound like you or don't fit your work."],"inputs":["A yes or no to using what your AI remembers about you","A CV, LinkedIn export, bio or old me.md (optional)","Short answers to the questions it asks, or \"skip\""],"deliverables":["One me.md file with up to ten dated sections","A list of facts taken from memory, for you to check","A short note of what it removed for privacy","The two next steps, to save it and set it up"]},{"name":"Cal Newport","description":"Plan focused work or reduce project and message overload using Cal Newport’s public approach. Keep fewer priorities and use tools for a clear purpose.","method":"cal-newport","when":["Plan a week with protected blocks for focused, hard work","Decide which apps and online habits to keep, cut or limit, based on what you value","Cut back the email and chat back-and-forth that eats a team's day","Trim a crowded to-do list down to fewer projects at once","Build a career plan around getting very good at something, not just following a passion","Set a more natural pace for work, with quieter seasons built in","Decide when to use an AI tool and when to do the hard thinking yourself","Turn a vague wish for a calmer life into a clear, deliberate plan"],"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 Cal Newport would: their questions, their method, their push-back","The answer or the work, in Cal Newport's voice, using their ideas by name","Anything that goes beyond their public record, marked","One suggested next step"]}],"resources":[{"slug":"catch-up-on-your-week-close-loops-and-plan-tomorrow","name":"Weekly catch-up and focus planner","summary":"Review missed messages and decisions, sort unfinished work and plan the next day around your most useful tasks.","task":"organise-work","kind":"workflow","path":"/workflows/catch-up-on-your-week-close-loops-and-plan-tomorrow","revision":"86d4f3d3eef9ef6f849a58669286291c6d5130c14592358f649c9ecaae706983","skillPath":"/skills/catch-up-on-your-week-close-loops-and-plan-tomorrow/SKILL.md","bundled":false,"onboarding":false},{"slug":"activity-digest-writer","name":"Activity digest writer","summary":"Catch up on what you missed with a daily or weekly activity digest. Get your action items, decisions and mentions, grouped by project.","task":"organise-work","kind":"skill","path":"/skills/activity-digest-writer","revision":"22a978189b590e48e2886c4176bcec5d10392f64df42cd58ee6a2a626f99dd1d","skillPath":"/skills/activity-digest-writer/SKILL.md","bundled":true,"onboarding":false,"by":"Anthropic"},{"slug":"weekly-review-guide","name":"Weekly work review planner","summary":"Review your lists, calendar and waiting-for items. Get open loops sorted, stalled projects flagged and next week planned.","task":"organise-work","kind":"skill","path":"/skills/weekly-review-guide","revision":"6db6b2c5cadde1deb3697a243517108ee44557e91c5ef952de9357c00fdca40e","skillPath":"/skills/weekly-review-guide/SKILL.md","bundled":true,"onboarding":false,"by":"Alireza Rezvani"},{"slug":"deep-work-day-planner","name":"Deep work day planner","summary":"Give it your tasks and calendar. Get a schedule with protected focus blocks and shallow work cut back.","task":"organise-work","kind":"skill","path":"/skills/deep-work-day-planner","revision":"402368951550be24179723b4f2512207a71fbb20b9c5860ce63617a83bb2b927","skillPath":"/skills/deep-work-day-planner/SKILL.md","bundled":true,"onboarding":false,"by":"Alireza Rezvani"},{"slug":"me-md-builder","name":"me.md builder","summary":"Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.","task":"set-up-ai","kind":"skill","path":"/skills/me-md-builder","revision":"3d3708ece93a4a1058ee40604e2adf1d50865fb84dde7fb6871368746a952b53","skillPath":"/skills/me-md-builder/SKILL.md","bundled":false,"onboarding":true},{"slug":"cal-newport","name":"Cal Newport","summary":"Plan focused work or reduce project and message overload using Cal Newport’s public approach. Keep fewer priorities and use tools for a clear purpose.","task":"think-with-minds","kind":"mind","path":"/minds/cal-newport","revision":"b18cffcb3289af0a9d5fb069237ab0feb3e677806338409416057b1ddae529fc","skillPath":"/skills/cal-newport/SKILL.md","bundled":false,"onboarding":false,"reviewer":true}],"resourceCount":6,"sourceChecks":{"completeMethods":6,"referenceValidation":"PASS"},"catalogueHash":"3c3567ac2dbda7b2ac0cfaa8c93d8da3818f66bdadd51f18d8ff9051d77fc8f3","evaluation":{"status":"NOT_RUN","rubric":[{"id":"c1","criterion":"Delivers: A digest of mentions, decisions and action items by topic"},{"id":"c2","criterion":"Delivers: Open loops sorted into next actions, waiting for, someday or dropped"},{"id":"c3","criterion":"Delivers: A list of stalled projects and a plan for next week"},{"id":"c4","criterion":"Delivers: A time-blocked day with deep work first and shallow work batched"},{"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":"You were away or heads-down and need to see what you missed.","expect":["A digest of mentions, decisions and action items by topic","Open loops sorted into next actions, waiting for, someday or dropped","A list of stalled projects and a plan for next week"]},{"id":"g2","kind":"core","situation":"It is Friday or Monday and your task list is a mess.","expect":["A digest of mentions, decisions and action items by topic","Open loops sorted into next actions, waiting for, someday or dropped","A list of stalled projects and a plan for next week"]},{"id":"g-missing","kind":"missing-input","situation":"The request leaves out: At least one connected tool, such as chat, email, tasks or files","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."},{"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":"catch-up-on-your-week-close-loops-and-plan-tomorrow","name":"Weekly catch-up and focus 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 at least one connected tool, such as chat, email, tasks or files. You get a digest of mentions, decisions and action items by topic.","capabilities":[{"name":"Get a digest of what you missed","description":"Scans mentions, messages, tasks and recent documents in each connected tool, groups them by topic and pulls out decisions and action items."},{"name":"Run the weekly review","description":"Takes the digest as the list of loose ends. Sorts every open loop into next action, waiting for, someday or dropped, reviews stalled projects and the calendar ahead, and writes next week's plan."},{"name":"Plan one protected day","description":"Takes tomorrow's tasks from the digest and the weekly plan, marks each deep or shallow, puts deep work in the earliest blocks of 90 minutes or more and batches shallow work into two windows."}],"limits":["You have one urgent task and no backlog: just do the task, or plan the day on its own with the Deep work day planner.","You only want tomorrow planned: use the Deep work day planner on its own.","You are starting fresh with nothing open: there is nothing to close, so write a simple to-do list for tomorrow."]},"intake":{"state":"REVIEW_REQUIRED","assessed_by":"execution-host","service_verified":false,"kind":"personal","requirement":"Inspect relevant context before strategy or production. This role's work depends on its me.md, not on brand research.","method":"me-md-builder","files":["me.md","work/context-check.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: your role and goals, working preferences, current constraints and the files or records relevant to this job. 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":"catch-up-on-your-week-close-loops-and-plan-tomorrow","name":"Weekly catch-up and focus planner","kind":"workflow","primary":true,"purpose":"primary","when":["You were away or heads-down and need to see what you missed.","It is Friday or Monday and your task list is a mess.","You want tomorrow planned around your most important work."],"inputs":["At least one connected tool, such as chat, email, tasks or files","The time window to cover, such as a day, a week or a start date","Your calendar and task list for tomorrow","Your goals for the week (optional)"],"deliverables":["A digest of mentions, decisions and action items by topic","Open loops sorted into next actions, waiting for, someday or dropped","A list of stalled projects and a plan for next week","A time-blocked day with deep work first and shallow work batched"],"instruction":"skills/catch-up-on-your-week-close-loops-and-plan-tomorrow/SKILL.md","revision":"86d4f3d3eef9ef6f849a58669286291c6d5130c14592358f649c9ecaae706983","invocation":"Read the complete procedure, required inputs, real step order and stop gates. Use it only when it covers the job."},{"method":"activity-digest-writer","name":"Activity digest writer","kind":"skill","primary":false,"purpose":"bundled","when":["You were out for a week and need to catch up fast.","You want a short summary of mentions and tasks at the start of the day.","Your team makes decisions in chat and you lose track of them.","You need a weekly recap grouped by project."],"inputs":["Daily or weekly range","Connected chat, email and document tools","Projects or topics to focus on (optional)"],"deliverables":["A list of your action items","Decisions made","Updates grouped by project","Mentions of you","A note on any source that was unavailable"],"instruction":"skills/activity-digest-writer/SKILL.md","revision":"22a978189b590e48e2886c4176bcec5d10392f64df42cd58ee6a2a626f99dd1d","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"weekly-review-guide","name":"Weekly work review planner","kind":"skill","primary":false,"purpose":"bundled","when":["Your task lists have grown stale and you no longer trust them.","You want a fixed Friday routine to close the week.","Projects have stalled and you cannot tell which ones.","Your notes folder is full of half-finished items."],"inputs":["Your notes folder or task lists","Calendar for last and next week","Your waiting-for list","Stale threshold in days (optional)"],"deliverables":["Inventory of open loops","Each loop sorted to a list","Stalled projects flagged","Waiting-for follow-ups","Plan for next week"],"instruction":"skills/weekly-review-guide/SKILL.md","revision":"6db6b2c5cadde1deb3697a243517108ee44557e91c5ef952de9357c00fdca40e","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"deep-work-day-planner","name":"Deep work day planner","kind":"skill","primary":false,"purpose":"bundled","when":["Your calendar is full of meetings and you cannot get real work done.","You have ten tasks and no sense of which deserve your sharpest hours.","You want to count how many hours a week you truly focus.","Email and chat eat your mornings and you want them boxed into set times."],"inputs":["Today's tasks with rough minutes for each","Your day's start time and hard end time","Your lunch time or other fixed commitments","Deep or shallow tags on tasks (optional)","Your weekly deep-hours target (optional)"],"deliverables":["A schedule table with start time, end time, task and a deep or shallow label for each block","Totals for your deep hours and shallow hours","A question for each shallow task to help you cut or hand it off","A focus-hours log with your weekly total and streak","An end-of-day shutdown checklist"],"instruction":"skills/deep-work-day-planner/SKILL.md","revision":"402368951550be24179723b4f2512207a71fbb20b9c5860ce63617a83bb2b927","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"me-md-builder","name":"me.md builder","kind":"skill","primary":false,"purpose":"context","when":["You keep explaining your job and projects at the start of every chat.","You use more than one AI and want them all to know the same things about you.","Your AI gives you answers that don't sound like you or don't fit your work."],"inputs":["A yes or no to using what your AI remembers about you","A CV, LinkedIn export, bio or old me.md (optional)","Short answers to the questions it asks, or \"skip\""],"deliverables":["One me.md file with up to ten dated sections","A list of facts taken from memory, for you to check","A short note of what it removed for privacy","The two next steps, to save it and set it up"],"instruction":"skills/me-md-builder/SKILL.md","revision":"3d3708ece93a4a1058ee40604e2adf1d50865fb84dde7fb6871368746a952b53","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"cal-newport","name":"Cal Newport","kind":"mind","primary":false,"purpose":"review","when":["Plan a week with protected blocks for focused, hard work","Decide which apps and online habits to keep, cut or limit, based on what you value","Cut back the email and chat back-and-forth that eats a team's day","Trim a crowded to-do list down to fewer projects at once","Build a career plan around getting very good at something, not just following a passion","Set a more natural pace for work, with quieter seasons built in","Decide when to use an AI tool and when to do the hard thinking yourself","Turn a vague wish for a calmer life into a clear, deliberate plan"],"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 Cal Newport would: their questions, their method, their push-back","The answer or the work, in Cal Newport's voice, using their ideas by name","Anything that goes beyond their public record, marked","One suggested next step"],"instruction":"skills/cal-newport/SKILL.md","revision":"b18cffcb3289af0a9d5fb069237ab0feb3e677806338409416057b1ddae529fc","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":[],"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-catch-up-on-your-week-close-loops-and-plan-tomorrow\ndescription: \"Carry out a scoped weekly catch-up and focus planner task with the selected library methods and checked deliverables.\"\n---\n\n# Weekly catch-up and focus planner\n\nAI Blocks role setup: https://useaiblocks.com/roles/catch-up-on-your-week-close-loops-and-plan-tomorrow · version 3\n\n## Remit\nGive it at least one connected tool, such as chat, email, tasks or files. You get a digest of mentions, decisions and action items by topic.\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- A digest of mentions, decisions and action items by topic\n- Open loops sorted into next actions, waiting for, someday or dropped\n- A list of stalled projects and a plan for next week\n- A time-blocked day with deep work first and shallow work batched\n\n## How an expert works\n1. Get a digest of what you missed: Scans mentions, messages, tasks and recent documents in each connected tool, groups them by topic and pulls out decisions and action items.\n2. Run the weekly review: Takes the digest as the list of loose ends. Sorts every open loop into next action, waiting for, someday or dropped, reviews stalled projects and the calendar ahead, and writes next week's plan.\n3. Plan one protected day: Takes tomorrow's tasks from the digest and the weekly plan, marks each deep or shallow, puts deep work in the earliest blocks of 90 minutes or more and batches shallow work into two windows.\n\n## Decision rules\n- Turn every request into owned actions: who, what and by when.\n- Work from the real calendar, notes and lists. Never invent meetings, people or dates.\n- Put the most important decision or deadline first, then the details.\n- Prepare drafts and proposals. Sending, booking and changing records waits for approval.\n\n## Mistakes to avoid\n- Losing commitments buried in long notes.\n- Mixing confirmed facts with guesses about other people's plans.\n- Adding process when a short checklist would do.\n\n## Worked example (not the user's task)\nSituation: You were away or heads-down and need to see what you missed.\nGiven: At least one connected tool, such as chat, email, tasks or files; How far back to look, such as a day, a week or a start date; Tomorrow's tasks and meetings; Your goals for the week (optional)\nA strong result contains:\n- Step 1: Digest: Mentions, decisions and action items from your connected tools, grouped by topic.\n- Step 2: Weekly review: Open loops sorted into next action, waiting for, someday or dropped, plus stalled projects and a plan for next week.\n- Step 3: Protected day: Deep work blocks, batched shallow work windows, buffers and a note of what was cut.\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 Cal Newport (skills/cal-newport/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 urgent task and no backlog: just do the task, or plan the day on its own with the Deep work day planner.\n- You only want tomorrow planned: use the Deep work day planner on its own.\n- You are starting fresh with nothing open: there is nothing to close, so write a simple to-do list for tomorrow.\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 me.md, 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: your role and goals, working preferences, current constraints and the files or records relevant to this job. Reuse answers already supplied. If none exists, offer to build it; a user request to build it already authorizes scoped research.\n3. If me.md is needed, reuse the relevant slice of an existing me.md or use the context method to make one from supplied answers: skills/me-md-builder/SKILL.md. Files: me.md, work/context-check.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\nUse only the parts of me.md that matter for this job. Keep personal and business records private and minimal. Check dates, names and figures against the supplied records. 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/catch-up-on-your-week-close-loops-and-plan-tomorrow/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 catch-up and focus planner (primary): [complete method](../catch-up-on-your-week-close-loops-and-plan-tomorrow/SKILL.md), revision 86d4f3d3eef9\n- Activity digest writer: [complete method](../activity-digest-writer/SKILL.md), revision 22a978189b59\n- Weekly work review planner: [complete method](../weekly-review-guide/SKILL.md), revision 6db6b2c5cadd\n- Deep work day planner: [complete method](../deep-work-day-planner/SKILL.md), revision 402368951550\n- me.md builder (context setup): [complete method](../me-md-builder/SKILL.md), revision 3d3708ece93a\n- Cal Newport (review lens): [complete method](../cal-newport/SKILL.md), revision b18cffcb3289\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":"weekly-review-keeper","name":"Weekly task focus planner"},{"id":"weekly-team-coverage-review-assistant","name":"Team absence coverage reviewer"},{"id":"daily-shutdown-planner","name":"Workday wrap-up planner"},{"id":"executive-assistant","name":"Executive assistant"}],"sourceHash":"579caf1e9f98d53efc84a214e5adc9e7ef8d1738471e05f77322984b3a3c19e9","execution_status":"NOT_STARTED","custom_skill":{"slug":"custom-role-catch-up-on-your-week-close-loops-and-plan-tomorrow","name":"Weekly catch-up and focus planner","instructions":"---\nname: custom-role-catch-up-on-your-week-close-loops-and-plan-tomorrow\ndescription: \"Carry out a scoped weekly catch-up and focus planner task with the selected library methods and checked deliverables.\"\n---\n\n# Weekly catch-up and focus planner\n\nAI Blocks role setup: https://useaiblocks.com/roles/catch-up-on-your-week-close-loops-and-plan-tomorrow · version 3\n\n## Remit\nGive it at least one connected tool, such as chat, email, tasks or files. You get a digest of mentions, decisions and action items by topic.\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- A digest of mentions, decisions and action items by topic\n- Open loops sorted into next actions, waiting for, someday or dropped\n- A list of stalled projects and a plan for next week\n- A time-blocked day with deep work first and shallow work batched\n\n## How an expert works\n1. Get a digest of what you missed: Scans mentions, messages, tasks and recent documents in each connected tool, groups them by topic and pulls out decisions and action items.\n2. Run the weekly review: Takes the digest as the list of loose ends. Sorts every open loop into next action, waiting for, someday or dropped, reviews stalled projects and the calendar ahead, and writes next week's plan.\n3. Plan one protected day: Takes tomorrow's tasks from the digest and the weekly plan, marks each deep or shallow, puts deep work in the earliest blocks of 90 minutes or more and batches shallow work into two windows.\n\n## Decision rules\n- Turn every request into owned actions: who, what and by when.\n- Work from the real calendar, notes and lists. Never invent meetings, people or dates.\n- Put the most important decision or deadline first, then the details.\n- Prepare drafts and proposals. Sending, booking and changing records waits for approval.\n\n## Mistakes to avoid\n- Losing commitments buried in long notes.\n- Mixing confirmed facts with guesses about other people's plans.\n- Adding process when a short checklist would do.\n\n## Worked example (not the user's task)\nSituation: You were away or heads-down and need to see what you missed.\nGiven: At least one connected tool, such as chat, email, tasks or files; How far back to look, such as a day, a week or a start date; Tomorrow's tasks and meetings; Your goals for the week (optional)\nA strong result contains:\n- Step 1: Digest: Mentions, decisions and action items from your connected tools, grouped by topic.\n- Step 2: Weekly review: Open loops sorted into next action, waiting for, someday or dropped, plus stalled projects and a plan for next week.\n- Step 3: Protected day: Deep work blocks, batched shallow work windows, buffers and a note of what was cut.\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 Cal Newport (skills/cal-newport/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 urgent task and no backlog: just do the task, or plan the day on its own with the Deep work day planner.\n- You only want tomorrow planned: use the Deep work day planner on its own.\n- You are starting fresh with nothing open: there is nothing to close, so write a simple to-do list for tomorrow.\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 me.md, 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: your role and goals, working preferences, current constraints and the files or records relevant to this job. Reuse answers already supplied. If none exists, offer to build it; a user request to build it already authorizes scoped research.\n3. If me.md is needed, reuse the relevant slice of an existing me.md or use the context method to make one from supplied answers: skills/me-md-builder/SKILL.md. Files: me.md, work/context-check.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\nUse only the parts of me.md that matter for this job. Keep personal and business records private and minimal. Check dates, names and figures against the supplied records. 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/catch-up-on-your-week-close-loops-and-plan-tomorrow/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 catch-up and focus planner (primary): [complete method](../catch-up-on-your-week-close-loops-and-plan-tomorrow/SKILL.md), revision 86d4f3d3eef9\n- Activity digest writer: [complete method](../activity-digest-writer/SKILL.md), revision 22a978189b59\n- Weekly work review planner: [complete method](../weekly-review-guide/SKILL.md), revision 6db6b2c5cadd\n- Deep work day planner: [complete method](../deep-work-day-planner/SKILL.md), revision 402368951550\n- me.md builder (context setup): [complete method](../me-md-builder/SKILL.md), revision 3d3708ece93a\n- Cal Newport (review lens): [complete method](../cal-newport/SKILL.md), revision b18cffcb3289\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","inputs":[{"type":"short_text","required":true}],"outputs":[{"type":"document","required":true}],"resources":[{"slug":"catch-up-on-your-week-close-loops-and-plan-tomorrow","revision_sha256":"86d4f3d3eef9ef6f849a58669286291c6d5130c14592358f649c9ecaae706983"},{"slug":"activity-digest-writer","revision_sha256":"22a978189b590e48e2886c4176bcec5d10392f64df42cd58ee6a2a626f99dd1d"},{"slug":"weekly-review-guide","revision_sha256":"6db6b2c5cadde1deb3697a243517108ee44557e91c5ef952de9357c00fdca40e"},{"slug":"deep-work-day-planner","revision_sha256":"402368951550be24179723b4f2512207a71fbb20b9c5860ce63617a83bb2b927"},{"slug":"me-md-builder","revision_sha256":"3d3708ece93a4a1058ee40604e2adf1d50865fb84dde7fb6871368746a952b53"},{"slug":"cal-newport","revision_sha256":"b18cffcb3289af0a9d5fb069237ab0feb3e677806338409416057b1ddae529fc"}]},"next_action":"Read the role instructions and selected full methods. Resolve task-relevant user context and tool access. Prepare the custom role as a workflow draft with prepare_workflow, or run its complete downloaded pack in the host AI under the user's authorization. No model was called and no task has run."}