learning-pathlisted

# Learning path One plan note per topic; plan mode writes it, retro mode edits it. No note for the topic (frontmatter `type: learning-path`) → plan. Note exists and the user names a milestone, says "retro", or asks what you learned → retro (no note: say so, then plan). Two or more matching notes → ask which (the one mid-task question). ## Folder Folder: unset. Agree it with the user in the first intake question and record it here (one-line edit). ## Plan mode Inputs: topic, baseline (known or built), target outcome (what you will ship or do), hours per week, deadline. Missing ones: one batched question, then finish without further check-ins. 1. Resources: reuse your Reader library (`readwise-mcp`) and `Resources/Readwise/` first; cap at 3 primary. Confirm each by search (URL, edition, version) even when the title is familiar. 2. Sequence fundamentals → applied practice. Each milestone: date, deliverable, pass/fail check, one practice exercise with feedback criteria; `quiz` is the understanding check. 3. Write the note (≤1 page): frontmatter (`type`, `topic`, `status`, `created`, `hours_per_week`, `deadline`), milestone table, one paragraph per milestone, empty `## Retros` section. Done: note in the agreed folder; every milestone dated with deliverable and check; milestone hours ≤ hours per week × weeks to deadline. ## Retro mode Inputs: the plan note; evidence since the last retro entry (or `created`): commits, vault notes, quiz results, daily notes, and what the use