---
name: task-strategy-review
type: task
description: Weekly Atlas strategy review — sweeps every area for a complete strategy (purpose, objectives, KPI tree with baselines and targets) and for drift, and raises a surfaced gap ticket to Aled for each thing missing or off track. Each ticket carries Atlas's draft and the open questions, and can be answered inline or reopened in Claude to run the engagement live. Linear connector only; proposes only — never writes strategy itself. Self-contained task.
license: Proprietary — Aled Pritchard workspace use.
---

# task-strategy-review

Atlas's weekly strategy loop. Strategy is not set once and left — it is kept live. Each week this task checks whether every area has a *complete* strategy and whether the live ones are still on track, and turns each gap into a **ticket to Aled** he can act on. It never writes the strategy itself; it raises the questions and drafts the answers, so Aled only has to decide. Linear connector only. Follows `convention-linear` and `core-operating-model` throughout: calm, precise, sentence case, British spelling, no exclamation marks.

This is the **completeness-and-drift** layer. It does not re-do `skill-goal-review`'s assessment; it consumes it. And it does not author the fix; that is `skill-strategy-charter` (the why) and `skill-strategy-cascade` (the KPIs), run on Aled's engagement.

## Scope

The **outcome-initiatives** across the ventures — careerOS, Apps / os.Claude, A1, Mr Pritchard, madebyneud / BARA. **Never the Pipeline team.** Read-mostly; the only writes are the gap tickets (and updates to ones already open).

## Behaviour

### Pass 1 — Completeness check

For each area's outcome-initiative, check it has a complete strategy:

- **Charter** — a purpose, who it serves, a mission, a vision of winning (the `skill-strategy-charter` output).
- **Objectives** — 2–4 objectives that serve the goal.
- **KPI tree** — each objective carrying at least one KPI with a **baseline and a named target** (not "baseline to be established").

Any of these missing is a completeness gap.

### Pass 2 — Drift pickup

Read the latest `skill-goal-review` output (its stalled / drifting findings and its refocus / de-scope / escalate proposals). Any open drift finding not already carried as a ticket is a drift gap. This task does not re-assess movement — it surfaces what `skill-goal-review` already found as an actionable ticket.

### Pass 3 — Raise (or update) one gap ticket per gap

For each gap, **dedupe first** — search the area's project for an open `STRATEGY:` ticket for the same area and gap; if one exists, update it (add a dated note) rather than opening a second. Otherwise raise a new ticket in the **area's own team/project**, in the gap-ticket format below, **assigned to Aled** and placed in **Todo** so it lands in his morning brief's "Your move" bucket (per `task-daily-report`). Labels: `type:task`, `work:configuration`.

### Pass 4 — Report

Short summary: areas checked, gaps found (completeness vs drift), tickets raised and updated (IDs), anything already complete. No preamble, no sign-off.

## Gap-ticket format

Each ticket is written so Aled can act in two minutes — inline, or by handing it back to Claude:

```
STRATEGY: [area] — [what's missing / drifting]

Area: [venture / initiative]
Gap: [no purpose set | objectives missing | KPIs without targets | KPI [x] drifting off target]

Atlas's draft (react to this — it's a starting point, not a decision):
[best-guess purpose / objectives / candidate targets drawn from existing material]

What I need from you:
1. [specific question]
2. [specific question]

Two ways to resolve:
• Answer inline here, and Atlas cascades it into the initiative + KPIs.
• Reopen in Claude — paste this ticket and say "run the strategy charter for [area]".
  Claude loads skill-strategy-charter seeded from this ticket, runs the Q&A live,
  writes the agreed charter + KPIs to the initiative, and closes this ticket.

The ticket holds the context; bringing it into Claude makes it a conversation.
```

The ticket is the durable memory of the gap; the Claude session is the dynamic engine that resolves it. Either path ends the same way — the charter and KPIs written to the initiative, this ticket closed.

## Guardrails

- **Proposes only.** Raises tickets and drafts answers; never writes a charter, sets a target, or changes an initiative — those flow through `skill-strategy-charter` / `skill-strategy-cascade` on Aled's engagement.
- **Dedupe.** One open `STRATEGY:` ticket per area-and-gap; update rather than re-raise, so the weekly cadence doesn't spawn duplicates.
- **Surfaced, not buried.** Every gap ticket is assigned to Aled and placed where his brief reads it (Todo / "Your move") — a strategy gap is a "needs you", and must show like one.
- **Consumes goal-review, doesn't duplicate it** — drift assessment is `skill-goal-review`'s; this task turns its findings into tickets.
- Linear only — never writes code, opens a PR, or touches the delivery loop. Never touches the Pipeline team.
- Aled is the gate. Atlas raises the questions and drafts; Aled decides.

## Setup

- Deployed as a **Cowork scheduled task** (cloud), weekly, aligned to the cycle/review day so it runs alongside cycle-planning. Connector: Linear only.
- Self-contained (no separate skill); if it ever needs on-demand invocation beyond the schedule, extract a `skill-strategy-review` and reduce this to a loader.
- Output: gap tickets (not a file) plus a short run summary.

Owned by Atlas (ATL-4S).

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.