5 AI Prompts for Life Domain Balance You Can Use This Week

The Season Concept works through a feedback loop: you invest in your Primary Domain, you check whether non-primary domains are holding their floors, you adjust. AI makes that loop faster and more honest.

These five prompts cover the key moments in a season. Each is designed to be used with your specific data—not as a generic reflection exercise, but as a structured analysis with your actual domain names, hours, and floors.

Prompt 1: Domain Mapping

Use this at the start of your first season, or when you suspect your existing domain map isn’t reflecting your actual life.

I want to build a personal life domain map for seasonal planning. Here's a brief description of my life and what matters most to me:
[2–4 sentences describing your situation: work, family, commitments, aspirations]

Please suggest an initial domain list of 6–8 areas. For each domain:
1. Why it warrants its own category rather than being part of another
2. What "thriving" looks like in one specific, observable sentence
3. What "neglected to the point of risk" looks like in one specific, observable sentence

After the list, identify any domain I likely missed based on what I described.

What to do with the output: Edit the suggestions based on your actual life. The AI’s list is a starting draft, not a final map. Remove domains that don’t feel meaningful; add anything it missed.

Prompt 2: Maintenance Floor Calibration

Use this when setting floors at the start of a season, or when a floor keeps getting violated and you suspect it’s set too high.

Here are my life domains and my current thinking on maintenance floors:
[list each domain with your proposed floor condition]

My Primary Domain this season is [domain] with a weekly time budget of approximately [X] hours.

For each floor, help me evaluate:
1. Is the floor specific and observable enough to confirm yes or no each week?
2. Is it realistic to maintain in a demanding week where my Primary Domain is taking priority?
3. Is it set at the right threshold—genuinely the minimum to prevent domain damage, not an aspirational goal?

Suggest revisions where the floor design is weak, and explain the reasoning.

What to do with the output: Use the revised floors as your season baseline. If the AI suggests a floor is unrealistically high, that’s important information—a floor you can’t hold will only produce guilt.

Prompt 3: Weekly Drift Check

Use this every Sunday (or whichever day opens your week). Takes 5–10 minutes.

It's week [X] of my [Primary Domain] season.

Here's how my time broke down this week (rough estimates by domain):
[list each domain and hours]

My Primary Domain budget was [X] hours. My maintenance floors are:
[list each domain floor]

Please:
1. Flag any domain at or below its maintenance floor
2. Identify if any domain has been below floor two or more consecutive weeks (I'll note that here: [any domains that were also below floor last week])
3. Suggest one specific scheduling adjustment for next week that protects my Primary Domain without letting any other domain fall further

What to do with the output: Make one scheduling change, not five. The prompt asks for a single adjustment deliberately—too many changes at once rarely stick.

Prompt 4: Mid-Season Correction

Use this if your season isn’t working as intended—either the Primary Domain isn’t getting its time, or a non-primary domain is in sustained difficulty.

I'm at week [X] of a [number]-week season. My Primary Domain is [domain] with a stated outcome goal of [goal].

Here's an honest mid-point assessment:
- Primary Domain progress: [what's happened, what hasn't]
- Which floors have held: [list]
- Which floors have struggled: [list with honest reason why]
- Whether there's been any external circumstance that's changed since the season started: [yes/no and brief description if yes]

Help me diagnose: is this a floor design problem, a scheduling problem, a season selection problem, or an external circumstances problem? For each issue, suggest the minimal structural change that addresses the root cause.

What to do with the output: A mid-season correction should be targeted—one or two specific changes, not a full season restart. If the assessment reveals the season was wrong from the start, it’s worth considering an early transition.

Prompt 5: Seasonal Transition Review

Use this at the 90-day mark, before selecting your next Primary Domain.

My [Primary Domain] season is ending. Here is a complete honest review:

Outcome goal was: [specific goal you set at season start]
What actually happened: [honest assessment—achieved, partially achieved, or missed, and why]

Floor audit (each domain: held / struggled / breached):
[list each domain with honest assessment]

Current state of each domain in one sentence:
[list all domains]

Life circumstances that may affect the next season: [anything relevant—job changes, relationship changes, health, travel, etc.]

Based on this, please:
1. Recommend the next Primary Domain with specific reasoning
2. Identify any floors that should be adjusted up or down based on what I learned
3. Note any domain that appears to be in a gradual decline that a floor alone won't address
4. Suggest one structural change for the next season setup that would improve on what went wrong this time

What to do with the output: Use the recommendations as inputs to your own decision, not as a final answer. You know your life circumstances more completely than any AI prompt can capture. The prompt’s value is in surfacing patterns and tradeoffs you might rationalize away on your own.

The prompt that delivers the most ongoing value for the least effort is Prompt 3—the weekly drift check. If you run nothing else from this list consistently, run that one.

Your immediate action: run Prompt 1 today and draft your first domain map.

Related:

• The Complete Guide to Life Domain Balance with AI
• How to Balance Life Domains with AI
• The Life Domain Balance Framework with AI

Tags: AI prompts, life domain balance, seasonal planning, Claude prompts, life design prompts