---
name: skill-time-management
type: skill
description: Plan Aled's time against his priorities. Use this whenever running the time-management routine, or when Aled asks how to spend his week, wants his time mapped to what matters, or feels overcommitted. Reads the current focus recommendation (the latest skill-plan output) and Aled's calendar, then proposes a weekly time allocation across the ventures and the work lanes — Aled's decisions and reviews, deep work, and relationship and pipeline time — flagging overcommitment and clashes. Proposes a plan; Aled decides and books. Never books or moves calendar events itself.
license: Proprietary — Aled Pritchard workspace use.
---

# time-management

The time-planning skill. It takes what matters this week — the focus recommendation from `skill-plan` — and Aled's actual calendar, and proposes how the week's time should be spent across the ventures and the work lanes. It surfaces overcommitment and clashes before they bite. It proposes; Aled decides and books. Runs on the Linear and calendar connectors. Follows `convention-linear` and `core-operating-model` throughout.

**Ownership.** Owned by **Aide** (`A1-DE`), the Owner-serving agent (see `agent-aide`, `agent-roster`). The skill is **shareable** — the name is agnostic because time-planning is a function, not an owner, so any agent planning the Owner's time may load it. It was renamed from `skill-operator-time` (APP-431) once "operator" became a loaded canon term for a *vertical operator* (`operator-bara`), which the old name misleadingly implied. No behaviour changed in the rename.

**Where it sits in Aide.** Aide composes three skills: `skill-attention-sweep` finds and sizes the cycle's items needing Aled; **this skill** proposes how his time should be allocated across lanes and ventures against those priorities; `skill-time-block` places the specific holds inside `work.Hold`. This skill is the allocation layer — it decides *how much* of the week each lane and venture should claim; it does not itself book (that is `skill-time-block`).

## Trigger

Scheduled run roughly weekly, ahead of the week. Also on demand when Aled asks how to spend his week or feels overcommitted. Reads, never books.

## Behaviour

A run has three passes, in order.

### Pass 1 — Read priorities and the calendar

Read the current focus recommendation — the latest `skill-plan` output (this week's important-by-urgent set and the actions in Aled's lane). Then read Aled's calendar for the week via the calendar connector: what is already booked, how much is committed, and where the open time sits.

If no recent `skill-plan` output exists, note it and propose against milestone and priority directly, flagging that the focus recommendation is stale.

### Pass 2 — Allocate against the lanes

Propose how the open time should be spent, across two axes:

- **The ventures** — madebyneud, careerOS, A1, Mr Pritchard, the apps — weighted to where the strategy needs Aled this week.
- **The work lanes:**
  - **Decisions and reviews** — the gate work only Aled can do: approvals, merges signalled, briefs to decide from.
  - **Deep work** — the focused blocks where Aled himself builds or thinks.
  - **Relationship and pipeline** — the people time: conversations, networking, the pipeline that needs a human.

Match the allocation to the focus recommendation: the more a lane carries this week's important work, the more time it should claim.

### Pass 3 — Flag and propose

Surface the friction:

- **Overcommitment** — the week is already fuller than the priorities can fit; name what would have to give.
- **Clashes** — booked time that collides, or that pulls against the week's stated focus.
- **Gaps** — important work in the focus recommendation with no time allocated to it.

Produce the time plan (below), posted for Aled and assigned to him. Aled decides and books — this skill never books, moves, or declines a calendar event itself. When Aide runs the full loop, the allocation this pass proposes is handed to `skill-time-block`, which places the concrete holds inside `work.Hold` for Aled's confirmation.

## Time plan

Post to the os.Claude project (or a designated planning issue):

```
[time-management] Week of [date]

Against this week's focus ([n] priorities from skill-plan):

By lane:
• Decisions and reviews — [proposed time] — [what it covers]
• Deep work — [proposed time] — [what it covers]
• Relationship and pipeline — [proposed time] — [what it covers]

By venture:
• [venture] — [proposed time] — [why this week]

Flags:
? Overcommitted — [what would have to give]
? Clash — [what collides]
? Gap — [important work with no time]

Proposed shape:
[a sketch of the week — blocks suggested, not booked]
```

## Guardrails

- Never books, moves, reschedules, or declines a calendar event. Reads the calendar; proposes a plan; Aled books (or `skill-time-block` proposes the holds for his confirmation).
- Proposes only — the plan is for Aled to decide from.
- Names overcommitment honestly rather than fitting everything in on paper.
- Never writes code, opens a PR, or touches the delivery loop.
- Aled is the gate. The allocation is proposed; Aled decides and books it.

## Setup

- Claude Code Desktop, Schedule, New remote task. Connectors: Linear and calendar.
- Cadence: roughly weekly, ahead of the week (or on demand when Aled asks).
- Routine prompt: Run the time-management skill.

Owned by Aide (A1-DE); shareable.

On finish, run skill-ops-retro capture on this run's friction: file a FRICTION note to the Pulse queue for the drain pass to assess.