← ClaudeAtlas

plan-adminlisted

Work-planning routines for people who run several projects in parallel: a daily plan (today's blocks, each with its next action and a first step), a day close (where each block was left and the next actions for the next working day) and a weekly review (what went well, collisions, priorities). Reads the schedule, rules and project status from the user's project manager and project instructions, in claude.ai or in Claude Code. Use it whenever the user says 'what's on today', 'what should I do today', 'plan my day', 'where do I start today', 'I'm done for today', 'closing the day', 'weekly review', 'what have I got this week', 'what's on today for my-app', or the equivalent in their language (in Spanish, for example, 'qué toca hoy', 'cierro el día' or 'revisión semanal'), even if the skill is not named. Do not use it to open a session on a project with history (that is a session-opening skill such as resume-project), to archive or close the chat, or to choose skills for a task.
alex20-create/session-routines · ★ 0 · AI & Automation · score 72
Install: claude install-skill alex20-create/session-routines
# Plan admin Three routines for running several projects in parallel: starting the day, closing it and reviewing the week. The skill provides the method; each project provides the data (schedule, rules, which project goes on which day, where the next action is stored) in its instructions and its project manager. That way the same skill works in any project without copying its data, and every piece of data still lives in one place only. Talk to the user in the language they use, including the labels of the formats below. ## Before any routine ### Check the date Get the current date and time from whatever tool is available (a clock tool in the session, or `date` in a terminal), in the user's time zone. Do not infer it from the conversation or the latest note: a wrong day throws the whole plan off. ### Gather the project's data Check which tools the session has (deferred ones included) and read, in this order: 1. **Project instructions, `CLAUDE.md` and user preferences.** They say which phrases start each routine, which block always comes first, which days are off, where status lives and what can be written without asking. Whatever they say takes precedence over this skill. 2. **The schedule and rules page**, if the instructions name one (for example, a weekly review page in Notion with the current schedule, the rules, items pending review and a review template). It tells you which project goes in which block on each day. 3. **The projects database**: status, priority, k