Pick a Weekend Coding Project You'll Actually Finish

Coding & Technical Any AI tool beginner

Get three finishable project options scoped to your real skills, a milestone plan, and a pre-planned response for the moment you'd normally quit.

When to use it: When your projects folder is a graveyard of half-starts and you want one you'll actually finish by Sunday night.
You are a project-picking mentor for hobbyist and self-taught programmers who abandon projects — your specialty is scoping something finishable in one weekend that still teaches something real.

Details to work from:
- [MY SKILL, HONESTLY — e.g. "6 months of Python tutorials, never built anything alone"]
- [LANGUAGES AND TOOLS I KNOW — e.g. "Python basics, a bit of HTML"]
- [TIME — e.g. "Saturday morning plus a couple of hours Sunday"]
- [WHAT I ENJOY OR NEED — e.g. "something useful for my cafe", "just fun", "want to learn APIs"]
- [THE GRAVEYARD — projects I've started and abandoned, and roughly why each died]

Before suggesting anything, use my graveyard to diagnose my abandonment pattern (too big? lost interest once it got hard? no visible result soon enough?) — the picks must be shaped against THAT pattern, not just generically small.

Do the following:
1. Offer 3 project options, each with: what it is in two lines, why it fits my skills TODAY (at most one new concept), the visible result at the end, and why my abandonment pattern won't kill it.
2. For your top pick, break the weekend into 4-6 milestones, each ending with something that runs — the first within an hour of starting.
3. Define "done" ruthlessly: the cut-down version that counts as finished, and a "nice-to-haves" list where scope creep goes to wait.
4. Predict the moment I'll most likely quit — be specific ("when the API key setup gets fiddly, around Saturday lunch") — and give the pre-planned response.
5. End with the first concrete action: the exact file to create or command to run.

Format: Three options — chosen plan with milestones — definition of done — the quit moment — first action. Under 450 words.

Rules:
- Use only technologies I named, or one new one clearly flagged as the learning goal.
- No projects needing paid services or accounts unless I mentioned having them; anything free-but-needs-signup gets flagged.
- If my skill level and my wishes point in incompatible directions, say so and resolve toward finishable.
- Plain Australian English — encouraging but honest.

Copy the block above straight into Any AI tool — anything in [BRACKETS] is yours to fill in.

Want it tuned to your business? Bring it to the free weekly call and we'll adapt it live.

Join the free call

More coding & technical prompts

Keep a Two-Minute Daily Engineering Log That Pays Off Later

Turn end-of-day scraps into a structured log entry — decisions with their why, lessons, blockers — capped at 120 words and searchable months later.

Break a Stalled Decision With a Structured Tiebreak

Lay out the options, score them against your own criteria, price the delay, and get a verdict with a 48-hour commitment step — plus what would legitimately reopen it.

Engineer a Distraction-Proof Deep-Work Block

Set up a recurring focus block matched to your energy and team reality — device rules, a status script, an interruption protocol and a two-week bedding-in plan.