coding-research

To gather authoritative evidence for API and architecture assumptions, use Context7-first sourcing to find official documentation, standards, and vendor sources. This resolves product, domain, or library uncertainties before finalizing planning documents and contracts.

The best way to verify external library uncertainties for app design is applying evidence-first research. It targets narrow questions affecting feature scope and implementation assumptions, mapping concise findings directly to planning documents like APP.md or ARCHITECTURE.md.

Yes, this research approach uses official documentation over blog posts for feature scope decisions. It enforces a preference for Context7, official documentation, standards, and vendor sources to prevent speculative planning and reliable evidence.

To map research findings to planning documents without a separate research track, use bounded decision support. It integrates concise external evidence directly into existing files like FEATURE.md, ensuring research informs architecture and product decisions seamlessly.

You need evidence-first research for implementation assumptions when you have a concrete uncertainty affecting app design, architecture, or feature scope. It gathers the minimum reliable evidence needed to resolve these specific domain or API questions before committing.