---
name: skill-attention-sweep
type: skill
description: Sweep the committed cycle for everything that needs Aled and size it. Use this whenever running the Aide attention sweep, or when Aled asks what in the current cycle needs him. Reads the upcoming/committed cycle across the delivery projects (read-only), finds the items needing him — assigned to him, human-lane, awaiting his review or approval, or an open decision — classifies each and sizes it into 15m/30m/1h/2h, routing anything over 2h to Relay to split. Produces the classified, sized list that skill-time-management allocates and skill-time-block books. Never re-prioritises, never writes Linear, never books calendar.
license: Proprietary — Aled Pritchard workspace use.
---

# attention-sweep

The read-and-classify half of Aide. It sweeps the **committed cycle** for everything that needs Aled, works out what kind of attention each item wants, and sizes it — so the rest of Aide (`skill-time-management` to allocate, `skill-time-block` to book) has a clean, sized worklist rather than the whole board. It is strictly read-only on Linear: it schedules Aled's attention, it never re-prioritises the work. Runs on the Linear connector. Follows `convention-linear` and `core-operating-model` throughout.

**Ownership.** Owned by **Aide** (`A1-DE`); see `agent-aide`. Downstream of Atlas — it reads the cycle Atlas (or Aled) has already **committed**, not the whole backlog, so Aide only ever schedules against agreed scope.

## Trigger

Runs after the cycle is committed (the start of the cycle, or on demand when Aled asks what in the current cycle needs him). Read-only.

## Scope — the committed cycle only

Sweep the **current committed cycle** across the delivery projects (careerOS, Apps, A1, Mr Pritchard). **Never the whole board, never Pipeline.** If no cycle is committed yet, say so and stop — there is nothing agreed to schedule against (the sweep is downstream of Atlas's commit, per `agent-aide`).

## What counts as "needs Aled"

Include a cycle item if any of these holds:

- **Assigned to Aled** — anything on his plate directly.
- **Human-lane** — carries the `agent`-group value `human` (his decisions, design, launch ops, on-device verifies).
- **Awaiting his review or approval** — In Review carrying `agent:PR-1SM` (or a QA write-up) with him assigned; the merge-gate sign-offs only he gives.
- **An open decision** — a ticket whose latest unprefixed comment poses a question to him, or a Refinement ticket assigned to him carrying a genuine question (per `convention-ticket`).

Exclude pure agent work with no gate for Aled — Forge build legs, Relay routing, Pulse intake — unless one of the above applies.

## Classify and size

For each included item:

1. **Classify the attention it wants** — `decision` (a call to make), `review` (sign-off on built work), `action` (something for him to do), or `deep-work` (a focused build/think block he owns).
2. **Size it** into one of **15m / 30m / 1h / 2h** — the shared sizing scale Aide books against. Estimate from the ticket's shape, not its title alone.
3. **Oversized → Relay, don't schedule.** Anything that genuinely needs **more than 2h** is too big for a single hold: flag it for **Relay** to split (a comment naming it needs breaking down), and **leave it out of the sized list** — do not size or schedule an item that should be decomposed first.

## Reading Linear safely

Per `convention-linear` (*Reading Linear safely*): scope reads **per project**, not per team, and filter by cycle plus state so a bulk `list_issues` doesn't overflow; the `agent`-group filter takes the **bare** value (`human`, `PR-1SM`), not the displayed `agent:` form; a `Backlog` filter also returns Refinement, so re-check each ticket's state name; and read comment **bodies**, not the author field, to tell an operator question from an agent comment.

## Output

Produce the **classified, sized worklist** — one line per item: `ID · title · class (decision/review/action/deep-work) · size (15m/30m/1h/2h) · why it needs Aled`. List oversized-and-routed items separately with a note that they went to Relay to split. This list is the input to `skill-time-management` (which allocates the week's shape against it) and `skill-time-block` (which books the holds). This skill hands off the list; it does not allocate or book.

## Guardrails

- **Read-only on Linear.** Never changes state, labels, priority, assignment, or cycle membership — it reads what needs Aled, it does not re-prioritise it. Re-prioritisation is Atlas/Relay's, not Aide's.
- **Committed cycle only.** Never sweeps the whole board or Pipeline; if nothing is committed, stops.
- **Never books calendar** — that is `skill-time-block`. This skill only produces the sized list.
- **Oversized items are routed, not sized** — >2h goes to Relay to split.
- Aled is the gate. The sweep informs; it decides nothing.

## Setup

- Deployed as part of the Aide driver task (Linear + Calendar), run after the cycle is committed. Connector: Linear (read-only) for this skill.
- Cadence: per cycle (weekly), or on demand.

Owned by Aide (A1-DE).

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.