A few weeks ago I shipped Skills — a way to save AI prompts as reusable templates inside ContextForge , so my best prompts wouldn't keep dying in a Notion page nobody opens. It worked. I stopped losing them. Then I noticed something worse. I had a Skill that drafts marketing copy every time we ship a feature. Another that summarizes my weekly progress. Another that generates LinkedIn posts. They were all sitting there, clean and named, in a tab I'd open every Monday morning and slowly click "Run" on like a factory line. That's when it hit me: I built a library, not an assistant. Skills were just dead prompts with a database row. So I built Routines. What a Routine actually is A Routine is a Skill on a cron expression. That's it. You pick a Skill (the prompt template). You pick a schedule — daily , weekly , monthly , or any 5-field cron you write yourself. You pass the input variables. You hit Create. From then on, ContextForge fires the Skill on schedule, forever, until you pause or delete the Routine.…