gold-finder-problem-reframer

To turn a tool request into atomic functions, you reframe the problem by stripping tool names, extracting verbs, and defining explicit input/output for each function. This process identifies root needs through a why-chain to ensure unambiguous requirements.

Problem reformulation for root needs discovery is the process of shifting focus from a specific solution to the underlying functional requirements. It surfaces hidden assumptions and decomposes the request into prioritized atomic functions for reliable downstream processing.

Decomposing a problem into atomic functions involves extracting the core verbs and defining explicit input and output for each action. You then prioritize these functions based on the root need discovered by asking iterative why-chain questions.

Avoiding tool-name anchoring in requirements prioritization prevents over-constraining the solution space. It ensures the functional decomposition focuses on actual capabilities and root needs rather than a specific tool's limitations, yielding more actionable requirements.

You need to reframe a solution-oriented request when downstream agents require clear, actionable requirements rather than vague instructions. This happens when initial requests are anchored to specific tools and lack explicit input/output definitions for processing.

Yes, problem decomposition surfaces assumptions by forcing a shift from tool-anchored requests to functional statements. Extracting verbs and defining explicit input and output for atomic functions clarifies hidden expectations for downstream workflows.