ultrathink

Deep planning for software architecture systematically challenges assumptions and simplifies design to an inevitable minimal viable architecture. It is needed for epic-scale features, multi-sprint initiatives, or when complex codebase analysis requires rigorous decision-making.

To create an assumption inventory, systematically document and question each project premise to identify hidden complexities. This process removes unnecessary architectural bloat, ensuring you deliver elegant, minimal viable solutions tailored to actual requirements.

You sketch a minimal viable architecture by performing deep codebase soul analysis to reveal existing patterns, then outlining the simplest viable plan. This approach ensures the architecture naturally emerges from validated decisions rather than premature complexity.

Yes, deep planning is specifically designed for large multi-sprint initiatives and epic-scale features. It handles complexity by comparing design alternatives, conducting codebase analysis, and generating robust trade-offs to ensure architectural stability.

The best way to compare design alternatives is to generate multiple architectural approaches and evaluate them against your assumption inventory and codebase analysis. This ensures robust trade-offs by validating each option against minimal viable design principles.

You should avoid minimal viable architecture planning when a feature requires immediate, unstructured prototyping without multi-sprint commitments, or when lacking the necessary context to challenge assumptions and perform deep codebase soul analysis.