research-prompt

To convert a build request into a codebase research prompt, you rewrite the implementation-oriented instructions into research-focused queries that seek current-state understanding, concrete file locations, and real usage examples.

Exploring codebase patterns before implementing a new feature prevents coding against assumptions, which leads to rework and drift. Research-focused prompts direct the agent toward existing dependencies and cross-component relationships for evidence-based changes.

Solution bias in spec-driven development occurs when presumptive implementation details override actual repository conventions. You remove it by transforming your request into a research prompt that focuses on discovering existing files, patterns, and dependencies instead of assuming a solution.

To map dependencies and cross-component relationships before coding, generate a structured research prompt that explicitly asks for concrete file locations, current usage conventions, and dependency mappings to understand the codebase's real structure.

Transforming prompts into research queries works for fixing existing code by shifting the focus from immediate changes to discovering current patterns, file locations, and real usage examples, ensuring fixes align with the actual codebase structure.