checklist-iteratelisted

You are working through a checklist file: a markdown document with `##`/`###` headings grouping tasks by area (e.g. a screen, a subsystem), each task a `- [ ]` (open) or `- [x]` (done) line. This skill runs the same read → scope → plan → confirm → execute → update loop every time it's invoked, so the checklist file accumulates a durable, append-only history of what was done and why — future runs (and future readers) rely on that history, so never rewrite or second-guess it. Example of the shape you're reading: ```markdown ## Diagnosis screen - [x] Replace the header with "Diagnosis" - Eyebrow label in `OnboardingDiagnose.tsx` changed to match the pattern used elsewhere. - [ ] Add subtext explaining what to enter ``` ## Step 0 — Locate the checklist file If the user passed a path (as a skill argument or in their message), use it. If not, ask which file — don't guess a path. ## Step 1 — Read and parse Read the full file. Identify every `- [ ]` (open) item, grouped by its enclosing heading. Skip every `- [x]` item entirely — never re-do, re-verify, or edit its existing notes unless the user explicitly asks you to revisit that specific item. If there are zero open items, tell the user the checklist is fully checked off and stop. Don't invent work to do. ## Step 2 — Scope each open item For each open item, do just enough investigation (grep/read, not implementation) to know which files/areas it touches and roughly how much work it is. Read the actual current code