Weekly planning
A realistic plan for your week, saved in your calendar
Turn commitments and priorities into a realistic weekly plan, then verify it is recorded in your calendar or planner. For individuals and freelancers.
- Personal life
- Agent does 1 of 3 steps
- 1 person involved
- 2 possible endings
- Agent
- Person
At a glance
The agent handles
- Draft weekRead the supplied commitments and priorities for weekOf.
People decide and act
- YouDoes · Choose planReview the proposal against your actual energy, obligations and available hours.
- YouDoes · Record planSave the accepted plan in your chosen planner or calendar.
How it can end
- Planning deferred
- Week planned
Purpose and scope
Start once for a selected week when commitments and priorities are available. Completion means a feasible plan is saved and checked; it does not mean the week's work is finished. The initiator owns and accepts the plan.
Process map
Explore who does what, where decisions happen, and how the process finishes.
Read-only · Select a step to inspect it
Loading the process map…
Pan to explore, use + / − to zoom, or switch to Step by step for a readable list. Human approvals and parallel branches follow the same flow as the app.
What it handles
Real situations the process is designed for, including the ones that go wrong.
Capacity is ample
Select the plan, save it, and verify entries.
Commitments exceed capacity
Defer work or choose planning_deferred.
An interrupted calendar save already created entries
Reuse them without duplication.
When things go wrong
Exceptions and recovery
Unavailable calendar information or unclear priorities goes back to the person through escalation. Inspect saved entries after an interrupted write; do not duplicate blocks. A changed commitment requires reviewing the affected plan, not erasing unrelated work. Deferral leaves the calendar unchanged.
What you’ll need
Fit the template to your people and tools, then try it with a few real cases before going live.
People to involve
- You (the person starting it)
Have these ready
- Week of
- Commitments reference
- Priorities reference
- Available hours
Setup checklist
- Start as a person because tasks use initiator; no other role bindings are needed.
- Choose a private planner and grant only the access you intend. Supply references to commitments and priorities.
- Define discretionary available hours, include care/rest commitments, and agree how estimates and buffers are handled.
- This is an adaptable template. Rehearse with sample data before any live calendar edits.
How to measure it
Track the share of planned outcomes completed or consciously renegotiated, and the time spent planning. Review actual capacity at the next weekly run; set personal targets only after observing a baseline.
Put it to work
Start with the file today. Plug it into your agents and tools when you’re ready.
Adapt it
Name your people, tools and rules. Your AI assistant can walk you through it with the prompt above.
What makes a good processConnect your agents
Claude, Codex, Cursor and the other agents your team already uses can pick up the agent steps.
See supported agentsRun it with Agent Process
Sign-offs by email, your data and systems, and a full record of every run.
Join the waitlist
Source, compatibility & validation
A starter template from the Agent Process collection. It passes structural validation; your own policies, tools and outcomes still need a rehearsal before live use.
Requires core protocol support. The package does not install connectors or grant access.
Package SHA-256: a3b3e9c8af26b0ad3cb1bddf006ac99721f5265e3580e186834eab04c69bb44e
Inspect full PROCESS.md
---
name: weekly-planning
description: Turn commitments and priorities into a realistic weekly plan, then verify it is recorded in your calendar or planner.
inputs:
weekOf: date
commitmentsReference: string
prioritiesReference: string
availableHours: number
steps:
- id: draft_week
agent: Read the supplied commitments and priorities for weekOf. Confirm availableHours is nonnegative and represents discretionary capacity after fixed commitments. If its meaning is unclear, escalate. Identify deadlines, fixed appointments and dependencies. Propose a small achievable set of outcomes within capacity, with buffers and explicit tradeoffs. Do not change calendars or notify anyone.
output:
proposedPlan: string
estimatedHours: number
conflicts:
type: list
items: string
deferredItems:
type: list
items: string
- id: choose_plan
person: initiator
task: Review the proposal against your actual energy, obligations and available hours. Resolve conflicts, choose outcomes and time blocks, and explicitly defer excess work. Record the final plan. Choose record_plan only when the plan fits capacity and fixed commitments. Choose deferred when you do not want to commit this week.
output:
finalPlan: string
decisionReason: string
next:
- to: record_plan
when: The person accepts a feasible plan
- to: deferred
when: The person defers planning without committing
- id: record_plan
person: initiator
task: Save the accepted plan in your chosen planner or calendar. Inspect existing entries for weekOf before creating or changing anything. Do not overwrite unrelated appointments or send invitations without intent. Read back the saved entries and check dates, time zones and durations. Keep this task open if saving or conflict resolution is incomplete.
output:
plannerReference: string
verificationSummary: string
evidence:
- link
next: planned
- id: deferred
finish: planning_deferred
- id: planned
finish: week_planned
---
# Weekly planning
Marketplace fit: Individuals, freelancers and busy parents who want an achievable week rather than a longer task list.
## Purpose and scope
Start once for a selected week when commitments and priorities are available. Completion means a feasible plan is saved and checked; it does not mean the week's work is finished. The initiator owns and accepts the plan.
## Before adoption
- Start as a person because tasks use initiator; no other role bindings are needed.
- Choose a private planner and grant only the access you intend. Supply references to commitments and priorities.
- Define discretionary available hours, include care/rest commitments, and agree how estimates and buffers are handled.
- This is an adaptable template. Rehearse with sample data before any live calendar edits.
## Exceptions and recovery
Unavailable calendar information or unclear priorities goes back to the person through escalation. Inspect saved entries after an interrupted write; do not duplicate blocks. A changed commitment requires reviewing the affected plan, not erasing unrelated work. Deferral leaves the calendar unchanged.
## Measures and review
Track the share of planned outcomes completed or consciously renegotiated, and the time spent planning. Review actual capacity at the next weekly run; set personal targets only after observing a baseline.
## Rehearsal cases
- Capacity is ample: select the plan, save it, and verify entries.
- Commitments exceed capacity: defer work or choose planning_deferred.
- An interrupted calendar save already created entries: reuse them without duplication.
## Process map
Declared transitions below. Escalation, pending work and operator cancellation follow the instructions above.
```mermaid
flowchart TD
draft_week("Draft week<br/>Agent"):::agent
choose_plan["Choose plan<br/>Person: initiator"]:::person
record_plan["Record plan<br/>Person: initiator"]:::person
deferred(["Planning deferred"]):::outcome
planned(["Week planned"]):::outcome
draft_week --> choose_plan
choose_plan -->|"The person accepts a feasible plan"| record_plan
choose_plan -->|"The person defers planning without committing"| deferred
record_plan --> planned
classDef agent fill:#E6F0EE,stroke:#0E5E59,color:#0B3B38,stroke-width:1.5px
classDef person fill:#FDF4E4,stroke:#A15500,color:#4A2B00,stroke-width:1.5px
classDef wait fill:#EEF3FD,stroke:#2456C2,color:#16264D,stroke-width:1.5px
classDef flow fill:#F6F5F1,stroke:#8F8C83,color:#1C1D1A,stroke-width:1.5px
classDef outcome fill:#1C1D1A,stroke:#1C1D1A,color:#FFFFFF
```