← ClaudeAtlas

recipe-timelinelisted

Convert a written recipe into an execution-order cooking timeline: when to act, how long until the next action, where prep fits, and how parallel components converge. Use when a recipe needs turning into a cooking plan.
tiny-glitch/recipe-timeline · ★ 0 · DevOps & Infrastructure · score 67
Install: claude install-skill tiny-glitch/recipe-timeline
# Recipe Timeline Turn a conventional recipe into an execution plan for one cook. A recipe lists actions in **written order**. This skill re-renders them in **execution order** — a cooking dependency graph laid out against a clock. Each plan row answers three questions at once: - **Where am I?** — cumulative position - **How long until I must act?** — the interval marker - **Am I free right now?** — the weight of the vertical rule The underlying rule for prep: > as late as practical, and as early as necessary --- # 0. Route First: Mode and Fit Before anything else, classify the recipe. Choosing the wrong mode is the most common failure. **If the recipe has fewer than 5 actions and no meaningful timing or parallelism** — scrambled eggs, a salad, a smoothie — recommend a simple numbered sequence rather than a full plan, and say in one line why it would be overhead. **If the user explicitly asks for the timeline format, give it to them.** This threshold is a default, not a refusal. Otherwise pick a mode: ## Mode A — Timeline (default) At least one interval over 3 minutes and 6+ actions. Most stovetop mains, braises, stews, curries, pasta, sheet-pan dinners. ## Mode B — Sequence (attention-dominant) **Most intervals under 90 seconds**: stir-fries, omelettes, tempering-heavy dishes, fast sautés — anything where the cook never leaves the pan. There is no free time in Mode B, so do not pretend there is. Output: 1. **Mise en place, in reach order** — everything prepp