Workmap

Draw the active conversation's work as a workmap: one tree of an idea, its projects, and their tasks and questions. The workmap is a view built from the conversation alone; drawing it leaves the work, native todos, files, and trackers as they were.

Nodes

• Idea: the one-line problem or aim the session is about.
• Project: one goal with a one-line done-condition, orthogonal to its sibling projects.
• Task: one reviewable change; in a code repository, one PR.
• Question: a decision or unknown still to be settled.

These name units of the work being mapped, whatever the repository's own domain calls a project or a task.

The tree also carries the order of the work:

• A project's tasks form a stack in listed order: each builds on the one above it in the list, one PR each, each PR based on the previous one (gh stack on GitHub). ∥ marks a task that stands outside the stack.
• Projects run in parallel, each in its own worktree. after P1 marks one that waits for another.
• touches: names the area a project changes; leave it off while the area is unknown. Two projects that touch the same area are not orthogonal: merge them, or order them with after.