SousMeow
Personal Projects Beginner Available now Free

Set a Thirty-Day Goal

Set one thirty-day finish line and the weekly rhythm to hit it.

Thirty days is long enough to see progress and short enough to stay honest. This Cookbook helps you choose one goal, define done, split the month into four weeks, place small actions on available days, prepare if-then obstacle moves, and pack a compact goal card. Enter only the goal, reason, available days, obstacles, and support you truly have. Every prompt tells the assistant to invent nothing about your calendar, motivation, tools, or helpers. You leave with a thirty-day card you can reread each week.

Made for
People choosing one personal goal for the next thirty days without turning it into a full project plan
You leave with
one-goal statement, four-week path, weekly actions, if-then obstacle plan, weekly check, and thirty-day goal card
Time
about 22 minutes
Steps
6 guided steps
Requires
any AI you already use (a free chat account is usually enough); sample answers included where available
Completed runs
389 (demo metric)
Average rating
4.9 / 5 (demo metric)

Also in Start Here Selected by SousMeow Recently Added Under 30 Minutes Deep Workflows

Start free to begin

Have an account? Sign in.

Stages

3 stages in sequence
  1. 1

    Choose

    Lock one thirty-day finish line before planning actions.

    1 step
  2. 2

    Plan

    Split the month, place actions, plan obstacles, and write a weekly check.

    4 steps
  3. 3

    Commit

    Pack the goal into a short card for the next thirty days.

    1 step

Workflow steps

6 steps · completed in order

Stage 1: Choose

  1. 1

    Lock one goal

    Turn the idea into one thirty-day goal with a clear finish line and scope cut.

    A thirty-day goal works best when it is one finish line, not a basket of improvements. This step names the goal, the reason thirty days matters, and what is not included. Common mistakes: adding a second goal, inventing motivation, or making done depend on perfect conditions. Need help if the AI expands it? Paste again and ask for one goal only. You are ready when the Day 30 proof is visible.

    • Only one goal The statement does not combine several personal goals.
    • Done is observable Day 30 completion can be checked from evidence.
    • Scope is cut The plan protects the month from extra ambitions.

Stage 2: Plan

  1. 2

    Split into four weeks

    Create a four-week path from start to proof without adding a bigger project plan.

    Thirty days is easier to hold when each week has a purpose. This step creates a simple month arc while keeping the goal smaller than a project roadmap. Common mistakes: planning exact dates not provided, overloading Week 1, or expanding the finish line. Need help if the AI makes a calendar? Paste again and ask for week labels only. You are ready when each week has one job.

    • Four weeks are present The path uses Week 1 through Week 4.
    • Evidence is weekly Each week has a simple proof item.
    • Goal stays small The scope guard prevents a full project plan.
  2. 3

    Place weekly actions

    Choose small actions that fit the available days and support already present.

    A month plan fails when actions assume more days, energy, or help than exist. This step turns the four-week path into repeatable actions that respect available days. Common mistakes: inventing exact schedules, adding supplies, or treating a missed day as failure. Need help if it overbooks you? Paste again and require the days-available number as a limit. You are ready when the week can survive a normal life.

    • Actions are small Weekly actions can happen inside normal available days.
    • Available days are respected The plan does not invent more days.
    • Support comes from facts No new helper, app, or supply appears.
  3. 4

    Name if-then obstacles

    Prepare simple if-then moves for the obstacles most likely to interrupt the month.

    Obstacles are easier to handle before they arrive. This step turns likely interruptions into small if-then choices, not self-criticism. Common mistakes: inventing dramatic problems, adding punishment, or solving everything with more time. Need help if the AI gets harsh? Paste again and ask for kind recovery language. You are ready when every obstacle has a next move.

    • Obstacles match pantry facts If-then rules come from obstacles you entered.
    • Recovery is kind and small Restart moves do not punish or expand the goal.
    • Support is not invented The ask uses only support already named.
  4. 5

    Write weekly check

    Create a short weekly review that uses evidence, adjustment, and one next action.

    A thirty-day goal needs a light check, not a giant tracking system. This step creates a weekly review that keeps the month honest and adjustable. Common mistakes: measuring only mood, inventing metrics, or making the check longer than the action. Need help if it becomes admin? Paste again and ask for five questions maximum. You are ready when the check takes a few minutes.

    • Check is lightweight Questions can be answered quickly each week.
    • Evidence matches done Recorded evidence proves progress toward the finish line.
    • Adjustment is practical The rule says when to keep, simplify, or use if-then moves.

Stage 3: Commit

  1. 6

    Pack thirty-day card

    Assemble the goal, reason, weekly rhythm, obstacle plan, and commitment line.

    A goal card is short enough to reread when the month gets messy. This step packs the approved pieces into one personal card without turning it into a full project plan. Common mistakes: adding new goals, promising perfect streaks, or hiding obstacles. Need help if the card grows? Paste again and ask for one screen. You are ready when the card can guide the next thirty days.

    • Card includes the finish line The single goal and done definition are easy to find.
    • Weekly rhythm is compact The card can be reread quickly during the month.
    • Commitment stays honest The final line does not promise perfect streaks or expanded scope.

Your information

6 details, answered once
  • Goal title Give the thirty-day goal a short name.
  • Why thirty days? Why this goal belongs in the next thirty days. Keep it honest and specific.
  • What counts as done? The personal finish line for Day 30. Make it observable.
  • Days available in the next 30 How many days you can realistically touch this goal. The plan will not invent more.
  • Likely obstacles What could interrupt the thirty-day rhythm?
  • Support you already have People, places, tools, reminders, supplies, or routines already available.

Finished files

What you export when every step is approved

One Markdown file per approved step, plus kit.html (opens in any browser, offline) and a README of what you approved.

  • kit.html Offline HTML reader for every approved step
  • 01-lock-one-goal.md Lock one goal
  • 02-split-into-four-weeks.md Split into four weeks
  • 03-place-weekly-actions.md Place weekly actions
  • 04-name-if-then-obstacles.md Name if-then obstacles
  • 05-write-weekly-check.md Write weekly check
  • 06-pack-thirty-day-card.md Pack thirty-day card
  • README.md Manifest of what you approved
Nearby guided projects you can start next
Personal Projects Available Finish a Personal Project Give a personal project a finish line and a first week of work. 9 steps · 70 min · Beginner · 4.7 ★ · Free