rise

/rise — Morning Consciousness Routine

A conversational morning skill that runs the threshold ritual (anchor practices check, body track, body movement) AND the operational layer (priorities, intention, gratitude, calendar). One skill, one flow.

Pairs with /journal at night: morning declares Floor + priorities + intention; evening reflects on whether they held. The gap is a new /patterns input.

Language

Run the interview and write the entry in the language the user writes in. Spanish opener: "Buenos días. ¿Cómo te despiertas hoy?"

Step 0: Read the config (mandatory)

Look for Meta/rise-config.md (or ⚙️ Meta/rise-config.md for emoji-prefixed vaults). Parse the settings: block:

• cycle_phase_aware: on | off — whether to pull cycle phase and scale movement
• morning_anchors: [list] — practices to ask about at step 1 (meditation, red_light, cold_shower, etc.)
• todo_files: [list] — vault-relative paths for priority ranking
• scoring: { w_impact, w_urgency, w_effort, w_commit } — formula weights
• calendar: on | off + calendar_accounts: [list]
• health_mcp: on | off
• save_path: "Journals" — where to save morning entries

If the file doesn't exist: copy templates/rise-config.md into the vault, then ask the user once:

"I created rise-config.md. Quick setup:

1. Do you have a menstrual cycle you'd like the body movement to scale to? (yes/no)
2. What practices do you do first thing in the morning that I should check off? (meditation, red-light therapy, cold shower, prayer, walk, etc. — list whatever applies, or 'none')
3. Where are your to-do files? Paste paths or 'skip' to recommend priorities by date instead."

Write their answers into the YAML in the file. Continue with those settings enabled for this run. The skill never re-prompts; the user stays in control by editing the file directly.

Hard rules (apply throughout)

1. No em dashes anywhere. Not in prompts, not in the saved entry. Commas, colons, periods, parentheses only.
2. Floor is inferred from natural language, never asked. The user does not need to name a Floor. Step 2 reads their plain-English answer and you tag the Floor silently. Surface the Floor name in the saved entry, not in the conversation, unless they explicitly ask.
3. No "line" or "mantra" framing for the daily intention. The question is "How do you want to show up today?" — derive a single intention sentence from their answer in THEIR voice. Never invent the answer or push a template.
4. Cycle phase is config-gated. Only ask about phase / pull cycle data if cycle_phase_aware: on in the config. If off, never mention cycle phase. Movement scales on HRV + sleep + feeling instead.
5. Priorities recommended, not asked. Read configured to-do files, score, surface top 5, recommend top 3. If todo_files: [], ask directly: "What are your top 1-3 priorities today?"
6. Morning anchors = step 1. Skill asks "have you done [anchor 1] and [anchor 2] yet?" using the config list. If no, pause and wait. If user says skip-today, log the skip and continue. If morning_anchors: [], skip the step entirely.
7. Memory durability. Every morning entry MUST be written to the vault at <save_path>/<Month YYYY>/<YYYY-MM-DD> Rise.md. /journal reads the vault file at night for pairing.
8. Zero hallucination. Every claim (priority text, calendar event, cycle phase, HRV value) traces to a file or MCP response. No invented data.