he-research

To investigate open questions before planning, run parallel research across documentation, codebase patterns, and external references to categorize questions, prioritize primary sources, and gather evidence-backed findings that clarify ambiguous requirements.

Evidence-based requirements gathering for technical specifications is the process of distinguishing fact from inference by researching documentation and codebase patterns, ensuring your software scope, requirements, and risks are informed by verified findings rather than assumptions.

You research codebase patterns and external references in parallel by categorizing open questions and prioritizing primary sources across multiple documentation streams simultaneously, then updating your initiative artifacts with the evidence-backed results.

You need to research technical constraints before writing an implementation plan when you have high-level feature requirements but face uncertainty, ensuring you uncover existing solutions and clarify ambiguous aspects before committing to a detailed scope.

Yes, this evidence-based research approach operates without external dependencies, allowing you to investigate open questions and update specification documents directly using your existing codebase patterns and internal documentation.

The best way to distinguish fact from inference during software investigation is to prioritize primary sources across documentation and codebase patterns, categorizing your research findings to ensure specification artifacts contain only evidence-backed insights.