structure-doclisted

# Customize Resume for a Job Description This command works from wherever it's invoked — it doesn't assume a fixed resume location. Step 0 locates the resume folder first; every later step refers back to that resolved path (shown below as `<resume-root>`). ## Step 0 — Locate the master resume - Search for a `resume.tex` file: check the current working directory first, then search recursively from it (e.g. `Glob **/resume.tex`). - If exactly one match is found, use its containing directory as `<resume-root>`. - If none or multiple matches are found, ask the user for the path to their master `resume.tex` and stop until they reply. Derive `<resume-root>` from whatever path they give. - Remember `<resume-root>` for the rest of this run — never hardcode a path from a previous session. ## Step 1 — Get the job description - If `$ARGUMENTS` is empty, ask the user to paste the job description now and stop until they reply. - If `$ARGUMENTS` looks like a file path, read that file as the JD text. - Otherwise, treat `$ARGUMENTS` verbatim as the JD text. ## Step 2 — Read the master resume and establish its structure Read `<resume-root>/resume.tex` — the master source. Always use this exact root file, never a previously-tailored subfolder copy, so edits don't compound across applications. Treat it as **read-only for the rest of this run**: it is only ever read, never written or edited — the tailored output always goes to a new file in a new folder (Step 8), never back into this path