communicate
Draft a professional communication (Slack, email, or async doc) with context from the vault
Daily planning - morning (fill journal, plan focus) or evening (close-out, prep tomorrow)
$ npx -y skills add aleksander-dytko/ai-pm-workspace --skill today --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/todayContext preview
The summary Claude sees to decide when to auto-load this skill.
Daily planning - morning (fill journal, plan focus) or evening (close-out, prep tomorrow)
name: today description: Daily planning - morning (fill journal, plan focus) or evening (close-out, prep tomorrow) argument-hint: "[morning | evening]"
You help the user run a morning ritual (plan focus items) or an evening ritual (close-out and prep tomorrow). Both modes write to the daily journal and to `Dashboard/tasks.md`.
Check `$ARGUMENTS`:
If unclear, ask the user once: "Morning planning or evening close-out?"
---
Do ALL of these before asking anything:
Use yesterday's values as hints.
1. **Mood** (1-10) - hint with yesterday's mood. Options: "3-4 (rough)", "5-6 (okay)", "7-8 (good)", "9-10 (great)" 2. **Energy** (1-10) - hint with yesterday's energy. Options: "3-4 (low)", "5-6 (medium)", "7-8 (high)", "9-10 (full power)" 3. **Self-care**: "What did you do for yourself before work?" Options: "Exercise / run", "Walk", "Nothing special" 4. **Yesterday evening**: "How was yesterday after work?" Options: "Relaxing, no stress", "Active (workout / outing)", "Stressful / tough"
Update the journal's frontmatter `mood` and `energy`, and fill yesterday + today personal sections.
If mood < 6 or energy < 6: set `low_energy = true`.
Ask the user to paste their calendar for the day (screenshot or text list).
After receiving the calendar:
**Suggest max 3 focus items** for "My focus today (max 3)":
**Capacity rules:**
Present the plan and ask: "Anything to change? If OK, I'll update your journal and mark tasks as today's focus."
Write a short conversational summary, **not** a code-fenced template card. Two or three sentences max. Cover: day/date + mood/energy, the focus item(s) in plain prose, how many tasks got the 🎯 marker, a backtick-wrapped path to the updated journal, and a one-line nudge to run `/today evening` later.
Example tone (do not copy verbatim):
> Planning done for Tuesday, 21 April - running at 4/10 mood and 4/10 energy, with ~5h of focus time around three meetings. Today's single focus: finish the sequencing decision note (overdue from Friday). I marked it 🎯 in `Dashboard/tasks.md` and updated `journals/2026/04-April/21-04-2026.md`. Catch you this evening - run `/today evening` to close out.
---
If today's journal doesn't exist, create it from `templates/daily-note.md`.
1. **Energy + mood at end of day** (0-10 each): "How did you end the day?" 2. **What did you finish today?** (free text) - suggest based on focus items + 🎯 completions as hints. 3. **What will you start with tomorrow?** (free text - one thing). 4. **Anything else to capture?** (optional free text; user can skip).
Update today's journal - find or append the `## End of Day` section:
## End of Day - Energy: [Q1 energy]/10 | Mood: [Q1 mood]/10 - Today I finished: - [user's answer to Q2] - Tomorrow I start with: - [user's answer to Q3] - Work closed.
If Q4 had content, append as a note below. Do NOT update frontmatter `mood` / `energy` - those reflect start-of-day state.
If unprocessed meetings exist from today:
Unprocessed meetings from today: - [Title] ([time or filename]) Run `/meeting` to process them.
If any 🎯 tasks are still open (not completed):
Open focus tasks (will carry over): - [task] - [task]
Write a short conversational close-out, **not** a code-fenced template card. Two or three sentences: end-of-day mood/energy, what got done (brief), what starts tomorrow, and any carry-overs (unprocessed meetings or open 🎯 tasks). Use backtick-wrapped paths for any file references.
Example tone (do not copy verbatim):
> Day closed - ended at 6/10 mood, 5/10 energy. Shipped the sequencing decision and got half of the auth write-up drafted. Tomorrow starts with finishing that write-up. One unprocessed meeting from today (`Meetings/2026-04-21 - Design review.md`) -
A structured, Claude-Code-ready workspace for product managers, designers, and other PM-adjacent roles. Your notes become the persistent memory; Claude Code becomes the executor. This is a template.
Draft a professional communication (Slack, email, or async doc) with context from the vault
Produce a sourced competitive matrix for a focused research question
Turn an idea into a structured epic draft using templates/epic-template.md
Make a product decision with full context from the vault and available sources
Interactive 8-module learning path for the shipped skills, role-adaptive
Process raw meeting notes into structured meeting note with in-repo tasks