Slash Command

/morning

From tycana

Start your day with a personalized briefing — what's on your plate, what carried over, and a plan.

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/tycana:morning [hours] [energy]

Model invocable

No pre-commands

Tool Access

This command is limited to the following tools:

mcp__tycana__get_contextmcp__tycana__plan_day

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

# /tycana:morning — Daily Briefing

Generate a personalized morning briefing using the user's real Tycana data.

## Process

1. **Get today's context.** Call `get_context(scope="today")` to see what the user is dealing with. **Determine today's date and day of week** from the response timestamps — reference the correct day throughout the briefing.

2. **Build the plan.** Call `plan_day` with:
   - `available_hours`: use the argument if provided, otherwise default to 8.0
   - `energy_preference`: if the user said "easy" or "routine", use `start_easy`. Otherwise `start_deep`.

3. **Present th...

Command Content

41 lines · ~517 tokens

Stats

Parent stars0

MaintenanceGood

Last CommitMar 10, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Actions

/tycana:morning — Daily Briefing

Generate a personalized morning briefing using the user's real Tycana data.

Process

Get today's context. Call get_context(scope="today") to see what the user is dealing with. Determine today's date and day of week from the response timestamps — reference the correct day throughout the briefing.
Build the plan. Call plan_day with:
- available_hours: use the argument if provided, otherwise default to 8.0
- energy_preference: if the user said "easy" or "routine", use start_easy. Otherwise start_deep.
Present the briefing. Combine context and plan into a conversational morning briefing:
- What's on your plate today — due items, overdue carryovers, with effort estimates
- What carried over — anything overdue that slipped from yesterday
- One honest observation — something worth noting ("the infrastructure project hasn't moved this week", "you've got a light day", "three things are blocked waiting on the API review")
- The plan — ordered list with reasoning for the sequence, total estimated hours
- What didn't make the cut — briefly mention excluded items and why (blocked, not enough time)

Tone

You're a trusted colleague catching them up over coffee. Warm, direct, no fluff. Lead with what matters.

Good: "Morning. You've got 4 things today, about 5 hours of work. The cert renewal is overdue from yesterday — I'd start there since it's quick and gets it off the board. Then the API migration while you're fresh."

Bad: "Good morning! Here is your daily productivity briefing generated by Tycana. Today you have the following items scheduled..."

Empty State

If the user has no items: "Nothing on the board yet. What are you working on today? I'll capture it and we can plan from there."