evanflow-design-interface

Parallel sub-agents generate radically different interface designs for a module, which are then evaluated on depth and simplicity to synthesize a final API shape. This approach surfaces trade-offs and risks before committing to a single design.

Generating multiple radically different interface designs in parallel provides diverse perspectives for module boundary decisions. Embedded grill questions surface risks and trade-offs, enabling a structured comparison on depth and simplicity before finalizing the refactor design.

Parallel design exploration spawns three or more sub-agents, each with distinct constraints, to produce diverse interface options. These designs are then evaluated on depth, simplicity, and implementation feasibility to synthesize the best compromise for the final API shape.

Yes, this approach designs new APIs by providing multiple interface designs and a synthesis workflow to evaluate trade-offs. It ensures you finalize the API shape and review implementation feasibility before any actual coding begins.

Running parallel sub-agents for interface design is necessary when multiple perspectives are valuable, such as during new API creation, refactors, or module boundary decisions. It surfaces trade-offs and risks via embedded grill questions before committing to a design.

A limitation of using sub-agents to synthesize a final API shape is that it does not commit code, focusing solely on design evaluation. The process relies on satisfying requirements for depth, simplicity, and implementation feasibility without generating the actual module implementation.