reconlisted

# RECON **Deep research. Persistent results. Never research the same thing twice.** --- ## Usage ``` /recon [topic] - Research a topic in depth /recon --quick [topic] - Quick overview (5-10 minutes) /recon --deep [topic] - Comprehensive investigation (30+ minutes) /recon --compare [A] vs [B] - Comparative analysis ``` --- ## What This Is RECON is a research skill that produces thorough technical reports and automatically saves them to a local knowledge base. Next time you (or Claude) need the same information, it's already there — no redundant web searches, no lost research. --- ## The Research Process ### 1. Check Existing Knowledge Before researching, RECON checks the knowledge base for existing reports on the topic. If a relevant report exists, it surfaces that first and asks if an update is needed. ### 2. Conduct Research Uses Claude's built-in `technical-research-agent` to: - Decompose the topic into subtopics - Search multiple sources (web, documentation, repos) - Synthesize findings into a structured report - Identify code examples and implementation patterns ### 3. Save Results Reports are saved as markdown files to the knowledge base directory: ``` knowledge/ research/ 2024-01-15_react-server-components.md 2024-01-20_rust-vs-go-backends.md 2024-02-01_vector-databases-comparison.md index.json # Master index for search ``` ### 4. Index for Future Retrieval The report is indexed with: - T