claude
bcd20283f3
CI / check (pull_request) Successful in 6s
The starter README said tasks-app is the running example for M1 and M2 only. In reality it's used from M1 through the capstone: agent-driven edits in M4, worktrees drive it in M7, the review lab pastes a patch onto it in M10, and so on. Tighten the note to reflect actual scope. Ports back the same change already merged on the GitHub mirror (recklessop/ai-workflow-course#2) so it survives the next Gitea -> GitHub sync instead of getting overwritten.
Demo app: tasks
A deliberately tiny command-line task tracker. It exists to be changed by an AI, so it's small enough to read in a minute but real enough to have more than one file, which is exactly where the copy-paste workflow starts to hurt.
This is the running example throughout the course: pain in Module 1, safety net in Module 2, docs in Module 3, agent-driven edits in Module 4, and it keeps showing up all the way to the capstone.
Files
tasks.py: the core logic (Task,TaskList).cli.py: the command-line front end. Reads/writestasks.json.
Run it
python3 cli.py add "read module 1"
python3 cli.py add "set up my editor"
python3 cli.py list
python3 cli.py done 0
python3 cli.py list
Requires Python 3.10+ (it uses list[Task] style type hints). No third-party packages.