Tasks

Your private todos, per project: quick, disposable, yours only.

Tasks are your personal scratchpad of TODOs inside a project: nobody else sees them, and they carry none of the ceremony of problems. Cut one when something crosses your mind mid-flow, tick it when done, delete it without guilt. They are project-scoped in the data but personal in nature, on the web they sit behind the checklist icon at the end of the project's bar, apart from the shared record.

1. Step 1 of 3

   Catch it before it escapes

   Mid-flow thoughts go here, not into your head. One line, no fields, no assignee: a task is yours alone. If it turns out to be real work for the team, promote it to a problem later.

   plm task · add

   $ plm task "rotate the staging DB password"

   ✓ task ptask_b02d91a4 — rotate the staging DB password

   full form · plm task "<title>"

2. Step 2 of 3

   Read the checklist

   A plain checklist, done items checked off. No counts, no burndown: tasks are a memory aid, and the honest measure of one is whether you can trust it to hold what you dropped there.

   plm tasks

   $ plm tasks

   [ ] ptask_b02d91a4 rotate the staging DB password

   [x] ptask_77e01c2f read the decisions log

3. Step 3 of 3

   Tick it, or fix it

   Done and undone are one flag away, and a mistyped title is not a new task. The id comes straight from the list.

   plm task · update

   $ plm task ptask_b02d91a4 --done

   ✓ updated ptask_b02d91a4

   full form · plm task <ptask_…> --done | --undone | --title "…"

Also in this chapter

• Project-scoped: run inside a linked repo (plm link <project-slug>). Personal: only you see your tasks.
• For shared, assignable work use problems (the Goals & Problems chapter); tasks are your own margin.