Helps managers cut through noise and identify their highest-leverage actions for the day or week. Aggregates signals from calendar, triage, team context, and OKRs/goals. Presents a suggested focus list grouped by urgency, importance, and investment. The manager reviews and adjusts. Supports effective execution and prioritisation.
Principle: "You are responsible." The skill proposes, the manager decides. This is not a task manager. It's a thinking partner for prioritisation.
Aggregates signals from multiple sources to surface the manager's highest-leverage actions.
If any MCP connector is unavailable, follow the connector unavailability protocol in ../../references/operating-principles.md.
Ask or infer whether this is a daily or weekly plan:
Before gathering signals, load the manager's goals. These are the lens through which everything gets prioritised.
From manager-context/manager-goals.md:
From Notion/Drive (if goals location is known):
If no goals are found:
⚠️ I don't have your goals on file. Without them I can prioritise by urgency, but not by impact alignment.
Run /setup or tell me your current OKRs so I can connect your priorities to what matters most.
Pull from multiple sources:
Calendar (today or this week):
Triage results (if /triage-messages was recently run):
Manager Context (from manager-context/):
triage-rules.mdNotion:
Slack:
Group everything into three categories (inspired by Eisenhower):
🔴 Urgent: Time-Sensitive Decisions Things where someone is blocked or a deadline is imminent:
🟡 Important: High-Impact Work Things that move OKRs and team goals forward:
🟢 Invest: Development & Strategic Thinking Things that compound over time but rarely feel urgent:
Read references/output-template.md for the full output template structure.
Here's a suggested priority plan. This is a starting point. Adjust based on your judgment. Want me to:
- Move anything between categories?
- Add something I missed?
- Prep for any of these items?
Read ../../references/operating-principles.md for shared operating principles (data scope, DM flagging, signals vs diagnoses, connector unavailability).
Additional notes specific to this skill:
manager-context/management-framework.md) an action supports.