Finish a Personal Project
Give a personal project a finish line and a first week of work.
Personal projects slip when they stay vague, too big, or always almost ready. This Cookbook helps you name what done means, why now matters, what constraints are real, and which chunks belong in the first finished version. Enter only pantry facts about the project, deadline, hours, materials, and blockers. Every prompt tells the assistant to invent nothing about your schedule, budget, tools, or motivation beyond those facts. You leave with a first week of real moves and a finish checklist.
- Made for
- People with a meaningful personal project that keeps slipping
- You leave with
- done definition, why-now, constraints, chunk list, week sequence, risks, check-in template, first-week actions, finish checklist
- Time
- about 70 minutes
- Steps
- 9 guided steps
- Requires
- any AI you already use (a free chat account is usually enough); sample answers included where available
- Completed runs
- 312 (demo metric)
- Average rating
- 4.7 / 5 (demo metric)
Also in Start Here Selected by SousMeow Recently Added Deep Workflows
Have an account? Sign in.
Stages
3 stages in sequence-
13 steps
Aim
Define done, why, and constraints before planning the work.
-
23 steps
Plan
Break the project into chunks, sequence the weeks, and name risks.
-
33 steps
Finish
Set check-ins, choose first-week moves, and pack the closeout checklist.
Workflow steps
9 steps · completed in orderStage 1: Aim
-
1
Define done
Turn the project from a fuzzy wish into a finish line with visible proof.
A personal project keeps slipping when "done" means "better someday." This step makes completion observable before planning starts. Common mistakes: describing a dream version, adding tools not listed, or making success depend on someone else approving it. Need help if the AI expands the project? Paste again and require it to use only your stated done definition and materials. You are ready when a friend could tell whether the project is finished.
- Done is observable The finish line can be verified from visible proof, not a mood.
- Scope is smaller than the dream The non-goals clearly cut tempting extras.
- No invented requirements The test does not add tools, approvals, or success metrics you did not provide.
-
2
Name why now
Write the honest reason this project deserves attention in this season.
Motivation fades when the reason is generic. This step ties the finish line to a real personal payoff and the cost of waiting. Common mistakes: inventing urgency, turning the project into self-criticism, or promising life changes the facts do not support. Need help if the AI gets dramatic? Paste again and ask for calm language using only your why-now field and approved done definition. You are ready when the reason feels true enough to reread during a stuck week.
- Reason comes from your facts The why-now statement matches what you entered and approved.
- Payoff is believable Benefits are practical or meaningful without promising a transformed life.
- Tone stays kind The cost of waiting and keep-going line do not shame you.
-
3
Name constraints
Make the real limits visible so the plan fits the life and supplies already described.
Constraints are not excuses; they are design rules. This step prevents a project plan from pretending there are extra hours, supplies, or space. Common mistakes: ignoring the hours-per-week number, treating missing materials as ready, or making every blocker a fatal flaw. Need help if the AI overbooks you? Paste again and require the weekly work to stay inside the entered hours and materials. You are ready when the plan has honest boundaries.
- Hours are treated as a limit The time budget does not invent extra availability.
- Materials are honest Ready and missing items match what you entered.
- Scope rules protect completion Rules stop obvious creep before planning begins.
Stage 2: Plan
-
4
Break into chunks
Split the finish line into small pieces with dependencies and parked ideas.
A project stays stuck when every next step feels like the whole project. This step turns the finish line into manageable chunks. Common mistakes: making chunks too large, adding research detours, or hiding dependencies until late. Need help if the chunks feel vague? Paste again and ask for each chunk to be completable in one sitting or one weekly repeat. You are ready when every chunk has a clear verb.
- Chunks have verbs Each chunk says what action happens, not just a topic name.
- Chunks fit your hours The size check respects the weekly time budget.
- Dependencies are visible The plan shows what must happen before later work.
-
5
Sequence the weeks
Turn project chunks into a simple week-by-week path toward the deadline.
Chunks need order or they become another list to avoid. This step builds a realistic sequence that respects weekly hours and the deadline. Common mistakes: placing everything in week one, assuming exact free days not provided, or expanding the finish line mid-plan. Need help if the AI invents a calendar? Paste again and tell it to use week labels only unless you gave exact days. You are ready when the sequence shows what happens first, middle, and last.
- Sequence reaches the finish line The final week closes the approved done definition.
- Hours stay realistic The time-fit note respects the hours you entered.
- Slip rule avoids heroic catch-up The fallback moves work without pretending extra time appears.
-
6
List risks
Name the likely ways the project could stall, plus prevention and recovery moves.
Risks are easiest to handle before they happen. This step turns known blockers into concrete watch points and small recovery actions. Common mistakes: catastrophizing, ignoring the blockers already named, or solving every risk with more money or time. Need help if the AI gets dramatic? Paste again and ask for small prevention moves using only approved constraints. You are ready when each risk has one prevention move and one recovery move.
- Risks come from known blockers The list reflects what you entered and approved, not imagined disasters.
- Prevention is small Moves can happen inside the current time and materials.
- Recovery avoids restarting The plan repairs or narrows instead of throwing everything away.
Stage 3: Finish
-
7
Write check-in template
Create a short weekly review that uses evidence, decisions, and one next move.
Personal projects drift when nobody checks the plan against reality. This step gives the project a lightweight review without turning it into admin work. Common mistakes: writing a long journal template, measuring feelings only, or scheduling exact check-in times not provided. Need help if the AI invents a calendar slot? Paste again and ask for questions only, with no assumed day or time. You are ready when the template can be answered in ten minutes.
- Template is short enough to use The check-in could be answered quickly during a normal week.
- Evidence matches done Progress evidence comes from the approved finish line.
- Decision rule is practical The rule tells you when to continue, adjust, or reduce scope.
-
8
Plan first week
Choose the first week of real moves that starts the project without overbuilding it.
A plan becomes real in the first week. This step turns the sequence into concrete actions while respecting the hours and materials already named. Common mistakes: using the first week for more planning only, buying extras, or placing tasks on exact days not provided. Need help if the AI over-schedules? Paste again and ask it to keep actions within the stated weekly hours and avoid exact days. You are ready when the first week has visible proof.
- Actions are concrete Every first-week item starts with a real action.
- Calendar stays honest Placement uses the weekly hours without inventing exact availability.
- Proof is visible You can tell whether the first week happened.
-
9
Pack finish checklist
Build the final checklist, closeout note, and parking lot for any next version.
Finishing needs a stop signal. This step prevents the project from turning into endless improvements by matching the checklist to the approved done definition. Common mistakes: adding a new version before closing this one, making the checklist vague, or requiring proof the person cannot collect. Need help if the AI expands the finish? Paste again and tell it to match only the approved done definition and artifacts. You are ready when every checklist item can be ticked or left unticked.
- Checklist matches done Items prove the approved finish line instead of a bigger project.
- Closeout stops the loop The note closes this version before any next version begins.
- Future ideas are parked Next-version ideas wait until after the checklist is complete.
Your information
7 details, answered once- Project name Give the personal project a short name. It can be plain or playful.
- What would count as done? Describe the finished version someone could actually verify. Keep it smaller than your dream version.
- Why now? A real reason this matters now. Use facts or personal meaning, not pressure you do not believe.
- Focused hours per week Hours you can actually protect for this project. The plan will not invent extra time.
- Deadline The date you want this version finished. Use a real calendar date or a clear week.
- Materials ready Tools, supplies, notes, space, or people already available. Include missing items only if you clearly mark them.
- Known blockers What usually makes this project slip: time, money, supplies, decisions, confidence, space, or energy.
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.htmlOffline HTML reader for every approved step01-define-done.mdDefine done02-name-why-now.mdName why now03-name-constraints.mdName constraints04-break-into-chunks.mdBreak into chunks05-sequence-the-weeks.mdSequence the weeks06-list-risks.mdList risks07-write-checkin-template.mdWrite check-in template08-plan-first-week.mdPlan first week09-pack-finish-checklist.mdPack finish checklistREADME.mdManifest of what you approved