| name | habit-builder |
| description | Design habits and build a calendar schedule using an evidence-based Behavior Change Framework. Use when you want to build a new habit, create a daily or weekly routine, schedule recurring goals, design a behavior loop, write an implementation contract, export a habit plan as an ics calendar file, add habits to Google Calendar, break a bad habit, start a morning routine, or apply the 4-law framework (obvious, attractive, easy, satisfying) to any behavior change goal. |
| argument-hint | Optional: describe the habit or goal you want to work on (e.g., 'morning exercise', 'read every evening') |
| user-invocable | true |
habit-builder
A guided, evidence-based workflow for designing sustainable habits and scheduling them on your calendar.
When to Use
- You want to build or strengthen a habit
- You want to break an existing bad habit
- You want a repeatable routine (morning, evening, weekly, etc.)
- You want to export your habit plan as a calendar file (
.ics) for Apple Calendar, Outlook, or other apps
- You want Google Calendar deep links to add events with one click
- You need a structured way to apply behavioral science to a goal
Workflow Overview
The skill runs in four sequential phases. Work through each phase with the user before moving to the next.
| Phase | Goal |
|---|
| 1. Identity & Audit | Establish who the user wants to become; identify existing anchor routines |
| 2. Habit Design | Apply the 4-law framework to each desired behavior |
| 3. Schedule | Assign time, days, and duration to each habit |
| 4. Output | Generate .ics file and/or Google Calendar deep links |
Phase 1 — Identity & Audit
Step 1.1 — Identity Statement
Ask the user:
"Who do you want to become? Describe it as an identity, not an outcome. For example: 'I am someone who moves their body every morning' rather than 'I want to lose 5kg'."
Record their Identity Statement. This frames every habit as evidence of an identity they are building.
Step 1.2 — Behavior Audit
Ask the user:
"List 3–5 things you do every single day without thinking — morning or evening routines, meals, commutes, anything consistent. These will become your anchor routines."
Record each anchor routine. These will be used in Phase 2 for Habit Anchoring.
Phase 2 — Habit Design
For each habit the user wants to build, work through all four laws. Load ../../habit-builder/references/four-laws.md for detailed prompts, examples, and explanations.
Law 1 — Make It Obvious (Cue)
- Identify the cue that will trigger the behavior
- Write an Implementation Contract:
"I will [BEHAVIOR] at [TIME] in [LOCATION]"
- Optionally use Habit Anchoring:
"After I [ANCHOR ROUTINE], I will [NEW HABIT]"
Law 2 — Make It Attractive (Craving)
- Identify what the user craves or finds rewarding about the behavior
- Pair the habit with something enjoyable (temptation bundling)
- Connect the habit back to the Identity Statement
Law 3 — Make It Easy (Response)
- Scale the habit down to its Minimum Viable Behavior (≤2 minutes)
- Identify and eliminate friction points
- Suggest Context Architecture changes (environment design)
Law 4 — Make It Satisfying (Reward)
- Define an immediate reward the user can experience right after the behavior
- Suggest a simple tracking method (checkbox, journal line, streak)
Phase 3 — Schedule
For each designed habit, collect:
| Field | Question to Ask |
|---|
start_date | "When do you want to start? (YYYY-MM-DD)" |
start_time | "What time of day? (HH:MM, 24-hour)" |
duration_minutes | "How long is the Minimum Viable Behavior in minutes?" |
frequency | "Daily, weekdays only, or specific days of the week?" |
days | If specific days: "Which days? (e.g., Mon/Wed/Fri)" |
count | "How many repetitions before you revisit? Research suggests 66 repetitions to form a habit. Alternatively, set an end date." |
Summarize all habits in a schedule table before proceeding to output.
Phase 4 — Output
Offer the user both options:
Option A — .ics Calendar File
Run the generation script:
python habit-builder/scripts/generate-ics.py
Or ask the user to save their habit data as habits.json and run the script. See ../../habit-builder/scripts/generate-ics.py for the input schema.
The script outputs habits.ics in the current directory. The user can then:
- Double-click to import into Apple Calendar
- Import via File → Import in Google Calendar
- Import into Outlook, Fantastical, Notion Calendar, or any RFC 5545-compliant app
Option B — Google Calendar Deep Links
For each habit, construct a Google Calendar deep link using the template in ../../habit-builder/references/google-calendar-links.md.
Provide one link per habit. Each link opens a pre-filled event creation page — no API key or login required in advance.
Final Output
After all phases, produce:
- A filled Habit Design Plan using the template in
../../habit-builder/assets/habit-design-template.md
- The
habits.json content (so the user can save it and re-run the script)
- The generated
.ics content inline (fenced code block), OR a confirmation that the script was run
- Google Calendar deep links (one per habit)
References
