planning

Coordinate weekly plans, daily routines, and priorities via Supabase REST API.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Cimminelli1982/crm-frontend --skill planning-cimminelli1982
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/Cimminelli1982/crm-frontend/tree/main/docs/openclaw-skills/planning
Command: npx skills add https://github.com/Cimminelli1982/crm-frontend --skill planning-cimminelli1982

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This planning skill helps individuals manage three levels of planning: weekly, daily, and priorities while keeping everything synchronized in a centralized store.

Core Features & Use Cases

  • Weekly planning with week_number, year, date_start, date_end, and notes.
  • Daily routine scheduling with day_of_week, time_slot, activity, category, and duration_min.
  • Priority tracking across scopes (day, week, month, year) with completion status and sortable order.
  • Sync and retrieval via Supabase REST API to support real-time updates and history.

Quick Start

Create an initial weekly plan, add daily routines for today, and start populating priorities to track progress.

Frequently Asked Questions about planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate weekly planning and daily scheduling using a centralized data store?

Coordinate weekly planning and daily scheduling by synchronizing your routines, time blocks, and priorities in a central data store. This approach uses the Supabase REST API to keep weekly plans, daily routines, and priority tracking aligned across all your personal productivity workflows.

Can I track priorities across different time horizons like day, week, month, and year?

Yes, you can track priorities across day, week, month, and year scopes. Priority tracking includes completion status and sortable order, allowing you to manage and synchronize goals across multiple time horizons within your centralized Supabase database.

Do I need Supabase to manage daily routine scheduling and time-blocking?

Yes, Supabase is required for daily routine scheduling and time-blocking. The system requires environment variables and specific Supabase tables including routine_schedule, weekly_plans, and priorities, using a REST interface for real-time data access and synchronization.

How does the Supabase REST API sync weekly plans and daily routines?

The Supabase REST API syncs weekly plans and daily routines by interfacing directly with the weekly_plans, routine_schedule, and priorities tables. This REST interface enables real-time updates, historical retrieval, and centralized synchronization for personal productivity workflows.

What data fields are needed to create a weekly plan with time-blocking?

Creating a weekly plan with time-blocking requires specific data fields including week_number, year, date_start, date_end, and notes for weekly plans. Daily routines require day_of_week, time_slot, activity, category, and duration_min fields stored in Supabase.

Is this centralized planning approach suitable for team projects needing synchronized plans?

Yes, this centralized planning approach suits team projects needing synchronized plans. By storing weekly plans, daily routines, and priorities in a shared Supabase data store, teams can coordinate schedules and track priorities across synchronized time horizons.