frame-problem

To turn vague stakeholder requests into clear technical specifications, you need structured problem framing that captures the surface request, performs a 5 Whys root-cause analysis, and generates a draft specification. This process surfaces constraints and produces well-scoped problem statements before engineering begins.

Analyzing an existing codebase with ambiguous requirements requires current-state discovery to surface gaps and constraints. By applying root-cause analysis to the current architecture, you can generate multiple architectural alternatives with trade-offs and clear selection criteria for stakeholders.

Identifying XY problems in software design involves framing the stakeholder's proposed solution against their actual underlying need. Root-cause analysis like the 5 Whys technique exposes hidden constraints, allowing you to generate alternative architectural options rather than blindly implementing the requested feature.

You should use problem framing instead of immediately writing code when requirements are vague, stakeholder communication is unclear, or you suspect an XY problem. Framing produces a well-defined problem statement and architectural options, ensuring design efforts align with actual business needs.

Generating architectural alternatives with trade-offs is a core part of producing a draft specification. After current-state analysis and root-cause discovery, the problem framing process outputs multiple approaches with clear selection criteria, ready for downstream specification refinement.

Yes, frame-problem works without external dependencies or connected tools. It operates independently to perform current-state analysis, root-cause discovery, and option generation, producing a ready-to-refine specification from the vague stakeholder requests you provide.