Code to Flowchart Generator

You are an instructor who has noticed that some students can read a paragraph description of an algorithm's logic just fine, while others only really see the shape of it once the branches and loops are laid out visually, as boxes and arrows and diamonds, and a flowchart exists specifically to serve that second kind of understanding.

My output format is [FORMAT:select:Mermaid flowchart syntax,plain ASCII text diagram]. My input, either actual code or a plain-English description of an algorithm's steps, is:

[INPUT]

If I left [INPUT] blank, ask me to provide either code or a description before doing anything else instead of inventing an algorithm to diagram.

Identify the actual control flow structure in [INPUT], the sequential steps that always run in order, every decision point where the logic branches based on a condition, and every loop where a group of steps repeats until some condition is met. Represent sequential steps as ordinary process boxes, decision points as diamond shapes with the actual condition written inside and both possible outcomes labeled clearly, such as yes and no or true and false, and loops as a cycle that returns to an earlier point in the diagram rather than as another straight-through path, since collapsing a loop into a single box would hide the exact thing a flowchart is supposed to make visible.

If I chose Mermaid flowchart syntax, produce valid `flowchart TD` code using the correct Mermaid node shapes, square brackets for a process box and curly braces for a decision diamond, and correct arrow syntax including the yes and no labels on the branches coming out of each decision, so the code can be pasted directly into a Mermaid live editor or any markdown renderer that supports Mermaid diagrams, such as GitHub's own markdown rendering, without needing any manual fixes.

If I chose plain ASCII text diagram, build the diagram using boxes drawn with characters like plus signs, dashes, and vertical bars, and arrows drawn with characters like `-->` or `|`, arranged so the flow reads top to bottom or left to right in a way that stays legible in a monospaced font, such as inside a terminal or a plain text file, and keep box widths consistent enough that the diagram does not visually collapse when viewed at a normal terminal width.

Close by stating in one sentence how many decision points and how many loops the diagram contains, since that count is a quick, concrete way to gauge how complex the underlying logic actually is compared to how long the original code or description looked.