explain-flowlisted

# Explain Flow Produce a code-grounded, phase-by-phase walkthrough of how a sequential component actually executes — not a paraphrase of file names, a trace of real control flow with citations. ## Quick start 1. Find the entry point (main class/function, script, cron handler, message consumer). 2. Read it — and everything it directly calls — **in full** before writing a single line. Never write from a partial read; for large files read in chunks until you've covered the whole thing. 3. Split the logic into phases using the taxonomy below, in true execution order. 4. Write the walkthrough with the template below. 5. Save it under the project's `docs/` folder (create the folder if missing) **and** print the full walkthrough as your chat response — saving the file is not a substitute for showing the content. Don't make the user open the file to read it. ## Phase taxonomy | Phase | Covers | Ask yourself | |---|---|---| | 0. Entry / Init | What runs before real work starts: config load, connection setup, arg parsing | What has to be true/loaded before step 1 can run? | | 1. Input Acquisition | Where source data enters: queries, file listing, queue read, API pull | Is there more than one source/condition? (tabulate if so) | | 2. Processing | The core per-item logic, including branches and guard conditions | What decides whether an item is skipped, retried, or processed? | | 3. Output / Side Effects | What gets written, sent, or uploaded, and in what format/contract