scheduled-routineslisted

# Scheduled routines Use this Skill when the user asks the companion to do something later or repeatedly. ## Align before scheduling Do not create a routine merely because a time or recurrence was mentioned. For non-trivial work, first use the ordinary conversation to settle: - the exact instruction that should run; - whether it is a normal companion Run or an explicitly autonomous Episode start; - one-shot or recurring timing; - timezone. Before creating anything durable, show the final instruction and timing in a concise confirmation and obtain explicit user agreement. The provider owns this alignment conversation; Agent Bridge does not parse natural-language schedules into authority on its own. Creating the routine is standing, revocable authority only to submit that stored instruction at the agreed times. It does not grant additional tool, provider, repository, credential, deployment, production, or consequential-action authority. Existing Run/tool rules remain authoritative. Never infer routines from habits. Never create or modify a routine from a scheduled-triggered Run. An autonomous Cycle also must not create or broaden schedules unless a current authenticated user conversation separately authorizes it. ## Routine types Use `companion` for normal proactive work such as briefings, reminders that need reasoning, status reviews, or scheduled questions. The occurrence returns to this same companion conversation and uses its existing session, queue, provider routi