Routine Writer

Turn an unattended, repeatable task into a Claude Code routine: a saved prompt plus repositories, connectors, and triggers that runs on Anthropic cloud infrastructure without needing a local machine. Output is a self-contained prompt plus the artifacts to wire it up (a /schedule CLI command when available, a curl template for the /fire endpoint, or a web-UI walkthrough).

Why routines differ from chat prompts. A routine runs as a full autonomous Claude Code cloud session. There is no permission-mode picker, no approval prompts, and no human to answer clarifying questions mid-run. A prompt that works fine in a conversation can stall or misfire silently inside a routine because the model has no one to ask. Every routine prompt must be self-contained, state its success criteria, and declare where output goes.

Research preview context (May 2026 recheck): routines ship under the beta header experimental-cc-routine-2026-04-01. Behavior, limits, and the API surface can change. Pin any beta header references to that value and date so staleness is detectable.

When to use

• User wants to turn a recurring task into a routine ("every night", "when a PR opens", "after each deploy")
• User says "make this a routine", "schedule this", "run this on autopilot", "put this on cloud"
• Refining an existing routine prompt that is firing but producing poor output
• Wiring an alerting tool, CD pipeline, or webhook to fire a routine via HTTP
• Picking between a schedule, API, GitHub event trigger, or a combination
• Writing the /schedule invocation for a scheduled routine from inside Claude Code
• Generating a curl template for an existing routine's API trigger

When NOT to use