Focus Blocks Builder

Purpose

Transform scattered, reactive days into intentional, focused ones by creating a personalized time-blocking schedule. This skill maps your natural energy patterns to your most important work, ensuring deep work happens when you're at your best.

When to Use

Use this Skill when you need to:

• Create a weekly schedule that supports deep work
• Figure out when to schedule different types of tasks
• Stop letting meetings and interruptions consume your best hours
• Build a sustainable daily rhythm that actually sticks
• Recover from a period of scattered, unproductive days

Step-by-Step Process

Step 1: Map Your Energy Patterns

Understand when your brain is at its best for different types of work.

Ask the user:

• "Think about a recent week. When did you feel most mentally sharp and focused? (Morning? After lunch? Evening?)"
• "When do you typically hit an energy wall or feel scattered?"
• "What type of work feels easiest vs. hardest at different times?"

Guide them to identify:

• Peak hours: Best for creative, complex, or cognitively demanding work
• Maintenance hours: Good for emails, meetings, admin tasks
• Recovery windows: Natural break times, energy dips

Output Variable: energy_map

Step 2: Audit Current Time Usage

Understand where time is currently going.

Ask the user:

• "How much of your day is typically in meetings?"
• "When do most interruptions happen?"
• "What recurring commitments can't be moved?"

Identify:

• Fixed commitments (meetings, standups, etc.)
• Controllable time blocks
• Current deep work windows (if any)
• Main time drains

Output Variable: time_audit Context Used: energy_map

Step 3: Define Focus Block Requirements

Determine what focused work needs to happen.

Ask the user:

• "What types of work require your deepest focus? (coding, writing, strategy, etc.)"
• "How long can you realistically focus before needing a break?"
• "What's your minimum viable focus block—the shortest time that's still productive?"

Define:

• Types of deep work needed
• Ideal focus block duration (typically 60-90 min)
• Minimum focus block (typically 25-45 min)
• Daily deep work goal (hours)

Output Variable: focus_requirements Context Used: energy_map, time_audit

Step 4: Design Protection Protocols

Create boundaries that protect focus time.

Ask the user:

• "What are your top 3 sources of interruption?"
• "Which interruptions can you eliminate vs. need to manage?"
• "What signals can you use to show you're in focus mode?"

Build protocols for:

• Notification management
• Communication boundaries (when to check email/Slack)
• Physical/environmental signals
• Interruption handling scripts

Output Variable: protection_protocols

Step 5: Generate Weekly Focus Block Template

Create the final schedule.

Using all gathered information, create a document with:

Weekly Focus Block Schedule

| Time | Monday | Tuesday | Wednesday | Thursday | Friday | |------|--------|---------|-----------|----------|--------| | [Peak hours] | Focus Block | Focus Block | Focus Block | Focus Block | Focus Block | | [Maintenance hours] | Meetings/Admin | Meetings/Admin | Meetings/Admin | Meetings/Admin | Weekly Reset | | [Recovery windows] | Break | Break | Break | Break | Break |

Daily Rhythm Template:

• [Time]: Morning startup ritual (15 min)
• [Peak time]: Focus Block 1 - [Work type]
• [After peak]: Short break + transition
• [Mid-day]: Batch communications
• [Afternoon]: Focus Block 2 or meetings
• [End of day]: Shutdown ritual (10 min)

Protection Protocols:

• [Protocol 1]
• [Protocol 2]
• [Protocol 3]

Context Used: All previous steps

Output Format

Your Focus Block System

Energy Pattern Summary:

• Peak focus hours: [times]
• Good for meetings/admin: [times]
• Natural break times: [times]

Weekly Template: [Table with time-blocked schedule]

Daily Rhythm: [Specific daily structure]

Protection Protocols: [List of boundaries and systems]

Getting Started:

1. [First step to implement]
2. [Second step]
3. [Third step]

Tools

• basile_create_document - Creates the weekly template document in user's space

Example

Input: Remote developer who does their best work in mornings but has meetings scattered throughout the day Output: A weekly schedule with protected morning focus blocks (9-11:30am), batched meetings in afternoon (1-4pm), and protocols for managing Slack notifications during deep work.