---
name: skill-goal-review
type: skill
description: Periodic review of progress against the outcome-initiatives and their KPIs across all ventures. Use this whenever running the goal-review routine, or when Aled asks how the strategy is tracking, which goals have stalled, or which KPIs are off target. Reads initiatives, their linked tickets and milestones, and KPI movement, then reports what is on track, what has stalled, and what is drifting — and proposes refocus, de-scope, or escalation for Aled to decide. Read-mostly; proposes only. Produces a scannable review summary.
license: Proprietary — Aled Pritchard workspace use.
---

# goal-review

Atlas's periodic strategy check. Roughly monthly or quarterly, it reads the outcome-initiatives across every venture and reports honestly on where the strategy stands — on track, stalled, or drifting — and proposes what to do about it. It does not change the strategy itself; that is skill-strategy-cascade with Aled's approval. Runs on the Linear connector only. Follows `convention-linear` and `core-operating-model` throughout.

## Trigger

Scheduled run roughly monthly or quarterly across all ventures: careerOS, Apps, A1, Mr Pritchard, and madebyneud. Also on demand when Aled asks how the goals are tracking. Never touches the Pipeline team.

## Behaviour

A run has three passes, in order.

### Pass 1 — Read the goals layer

Read all outcome-initiatives across the ventures (the source produced by `skill-strategy-cascade`). For each, note: name, strategy statement, objectives, KPI targets and baselines, current status, linked tickets, and milestone targets.

If no outcome-initiatives exist for a venture, note the gap in the summary and propose running `skill-strategy-cascade` for that domain rather than reviewing against nothing.

### Pass 2 — Assess movement

For each initiative, read the linked tickets and milestones and the KPI movement since the last review, and place it in one of three states:

- **On track** — KPIs moving toward target at a reasonable pace; milestones being met.
- **Stalled** — no meaningful progress in the period: no tickets closed, milestones slipping with no activity, the initiative quietly parked.
- **Drifting** — work is happening but the KPIs are off target, or the activity no longer maps cleanly to the objective it was meant to serve.

Be honest about stalls and drift. A clear "this has not moved" is more useful to Aled than a generous reading.

### Pass 3 — Report and propose

Produce the review summary (below). For each initiative that has stalled or is drifting, propose one of:

- **Refocus** — the goal stands but the effort is misdirected; recommend where attention should move.
- **De-scope** — the goal is too large or no longer worth its full ambition; recommend trimming it.
- **Escalate** — the goal is blocked or at risk in a way Aled needs to decide on directly.

Each proposal is a recommendation with its reason, posted for Aled and assigned to him. Do not change initiatives, cancel goals, or re-cut strategy in this skill — those are proposals Aled approves, then actioned via `skill-strategy-cascade`.

## Review summary

Post the summary to the os.Claude project (or a designated strategy-review issue). It is the deliverable Aled reads:

```
[goal-review] Strategy — [date] — [period covered]

On track:
• [venture] / [initiative] — [KPI] at [value] vs [target]

Stalled (no progress this period):
• [venture] / [initiative] — [what has not moved]

Drifting (off target):
• [venture] / [initiative] — [KPI] at [value] vs [target], [why]

Proposals (needs your decision):
? Refocus / De-scope / Escalate — [initiative] — [recommendation and reason] — [link]
```

Keep it scannable. Aled reads it at his review, not line by line.

## Guardrails

- Read-mostly. Proposes only; never changes strategy, cancels a goal, or re-cuts a cascade — those flow through `skill-strategy-cascade` on Aled's approval.
- Never marks an initiative or ticket Done.
- Linear only — never writes code, opens a PR, or touches the delivery loop.
- Never touches the Pipeline team.
- Honest assessment over generous: name stalls and drift plainly.
- Aled is the gate. Atlas proposes; Aled decides.

## Setup

- Claude Code Desktop, Schedule, New remote task. Connector: Linear only.
- Cadence: roughly monthly or quarterly (or on demand when Aled asks how the goals are tracking).
- Routine prompt: Run the goal-review skill.

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.