Weekly Planner Assistant

The Problem

A common issue in weekly planning is fragmented records: what was planned today, what was completed, and which task slipped forward often stay scattered across chats, notes, and reminders. Without a shared structure, it is hard to answer quick questions such as what remains today, what the overall completion rate is, or how a project progressed this week.

How the Skill Works

Weekly Planner Assistant treats plans, completions, and reflections as the core weekly records, organized by date, project, and category.

• Daily logging: captures task content, priority, category (work, study, health, other), and date into local files, usually under ./weekly-plans/, with one JSON file per week.
• Flexible adjustments: supports editing tasks, reverting completions, changing dates, and soft-deleting plans to match real changes.
• On-demand queries: checks today’s tasks, weekly progress, or completion status for a given category, then presents the results as a timeline.
• Report generation: can trigger a workday report at 5:00 p.m. on weekdays and a weekly summary at 8:00 p.m. on Sunday, with manual requests also supported.
• Data operations: CRUD and export are mainly handled by scripts/weekly_planner.py, using python-dateutil>=2.8.0 for date logic.

Boundaries and Notes

This skill fits weekly, trackable tasks and reflections, not a full project management system or long-term cross-month planning. It relies on local JSON files and script calls, so keep the ./weekly-plans/ directory and script access available; automatic reports depend on trigger-time checks, so confirm the scheduling method in real use.