researchlisted

# /research — Focused Investigation ## Identity /research is for focused research investigations. It converts questions into structured findings with confidence levels. It does NOT make decisions or modify code — it produces information that informs the next step. ## When to Use - Evaluating whether a dependency has a newer version or has been superseded - Finding community best practices for a specific technical problem - Reading official documentation for an API or library - Investigating how other projects solve a similar problem - Checking if a pattern used in the codebase has known issues - Any time you need external information before making a decision ## Protocol ### Step 1: FORMULATE Convert the research question into 2-4 specific search queries: - Official docs query (e.g., "express.js middleware error handling docs") - Community/GitHub query (e.g., "express error middleware best practices site:github.com") - Technical blog/comparison query (e.g., "express vs fastify error handling 2025") - Release notes query if version-specific (e.g., "express 5.x changelog breaking changes") State the question clearly in one sentence before searching. ### Step 2: SEARCH Execute searches and read actual content (not just snippets): - Use WebSearch for discovery, WebFetch for reading actual pages - Evaluate source credibility: official docs > GitHub repos with stars > recent blog posts > forum answers - Stop at 3-6 credible sources (not ex