question-resolver

To systematically resolve technical questions, classify the inquiry first, then conduct a structured investigation using verifiable evidence like documentation or code, and document the final resolution. This prevents unverified assumptions and avoids rabbit holes.

The best way to document a research spike for an unfamiliar API is to classify the question, hypothesize, search for verifiable evidence, and record the resolved answer along with its supporting documentation to ensure findings are logged.

To determine if a technical question needs stakeholder input, classify the inquiry by checking if it is answerable via existing documentation, requires further research spikes, or explicitly needs stakeholder input to resolve ambiguous requirements.

To structure a technical investigation and avoid unverified answers, employ a methodical approach of hypothesizing, searching for evidence in verifiable sources like code or experimental results, and verifying findings before documenting the resolution.

You should use a structured approach for technical problem solving when encountering unfamiliar APIs, new codebase patterns, or ambiguous requirements, ensuring answers are verifiable and properly documented rather than guessed.