brainstorm

To translate vague requirements into an implementation strategy, this Skill explores multiple architectural approaches, identifies trade-offs, and generates a high-level implementation picture with a work breakdown before you commit to detailed specs.

Evaluating architecture trade-offs during early planning involves generating 2–3 viable architectural options, assessing risks for each, and validating them against existing codebase constraints to ensure pattern alignment before development begins.

Yes, you can generate a work breakdown structure from an unclear product requirement by running a brainstorming session that surfaces multiple options and outlines a validation plan suitable for creating development epics.

Yes, this approach validates architecture options by incorporating constraints from the existing codebase, ensuring that the proposed implementation strategies align seamlessly with your current architectural patterns and technical limitations.

You should avoid this approach when a product requirement is already highly specific or when detailed technical specifications are finalized, as it targets early planning where multiple implementation approaches still need exploration.