issue-driven-design

To convert vague product requests into testable software design documents, you crystallize the core issue into a measurable problem statement and structure hypothesis-driven decisions with verifiable evidence. This process yields a structured markdown document with traceable architecture and risk matrices.

The best way to structure an evidence-based system design document is to break the main design thesis into independent, verifiable sub-theses. You then produce a markdown file containing an executive summary, Mermaid architecture, component design, and a decision log.

To generate a decision log with a risk matrix for architecture comparisons, you prioritize blockers and define architecture choices using hypothesis-driven decisions. The output attaches verifiable evidence and security checks for each claim within a structured markdown format.

Yes, this approach works for planning large refactors and infrastructure decisions by applying issue-driven design to technical problem solving. It produces traceable trade-offs and success criteria specifically tailored for infrastructure configuration and refactoring scenarios.

An issue-driven design document for a new payment service should include the current state, goals, constraints, hypothesis, risks, and required references. It generates a complete technical design with a Mermaid architecture diagram and a structured test plan.

You need to use hypothesis-driven decision structuring for software architecture when facing ambiguous technical problems or new system designs. It transforms unclear goals into independent, verifiable sub-theses with required evidence, ensuring every design choice is defensible.