agents-remember: Skill for Claude Code

l-01-agent-lifecycles — The Agent Lifecycles

Lifecycle and job are one entity: each agent type runs its own, self-contained lifecycle. This skill is the single roof over all of them — a thin router, the minimal frame every session shares, and the role lifecycles as the payload files. No role is defined by reference to another role's lifecycle, and no role reads another role's file.

Which Lifecycle Am I? (the router — exactly three conditions, in order)

1. AR_SPAWN_ROLE is set (injected by the hosted-seat control plane) → run roles/<value>.md. Nothing else in this file's "developer session" material applies to you. (designer here means the same design hat in a separate chair — see roles/designer.md.)
2. Else: the first user message is a role brief in a fresh session — a templates/*-brief.md-shaped dispatch or a first line of the form ROLE BRIEF — <role> from an orchestrating agent → run that role's lifecycle. The brief is your session start; a workspace session-start notice is not addressed to you.
3. Else (a developer opened this session) → you are the developer-facing free chat — a launcher, not a role seat (ruled 2026-07-09). Research-only questions are answered inline with no role taken. For ordinary role-shaped work (a sprint, a task, any durable change that is not an explicit task-seat takeover), do NOT assume the architect role in this chat: resolve the target sprint, compile one complete brief from templates/architect-brief.md, and call dispatch_agent(task_document_ref=<canonical sprint document>, role="architect", brief=<compiled brief>) once. No plane-injected hosted identity selects ambient-launcher mode; the canonical target document and architect altitude supply its authority. The launcher never submits caller identity or handles a session id. The control plane chooses the settings-owned harness/model/effort, creates the seat, and durably pins the exact brief. On dispatched or dispatch-queued, switch the developer conversation to the canonical (sprint document, architect) chat and stop role work here; both results mean the brief is durable, so never send a second brief. The resulting architect runs roles/architect.md. An explicit developer-declared task-seat takeover is the bounded exception below: it dispatches the named role on that role's canonical task document instead of first creating an architect. For a first sprint, free chat uses the ordinary durable task workflow to create the master and first leaf before this launch; that bounded bootstrap creates scope data, not a global role seat.