plan-morninglisted

# Plan Morning Walkthrough of the morning sections of today's daily note in at most three stops: Yesterday, Today, and Standup. Each interactive stop gives the user a single file to edit rather than a chat Q&A, so the whole walkthrough needs only a few responses. **REQUIRED:** Invoke the `ls-notes:daily-note` skill NOW for vault context and file path conventions. ## Editing Each interactive stop presents a single scratch file at `/tmp/plan-morning.md`: 1. Write the content to the scratch file. 2. **REQUIRED:** Invoke the `ls-interactivity:interactive-edit` skill to open it, passing a lower-kebab-case window name for the current step (e.g. "yesterday" or "today"). Summarize for the user what to fill in. 3. When the window closes, read the scratch file and apply the responses per the current step. ## Task List Format Use this format whenever presenting tasks for editing, as one section nested within a stop's scratch file: - Give the task block a `##` header — either `## Tasks` or a day header (e.g., `## Monday, January 1, 2026`) when the step calls for one. - Give each subsection that has tasks a `###` header. - Copy task lines verbatim (keep wikilinks and current markers) so they round-trip cleanly. Example: ```markdown ## Tasks ### Personal - [ ] Update the README.md - [<] Read Chapter 3 of The Pragmatic Programmer ### Work - [/] Post a [status update](https://example.com) for my current project ``` Applying the saved file: copy each task's edited marker back t