bts-researchlisted

# Systematic Research Research the given topic and produce a structured document. ## Steps 1. Spawn Agent(Explore) to investigate the codebase: ``` Thoroughly explore the codebase related to: $ARGUMENTS Find: - Relevant files and their roles - Key functions, types, and interfaces - Dependencies and import relationships - Existing patterns and conventions - Configuration and environment requirements ``` If `.bts/specs/recipes/` contains completed recipes, read their final.md to understand existing design decisions, patterns, and known issues that may affect this research. 2. For library/framework documentation, use Context7 MCP: - `mcp__context7__resolve-library-id` to find the library - `mcp__context7__get-library-docs` to fetch up-to-date docs and examples - This gives more accurate, structured results than web search for known libraries 3. If additional external research is needed, use WebSearch/WebFetch for: - Official documentation not covered by Context7 - API references - Known issues or limitations Follow `.claude/rules/bts-evidence-policy.md` for source hierarchy (Context7 → official domains → site-filtered search). Every external claim recorded in the research document MUST carry a `Source:` line — uncited claims force /bts-verify to re-gather the same evidence later, one iteration per claim. 3.5 **Official Architecture Guidance (MANDATORY when the feature targets a framework/platform).**