brainstorming

Turn vague intent into one selected direction and a Design Handoff. Stay at product/design/architecture altitude: no file-by-file steps, tracker mutations, executor prompts, or a parallel project charter. Recommend the next owner as text; never invoke it.

Workflow

1. Ground in context first. Inspect safely discoverable repository context (README, docs, existing code, existing task or tracker artifacts, sprint notes) before asking anything. Ask only what that context and the user have not already answered.

   Complete when: every question candidate is something repository context and the user have not already answered.

2. Size the pass by clarity.

   • Genuinely vague work: ask 1-5 material questions, one at a time, each only when its answer would change the decision. Stop asking once the direction is determined.
   • Clear, low-risk request: ask at most one question — often zero. Keep the pass short.
   • Honor an explicitly requested successor or route without re-asking.
   • If the user delegates the judgment, choose and explain rather than block.

   Complete when: the direction is determined, or every remaining uncertainty is classified as high-impact (still open) or low-impact.

3. Compare viable approaches. Name the genuinely viable approaches and their material trade-offs. Recommend one. Accept an override.