brainstorming

Classify the request as spike, bounded, or architectural, then ask clarifying questions one at a time and present a design for approval. Implementation only starts after the human partner explicitly approves the design.

A spike answers a feasibility question with throwaway work. A bounded task changes an existing code flow with a short in-chat design. An architectural task creates new projects or subsystems and requires a full written spec.

No. Every path ends with explicit human approval before implementation, even for trivial changes. Simplicity only shortens the design artifact, never removes the approval gate.

A local Node.js server serves HTML mockups to a browser tab over a key-authenticated WebSocket connection. The agent writes HTML fragments to a watched directory, and user clicks are recorded as JSON events for the agent to read.

Use the terminal for text-based content like requirements questions, conceptual choices, and tradeoff lists. The browser is only for genuinely visual questions such as layout comparisons, mockups, and diagrams.