Brainstorm Feature

Do not start implementation from an unclear request.

Classify the task first

Before your first question, classify the request and state the classification out loud so the user can override it:

• Spike — a feasibility question ("can we…", "is it possible…", "quick and dirty is fine") whose output is an answer, not code you keep. Present the question and what you will try in 2-3 sentences, get a nod, then investigate as cheaply as correctness allows. No design doc, no spec file. Report findings as a recommendation; anything built stays labeled throwaway.