skills/reformcue-routine-builder/references/routine-assembly.md

# Routine assembly

Start from the user’s target duration, explicit exclusions, difficulty, focus, and available move IDs. Allocate time to work intervals first, then include every transition, setup, recovery, and side rest explicitly. Use exact integer seconds and validate the expanded duration before presenting a save option.

Use the move’s difficulty-specific spring preset when it exists; otherwise use its default and let validation surface a warning. A move interval cannot be represented by an arbitrary name. A transition may have a short label without a move ID, but it must remain an explicit transition interval.

Keep repeated moves intentional and bounded. Avoid long accidental runs, unexplained adjacent transitions, and one-sided split work. A fresh routine can echo historical structure without copying a prior sequence verbatim. If a small library makes a requested structure impossible, explain the tradeoff instead of inventing content.