Skip to content
Work OSWork Compass
OverviewPack SetupWorkflowsWorkflows indexCustomizationKnowledge
Work OS · Work Compass · Pack Setup

Pack Setup

Work Compass setup establishes the connections, configuration files, and operating rules needed for the weekly planner to run safely. It is resume-first: valid outputs are skipped, and setup resumes at the first missing or invalid component.

Setup creates the initial operating baseline. Later changes belong in Customization and normally apply to future workflow runs; they do not silently rewrite previous plans, tasks, logs, or calendar decisions.

Before you start

Start from a registered Work OS workspace.

Work Compass runs inside an existing Work OS workspace. Create that workspace first, then start setup from a new chat session.

If the workspace does not exist yet, create and register it before setting up Work Compass.

The workspace should have a clear name, a real location on disk, and an active entry in the workspace registry. Work Compass setup then adds the calendar, planning, rules, and task state it needs inside that workspace.

Install the Work Compass Pack

Install the current pack before configuration.

The current Work Compass Pack is provided in the shared REBOOT resource folder on Google Drive. Every REBOOT student can access this folder. Download the latest release available there; the folder may contain a newer release than the one described in an earlier lesson or screenshot.

  1. Open the shared REBOOT Work Compass Pack folder in Google Drive.
  2. Download the current Work Compass Pack and unzip it.
  3. Inside the extracted folder, find deployment/install.md and copy its full file path. The path will look like /Users/your-name/Downloads/work-compass-pack/deployment/install.md; use the folder name created by the release you downloaded.
  4. Open your 10 Work Compass workspace in Cowork and run:
Prompt example

run [paste the full path to deployment/install.md]

  1. Follow the installation instructions through the migration steps, managed-file installation, and post-install validation. Wait for the complete deployment receipt before continuing.

Run the deployment from inside 10 Work Compass. The installation instructions need that workspace as their starting point. Once the deployment is complete, continue with Work Compass setup below.

Get Work Compass ready to run your weekly planning workflow

Give Work Compass the context it needs.

01

What setup gives you

Setup gives Work Compass enough context to plan against your real working life:

  • the workspaces you actively use;
  • the calendars that contain real commitments;
  • your working hours, planning preferences, and recurring constraints;
  • the rules that determine how Work Compass interprets time, tasks, and conflicts;
  • a valid place for daily captures and weekly planning records.

Open a new chat session in the Work Compass workspace and begin with the intent: “set up my Work Compass.” This starts the setup conversation. You can run setup again later; it checks what is already valid and resumes at the first part that needs attention.

Setup does not permanently lock your choices. It records them as editable configuration and rules, then verifies that the resulting system is ready.

Connections and dependencies

Verify capabilities, not connection labels.

Work Compass must know which connected services it relies on before setup can be considered complete. A connection is useful only when the required capability works, not merely because the service is available.

ConnectionRequired forIf unavailable
Calendar connectionReading commitments, checking capacity, and projecting approved workReadiness fails if the required Priority Calendar is unavailable or not writable. Work Compass does not substitute another calendar.
Inbox connectionInbox Triage and email-derived task candidatesInbox Triage is skipped. Planning can continue without inbox candidates.
Your Work Compass filesReading workspaces, configuration, logs, and capturesSetup cannot verify the system until the files are restored.

During setup, identify each connection in use, test the capability Work Compass needs, and record whether access is required, optional, read-only, or writable. If a required connection is unavailable, setup stops at readiness rather than quietly substituting another service.

How setup learns how you work

Complete only the interviews the workspace needs.

Setup does not ask one long list of unrelated questions. It checks what is already valid, then runs only the interviews needed to fill the gaps. Each interview covers a different part of the working context Work Compass needs.

01

Workspace interview

What happens: Work Compass looks at the folders available in your work folder, shows you the eligible workspaces, and asks which ones are active. It reads each selected workspace’s description when available and asks whether you want a @personal catch-all for personal and family work. You review the proposed workspace list before it is saved.

After: Work Compass has a working map of where your work lives. That map helps later planning and task capture use the right workspace instead of relying on memory or guesswork.

If you need to rerun this interview on its own, use Templates/prompt-interview-workspaces.md from the Work Compass Pack.

02

Calendar and planning interview

What happens: Work Compass first confirms that Google Calendar is connected and checks your primary calendar. It then asks which calendars matter, what each one contains, whether access should be read-only or writable, and which calendar should receive approved Focus Work. The interview also covers working hours, lunch, weekends, recurring commitments, focus-time preferences, customer-booking windows, planning mode, and when you want to plan your week. Initial calendar discovery is limited to the last 24 hours.

You review one proposed summary covering the calendar configuration, planning settings, and Compass rules before anything is saved. Work Compass then validates that the Priority Calendar is active and writable.

After: Work Compass can build a weekly plan around your real commitments, working boundaries, and planning preferences. Approved Focus Work has one clear calendar destination, while other calendars can still inform capacity and conflicts.

If you need to rerun this interview on its own, use Templates/prompt-interview-calendar-planning.md from the Work Compass Pack.

03

Inbox interview

This interview runs only when Inbox capability is enabled and the inbox configuration is missing or incomplete.

What happens: Work Compass confirms the connected inbox, uses only the last 24 hours for initial discovery, and asks you to confirm the inbox and its mixed-signal behavior. It also asks what business name to use for business classification. You review the proposed classification, work-signal, disposition, and task-candidate behavior before it is saved.

Inbox Triage labels emails only after you approve the proposed decisions. It does not send, delete, or archive emails automatically.

After: Inbox Triage has a clear source and a safe classification baseline. It can identify possible work and reply items without silently changing your inbox, and approved Needs Reply items can become To-Do List work with a source link.

If you need to rerun this interview on its own, use Templates/prompt-interview-inbox-config.md from the Work Compass Pack.

04

What happens after the interviews

Work Compass creates or checks the shared To-Do List, preserves valid existing configuration, and runs the final Readiness Check. That check confirms the workspace, calendar, planning, inbox, rules, runtime, core workflow coverage, and live Google Calendar access.

Only a passing Readiness Check means setup is complete. If something fails, Work Compass identifies the component to fix and resumes from there when you run setup or the readiness check again.

Configuration supplies values. Rules translate those values into behavior. A later rule change normally affects future workflow runs; existing weekly logs, completed tasks, prior plans, and calendar decisions stay unchanged unless you explicitly request a migration or recalculation.

The output: what setup creates and where it goes

What setup creates and where it goes.

Setup produces a small set of configuration and readiness records. Some are saved only after you approve the proposed content; the shared task hub is created automatically when it does not exist.

OutputWhat happensWhere it goes
Workspace registryRecords the active workspaces and optional @personal routing. Saved after you approve the workspace proposal.{@WORK-OS}/_OS/Operations/workspaces.md
Calendar configurationRecords calendar sources, roles, permissions, working hours, recurring constraints, and Focus Work preferences. Saved after you approve the setup summary.Knowledge/config-work-compass-calendar.md
Planning configurationRecords Phase 1, planning mode, planning window, Focus Work sizes, Priority Calendar projection, and output paths. Saved with the calendar configuration after approval.Knowledge/config-work-compass.md
Compass rulesRecords the rules that shape commitment, conflict, capture, and planning behavior. Created or extended with the approved calendar and planning setup.Knowledge/rules-work-compass.md
Inbox configurationRecords the inbox source, classification baseline, work signals, dispositions, and task-candidate behavior. Saved after approval when Inbox capability is enabled and configuration is missing or incomplete.Knowledge/config-work-compass-inbox.md
Shared To-Do ListCreates the current empty structure when missing, or migrates eligible open work when an older format is found.{@WORK-OS}/_OS/Operations/TASKS.md
Setup readiness recordRecords the final readiness result and setup run reference after the required checks pass. A failed or interrupted setup does not replace a previous valid readiness record.Knowledge/runtime-work-compass.md

The workspace and calendar interviews may also add entries for new configuration files to Knowledge/knowledge.md. That file is the index that helps Work Compass find the configuration; it is not another planning configuration file.

Understand and manage your current configuration

Inspect and change configuration through Work Compass.

You do not need to open configuration files yourself. Ask Work Compass to read the current workspace, settings, rules, and connection state, then explain the result in plain language.

01

Get the overall configuration summary

Use this prompt when you want a complete, current view:

Prompt example

Give me a plain-language summary of my current Work Compass configuration. Include my workspace, connections, calendar roles, working boundaries, planning mode, priority model, task capture behavior, active rules, and readiness status. Read the actual current configuration and tell me what is missing, invalid, or ambiguous.

The summary should be generated from the current 10 Work Compass workspace, not from an old setup report or a remembered answer.

02

Look up one use case

Use this prompt when you want to understand one setting quickly:

Prompt example

For [use case], tell me which Work Compass setting or rule controls it, what the current value is, which workflow uses it, what behavior it produces, and the exact prompt I should use if I want to change it.

Examples:

  • “For changing my Priority Calendar, tell me which setting controls it and how to change it safely.”
  • “For planning from priorities versus tasks, tell me which setting controls it and what each option changes.”
  • “For treating placeholder calendar events as soft holds, show me the active rule and how to change it.”
03

Change a setup-level configuration

Use prompts such as:

  • “Change my official commitment calendar to [calendar]. Show me the effect before saving.”
  • “Use [calendar] as my Priority Calendar and verify that it is writable.”
  • “Update my working hours to [hours]. Tell me how this changes capacity calculations.”
  • “Add [recurring commitment] to my planning constraints.”
  • “Show me which calendar settings control where approved Focus Work is placed and what changes when I update them.”

Work Compass should read the current state, explain the proposed change, check its dependencies, wait for approval, update the canonical configuration, and run a readiness check against the resulting workspace.

Keep the system aligned with your work

Maintain the live configuration.

Update these settings as your working system changes:

  • active workspaces and their paths;
  • calendar sources, write access, working hours, and preferences;
  • planning phase, week-start day, planning mode, task sizes, and projection settings;
  • Compass rules;
  • the shared task list and Inbox state.

You do not need to rebuild valid configuration from scratch. Rerun setup or update the relevant customization when a workspace changes, calendar access changes, or your working rules change.

Check that the system still matches reality

Detect configuration drift before it breaks planning.

Run the Readiness Check whenever setup or a dependency changes, or when the workspace no longer matches the way you work.

Run the check when:

  • a workflow stops finding an expected file;
  • a workspace is renamed, moved, or no longer active;
  • calendar access or write permissions change;
  • planning behavior no longer matches the configured phase or mode;
  • the shared task list has reverted to an old structure;
  • setup was interrupted before the Readiness Check passed.

The Readiness Check compares the current workspace and settings with what Work Compass needs, tests the required connections, and reports the exact component that is missing or invalid. It is the completion signal for setup; fix the marked component and run the check again.

If setup stops or a connection changes

Recover, verify, and confirm the readiness record.

ProblemCorrection
Google Calendar is not connectedAuthorize Google Calendar in Claude Connected Apps, then rerun setup
A setup step was interruptedRerun setup; valid completed steps are skipped
Prior configuration is incompleteResume at the first invalid component and complete that interview
Priority Calendar is unavailableRestore access or write permission. Never substitute the official commitment calendar or another writable calendar
Readiness check failsFix the marked component, then rerun the Readiness Check without repeating the full setup
Verification

Successful setup ends with the explicit message that Work Compass is configured and ready, followed by the instruction to run the first weekly planner.

Setup result

Setup records its readiness result in Knowledge/runtime-work-compass.md. That result shows whether the required workspace, calendar, inbox, task list, and connection checks passed. It remains the authoritative record of setup readiness and is updated when setup is rerun; confirm the result before starting weekly planning.