research
Evidence-Driven Research
Answer the actual question with traceable evidence and a recommendation when the question calls for one. Alternate investigation and provisional synthesis: use what you learn to choose the next useful check, while keeping conclusions revisable.
The user's instructions take precedence over this skill's guidelines. Research does not authorize implementation or external mutations. Respect a request to browse, to use specified sources, or to avoid browsing; explain any resulting evidence limit without inventing current facts.
Frame the Decision
Identify the question, target system, relevant time or version, and consequence of being wrong. Confirm the named repository, product, or artifact exists before researching its properties. Recall prior decisions through the configured memory workflow; treat memory as a lead rather than current proof.
For an existing system, run an internal investigation alongside external research. Inspect the installed version, actual interface, deployment topology, or migration constraint. A technically attractive option can still fail the target system's requirements.
| Question shape | Useful approach |
|---|---|
| A current version or specific capability | Inspect the authoritative registry, release, docs, or local interface directly |
| A choice between technologies | Compare relevant capabilities, operating cost, failure modes, and adoption/exit cost |
| An uncertain performance claim | Examine methodology, then benchmark representative work if feasible |
| A broad landscape | Map distinct directions, then investigate the gaps that could alter the answer |
| A codebase question | Trace the implementation and consumers before searching externally |