5 AI Prompts to Design Your Personal OS This Weekend

You can design a working first version of your personal OS in a single two-to-three hour session if you have the right prompts and honest inputs. Here are five prompts that cover the three layers of the 3-Layer framework — values, systems, and rituals — in sequence.

Run them in order. The outputs of earlier prompts become inputs for later ones.

Prompt 1: Excavate Your Operative Values From Your Calendar

This prompt works best with real data. Before running it, pull your calendar or a rough time log from the last 30–90 days.

Here is how I actually spent my time over the last [timeframe] by category:
[list categories with approximate percentage or hours, e.g.:
- Reactive email/Slack: 30%
- Meetings: 25%
- Deep work / focused project work: 20%
- Administrative tasks: 15%
- Strategic thinking / planning: 10%]

My job / work context is: [brief description]
What I say my priorities are: [list your stated priorities]

Based on the behavioral data, what do I appear to actually value most?
Where is the largest gap between my stated priorities and how I spend time?
What does this suggest my operative values really are?

What you get: a diagnostic that surfaces the values your behavior is already serving, and a direct confrontation with any gaps between intention and reality. Do not defend yourself against the analysis — use it.

Prompt 2: Audit Your Current Systems for Gaps and Conflicts

Take 20 minutes to list every recurring process you use before running this prompt. Include tools, routines, and protocols you use without thinking about them.

Here are my operative values (from the previous analysis):
[list 3–5 operative values as behavioral commitments]

Here are my current recurring systems:
[list each with a one-line description, e.g.:
- Task management: Todoist, reviewed inconsistently, no clear priority method
- Email: checked continuously throughout the day
- Note-taking: Apple Notes, unorganized, rarely reviewed
- Planning: occasional weekly review on Sundays, often skipped]

For each system, identify:
1. Which operative value it serves (or doesn't)
2. Any systems that create conflicts with each other
3. What is missing — values with no corresponding system
4. What I should consider removing because it adds overhead without serving a value

What you get: a gap analysis that shows you exactly where your current system architecture is misaligned with your values, and where new systems are needed versus where existing ones should be removed.

Prompt 3: Design Your Minimal System Stack

Use the gaps and conflicts identified in Prompt 2 as input here.

Based on these operative values:
[list]

And these gaps identified in my current systems:
[list gaps from Prompt 2]

Help me design a minimal but complete system stack for the following categories:
- Task management and prioritization
- Information capture and retrieval
- Communication protocol
- Planning at daily and weekly levels

For each system, I need:
- The design principle (what it is optimized for)
- The minimum viable implementation
- How it connects to a specific operative value
Keep each system as simple as possible.

What you get: a redesigned Layer 2 that is coherent with your actual values and stripped of components that were adding overhead without serving a clear purpose.

Prompt 4: Design Your Ritual Stack

I need to design three core rituals for my personal OS:
1. A morning planning ritual (target: 10–15 minutes)
2. An end-of-day shutdown ritual (target: 10 minutes)
3. A weekly review ritual (target: 30–45 minutes)

My operative values are: [list]
My system stack includes: [brief list from Prompt 3]
My typical workday starts at [time] and ends at [time].
My most cognitively productive hours are: [morning/afternoon/evening]

For each ritual:
- Give me a step-by-step structure with time estimates per step
- Specify the output artifact or deliverable the ritual produces
- Identify the existing behavior I should anchor it to

What you get: a concrete ritual design for each of the three core rituals, with implementation intentions built in (the anchor behavior functions as the if-then trigger).

Prompt 5: Run a Coherence Check on the Full OS

Use this prompt after completing the first four to check whether the three layers are actually integrated.

Here is my personal OS first draft:

VALUES LAYER:
[list your 3–5 operative values as behavioral commitments]

SYSTEMS LAYER:
[list your systems from Prompt 3]

RITUALS LAYER:
[list your three rituals from Prompt 4]

Please check:
1. Does every system trace clearly to a value? If not, which ones don't?
2. Does every ritual activate at least one system? If not, which ones don't?
3. Are there any coherence conflicts — where two components make incompatible demands?
4. What is the most likely single point of failure in the first 30 days?
5. What one change would most improve the overall design?

What you get: an integrated design review that catches the gaps and conflicts that are easy to miss when you are building each layer in sequence.

After the Session

The output of these five prompts is a first draft, not a final OS. Run it for 30 days before revising any core component.

At the 30-day mark, add one more prompt: paste in your notes about what worked and what did not, and ask for an analysis of whether the friction you experienced points to a values issue, a systems issue, or a rituals issue. That distinction will tell you which layer to adjust.

Your next step: Block two hours this weekend, gather your calendar data, and run Prompt 1. The values analysis alone will tell you something useful about your current priorities that is worth knowing.

Related:

• The Complete Guide to Personal Operating System Design
• How to Design Your Personal OS in 5 Steps
• The 3-Layer Personal OS Framework Explained
• The Complete Guide to Daily Planning Ritual with AI

Tags: AI prompts personal OS, personal operating system design prompts, Claude productivity prompts, AI planning workflow, personal OS quick win