/week-plan

name: week-plan
description: "Set the week's priorities against goals, calendar shape and task effort. Use when the user says 'plan my week', 'what should I focus on this week', or on their first working day. Also use proactively at the first session of a new week. Not for reviewing the week just past; use `week-review`."
context: fork

Purpose

Set priorities and plan the week ahead. Now with **intelligent priority suggestions** based on quarterly goals, calendar capacity, and task effort classification.

Usage

• `/week-plan` — Plan current week (or next week if run on the last working day or a non-working day)
• `/week-plan next` — Explicitly plan next week
• `/week-plan current` — Force planning current week

---

When to Use

**Best times:**

• **First working day, before work** - Before diving into daily work
• **Last working day, after work** - Set up next week while context is fresh
• **Evening before the first working day** - Plan before the week begins

Read `working_week.days` in `System/user-profile.yaml` before deciding which days are first, last, or outside the working week.

---

Step 1: Determine Target Week

Calculate target week (current or next) based on day of week and user parameter.

---

Step 2: Context Gathering (ENHANCED)

Gather comprehensive context to inform **intelligent priority suggestions**.

2.1 Last Week's Review

Check for `00-Inbox/Weekly_Synthesis_[last-monday].md`:

• "Next Week" section → Suggested priorities
• "Carried Over" section → Unfinished tasks
• "Blocked Items" → Things that need resolution
• "Learnings" → Insights to apply

2.2 Quarterly Goals Status

Use: get_quarterly_goals()
Use: get_goal_status(goal_id) for each goal

For each goal, get:

• Current progress (concrete: "2 of 5 milestones complete")
• Linked priorities count
• Weeks since last activity
• Stall warnings

**Identify goals needing attention:**

• Goals with no linked priorities (orphaned)
• Goals with no activity in 2+ weeks (stalled)
• Goals behind expected pace

2.3 Open Tasks and Projects

Use: list_tasks(include_done=False)

Get all open tasks and:

• Classify by effort (deep_work / medium / quick)
• Group by pillar alignment
• Identify P0/P1 items
• Find tasks that could advance stalled goals

2.4 Calendar Shape Analysis (NEW)

Use: analyze_calendar_capacity(days_ahead=7, events=[...from calendar MCP...])

Understand the **shape of the week**:

| Day | Type | Largest Block | Best For | |-----|------|---------------|----------| | Mon | Stacked (7 meetings) | 45 min | Quick tasks only | | Tue | Moderate (4 meetings) | 90 min | Medium tasks | | Wed | **Open** (2 meetings) | **3 hours** | **Deep work day** ✨ | | Thu | Stacked (6 meetings) | 30 min | Quick tasks only | | Fri | Moderate (3 meetings) | 2 hours | Medium tasks, wrap-up |

**Week capacity summary:**

• Deep work opportunities: {{count}} days with 2+ hour blocks
• Total deep work hours available: ~{{X}} hours
• Stacked days to avoid scheduling deep work: {{list}}

2.5 Task-to-Time Matching (NEW)

Use: classify_task_effort(title) for key tasks
Use: suggest_task_scheduling(include_all_tasks=True, calendar_events=[...])

Get intelligent matching:

• Which tasks need deep work time?
• Which can fit in gaps?
• Are there enough slots for all deep work?

**Capacity check:**

> "You have 5 deep work tasks totaling ~12 hours. > You have 2 open days with ~6 hours of deep work capacity. > > ⚠️ **Capacity gap:** Consider deferring 2 deep work items or protecting more time."

2.6 Semantic Goal Intelligence (if QMD available)

**Check if semantic search is available** by looking for `qmd` in PATH.

If available, enhance priority suggestions with meaning-based analysis:

1. **Find stale goals with hidden activity:** For each stalled quarterly goal, search:

   qmd query "goal description/success criteria" --limit 5

against recent tasks and meeting notes. Sometimes goals appear stalled because related work wasn't explicitly linked.

• Example: Goal "Build partner ecosystem" shows no linked tasks, but QMD finds 3 meetings about "integration partnerships" and a task about "API documentation for vendors."

2. **Suggest priorities that move stalled goals:** For goals with no recent activity:

   qmd query "goal title concepts" --limit 3

against open tasks. Surface tasks that could advance the goal semantically.

• "You have an open task 'Review vendor onboarding flow' — this could advance your stalled goal 'Build partner ecosystem'"

3. **Detect priority conflicts:** Search for semantic overlap between candidate priorities:

   qmd query "priority A description" --limit 3

If two priorities are semantically very similar, suggest merging them.

**Integration:** Fold findings into the "Intelligent Priority Suggestions" in Step 3. Label semantic discoveries: "🔍 *Detected via semantic search*"

**If QMD unavailable:** Skip silently. Priority suggestions still work from explicit goal links.

2.7 Commitments and Follow-ups

Use: get_commitments_due(date_range="this_week")

Surface things you've committed to that are due this week.

---

Step 3: Intelligent Priority Suggestions (NEW)

**Don't just ask "What are your Top 3?" — Suggest priorities based on analysis.**

3.1 Generate Suggestions

Based on the gathered context, generate 4-5 suggested priorities:

**Goal-driven suggestions:**

• "Goal X has no activity in 3 weeks. Suggested priority: {{specific work that advances it}}"
• "Goal Y is at 2 of 5 milestones with 6 weeks left. Suggested priority: Complete milestone 3"

**Commitment-driven suggestions:**

• "You committed to {{X}} with {{person}} — due this week"

**Carried-over suggestions:**

• "{{Priority}} carried over from last week — still important?"

**Calendar-aware suggestions:**

• "You have a deep work day Wednesday — good time for {{specific deep work task}}"
• "Friday is light — good f