design-an-interface

To compare API designs simultaneously, you describe your module and coordinate parallel sub-agents to generate three or more radically different interface signatures, highlighting trade-offs for each architectural approach.

The best way to explore interface designs during an architectural review is to generate multiple modular design options in parallel, which surfaces diverse API signatures and usage patterns for rapid structured comparison.

Generating parallel interface designs helps with module boundary decisions by rapidly producing diverse API signatures and usage examples, allowing teams to directly evaluate trade-offs across different architectural approaches before implementation.

Yes, you can use parallel sub-agents to evaluate trade-offs for different API design options, generating radically different interfaces and providing a structured comparison of each approach's architectural impact.

You need to generate multiple interface designs when you are designing an API, evaluating module boundaries, or conducting design reviews where rapid comparison of radically different architectural options is required.

The limitation of using parallel agents for API design comparison is that it focuses strictly on generating interface signatures, usage patterns, and trade-offs, requiring your team to manually decide and implement the final architectural design.