agent-researcher

To generate a research brief from a codebase, you need a tool that reads code and documentation in read-only mode to produce structured findings with sources and confidence ratings. This process surfaces evidence during plan and design phases to inform feature specs and acceptance criteria.

A structured findings report for software design is a concise research brief that answers a stated question by synthesizing evidence from codebases and documentation. It includes exported citations and a clear confidence score to guide design decisions and feature spec writing.

Yes, you can use brain-mcp references to research codebase questions. The tool conducts read-only exploration of codebases, documentation sets, and brain-mcp collections to answer stated questions and deliver a research brief with a confidence rating.

No, the research process does not modify your existing code or documentation. It applies read-only exploration across codebases, docs, and external sources to extract findings, ensuring your source files remain untouched while generating the report.

You get a confidence score for feature spec research by running a read-only exploration of your codebase and documentation. The tool analyzes the gathered evidence and exports a clear confidence level alongside source citations within the structured findings report.

The best way to gather evidence for feature specs from documentation is using an automated research tool that scans docs and code to output a structured brief. This approach provides exported citations and a confidence rating, streamlining early design decisions.