issue-driven-design

What problem does it solve?

Turn ambiguous product or technical requests into clear, testable software design documents by crystallizing the core issue, structuring hypothesis-driven decisions, and attaching verifiable evidence for each claim.

Core Features & Use Cases

• Issue crystallization: Convert vague goals into a single, measurable problem statement and success criteria.
• Hypothesis-driven decision structuring: Break the main design thesis into independent, verifiable sub-theses with required evidence.
• Critical-path and defensive review: Prioritize blockers, define architecture choices, and produce risk matrices, security checks, and test plans.
• Use Case: Designing a new payment system, comparing architecture options, planning large refactors, or selecting infra configurations with traceable trade-offs.

Quick Start

Create an issue-driven design document for a new payment service including current state, goals, constraints, hypothesis, risks, and required references.