Make repeatable work useful.

Define the task first

Use a task to name an outcome and track its status. Give the agent enough context to work and an explicit standard for completion. A recurring responsibility should start as a task you can run and verify once.

Schedule with clear expectations

Routines provide a schedule for agent work. Confirm the intended agent, instructions, project, and timing before enabling a routine. The local application needs to be running for local work to execute; this is not a promise of an always-on hosted agent.

Provider authentication, usage limits, and device availability can interrupt a run. Review completed and failed work instead of assuming that a schedule guarantees an outcome.

Keep the output reviewable

• Ask for a concise summary and the evidence behind it.
• Keep external actions behind an explicit review decision.
• Update or disable a routine when its project or responsibility changes.