concise▌

Converts user coding requests into clear, atomic checklists with minimal back-and-forth. \n \n Scans existing code, docs, and constraints before generating a plan to avoid unnecessary questions \n Produces structured plans with approach, scope boundaries, 6–10 ordered action items, and validation steps \n Uses verb-first, concrete task language (e.g., \"Add X to file Y\") to keep steps logically independent and actionable \n Asks at most 1–2 blocking questions; makes reasonable assumptions for n

Turn a user request into a single, actionable plan with atomic steps.