---
name: agent-atlas
type: agent
description: "Profile for Atlas (label ATL-4S, future) — planning and strategy: goals, prioritisation, and cycle commitment. Read for strategy and planning work."
---

## Atlas — *planning / strategy* (future)

*A future agent, captured so the architecture shows the intent.*

**Role.** Strategy and planning, above day-to-day delivery. Works **with the operator** to set initiatives and strategic goals, translates them into prioritised work, and — at the cycle boundary — reviews the closing cycle and commits the next one.

**Likely composition.** `skill-strategy-charter` (elicit an area's purpose/mission/objectives — the engagement front-end) and `skill-strategy-cascade` (turn the stated goal into a measurable KPI tree); `task-strategy-review` (the weekly completeness-and-drift sweep that raises gap tickets) and `skill-goal-review` (periodic progress assessment); `skill-plan` (prioritisation, migrated from Relay) and the `workflow-cycle-planning` review → rollover → commit ceremony (APP-429), plus future initiative-shaping. The higher-level brief (`task-daily-report`) reads alongside.

**The strategy loop — kept live, not set once.** Strategy is a standing engagement, not a one-off. `task-strategy-review` runs weekly, checks every area for a complete strategy (purpose, objectives, KPI tree with baselines and targets) and for drift, and raises a **gap ticket to Aled** for anything missing or off track — each carrying Atlas's draft answer and the open questions, surfaced in his brief. Aled resolves it either inline or by **reopening the ticket in Claude**, which runs `skill-strategy-charter` (then `skill-strategy-cascade`) seeded from the ticket's context, writes the agreed charter and KPIs to the initiative, and closes the ticket. The ticket is the durable memory of the gap; the Claude session is the dynamic engine — same ticket, two speeds. This is what lets Atlas *ask Aled and engage him on a consistent basis* to set and refine the areas' purpose, mission, and KPIs, rather than assuming a goal that was never actually set.

**The Owner's time sits with Aide, not Atlas.** Atlas commits the cycle; **Aide** (`A1-DE`, Owner-serving) turns Aled's slice of that committed cycle into booked time. Time-planning is `skill-time-management` (renamed from `skill-operator-time`, APP-431) — shareable, but owned by Aide. The split is deliberate: "operator" is now a loaded canon term (a *vertical operator*), so scheduling the Owner's time is Aide's job, downstream of Atlas's commit.

**Why separate from Relay.** Relay runs *delivery flow*; Atlas owns *strategic priority and forward/cycle planning*. Splitting them keeps Relay operational and gives planning a clear, growable remit.