weekly-plan

Plan Weekly P-Tasks

You help plan the upcoming week's P-Tasks (3-5 meaty priorities) with an overplanning challenge and triage of the in-repo task list.

Input

The user invokes this skill (typically Sunday evening or Monday morning) without arguments, or with context like "plan my week".

The user may:

• Let you suggest P-tasks based on context
• Propose their own P-task list for validation
• Provide calendar context (screenshot or text)

Workflow

1. Review previous week

Read Dashboard/Weekly P-Tasks.md. Find the most recent week's P-tasks.

If last week's P-tasks don't have completion markers, prompt the user:

Let's review last week before planning this week:

P1: [Task]
- Status? (Completed / Partial / Not done)
- If completed: results?
- If partial or not done: what blocked it?

P2: [Task]
...

Wait for review, then update last week's entry with markers:

• ✅ completed (add a note about results)
• 🔄 partial / carry over (add a note about what's left)
• ❌ not started / deprioritized (add a note about why)

Compute last week's completion rate (completed / total) - used for the overplanning check.

2. Analyze recent daily notes

Read the last 7 days from journals/YYYY/MM-Month/.

Identify:

• Carryover items mentioned but not finished.
• Energy/mood patterns from frontmatter and content:
  • Declining trend (e.g., 7 → 5).
  • Mentions of overwork, burnout, feeling overwhelmed.
• Recurring themes or blockers.
• Weekly review notes (Friday entries).

Capacity adjustment:

• Energy < 6 or declining trend → suggest 3-4 P-tasks max.
• "Feeling overwhelmed" appears → reduce scope aggressively.

3. Calendar context

If the user hasn't shared their calendar, ask: "Share your calendar for this week or highlight key deadlines."

Look for hard deadlines (presentations, demos, deliverables), meeting density, and time-sensitive milestones.

If calendar shows >50% meeting time: reduce P-task count and note reduced capacity.

4. Review recent meetings for follow-ups