Back to the journal
Everyday lifePlanning exampleEXAMPLE / 01

A small tool for just today’s tasks

A few things for today, instead of an endless list. Defining the first requirements for a little tool that helps you remember.

CONCEPT SCREEN
everyday / tasks
Just for today.3 things
Take a short walk
Read a chapter
Pick tomorrow’s first task
Add a little task
Conceptual screen layout · This is not a runnable program.
01

Problem · Today gets buried in a long list

Imagine a task app that mixes this month’s plans with things you might do someday. To find what matters today, you end up reading the entire list again.

This is a planning example, not a firsthand review. It shows how to define a small first tool and decide what to check.

02

Requirements · Keep only what matters today

The first screen should show only today’s tasks. Start with three actions: add a task, mark it complete, and delete a mistaken entry.

Leave calendars, priority scores, notifications, and accounts out of the first version. Fewer features also mean a smaller set of behaviors to verify.

03

Build · The first request to AI

Describe who will use it, what it should do, what is out of scope, and what you expect to verify. This sample prompt has not been run.

SAMPLE AI PROMPT
Build a personal web tool for today’s tasks.

Core functions:
1. Enter and add a task
2. Show only today’s tasks
3. Mark a task complete or delete it
4. Keep tasks in the same browser after a refresh

Reject empty entries. Wrap long text on mobile. No accounts, notifications, or calendar. Explain the limitations of browser storage.

04

Verify · A working button is just the start

Once built, test actions that could happen in daily use. A visible screen and reliably stored information are separate concerns.

  • Does it reject empty or whitespace-only entries?
  • Do completion and deletion affect only the selected task?
  • Do tasks survive a refresh?
  • Is the rule for yesterday’s tasks clear when the date changes?
  • Do long tasks and controls remain readable on narrow screens?
05

Use · What to observe in real life

There is no real usage record yet. When using it, note whether you open it to check tasks, duplicate information elsewhere, or need to find completed entries again.

Whether you return to the tool matters more than how quickly it was built. Record usage counts or time saved only after measuring them.

06

Improve · Change things after a need appears

Decide whether to preserve old tasks, collapse completed ones, or speed up entry based on problems discovered during use. Avoid adding features for every imagined scenario.

Browser storage does not follow you to another device and can disappear when browser data is cleared. Consider export before storing important information.

07

Current status · A planning example

This tool has not been built or released. Its screen is a conceptual layout and does not count toward the goal of 20 completed tools.

Start by listing tasks you actually forget and explain in one sentence why your existing tools are not helping.

Current tool status

Status
Not built yet · Planning example
Availability
Not released
Build tools
Not selected
Verified on
Not yet verified
ANOTHER PLANNING EXAMPLEA habit tracker that welcomes you back