researchlisted

# Research Output "Read Research skill." to chat to acknowledge you read this file. Cache expensive exploration into a persistent research.md so implementation conversations can start with full context instead of re-exploring. ## When to Use - Before a large feature where architecture, dependencies, or API choices are unclear - When multiple conversations will work on the same area - When exploration would consume >20% of context and you still need room to implement - When the user says "research this first" or "investigate before building" ## Process ### 1. Check for Existing Research If research.md already exists in the project root: - Read it fully - Check the `Generated` date in the header - If <7 days old and topic matches: use it as-is, skip to handoff - If >7 days old or topic doesn't match: re-validate by spot-checking 2-3 key claims, then update or regenerate ### 2. Decompose Break the research topic into 3-6 distinct areas of concern. Each area should be explorable independently. ### 3. Parallel Exploration Spawn a dedicated sub-agent for each area using the `explore` verb (per the explore skill). Each sub-agent should have a narrow, specific focus. ### 4. Synthesize Combine all sub-agent findings into research.md in the project root with this structure: ```markdown # Research: [Topic] Generated: [date] Topic: [one-line summary] ## Summary [2-3 paragraph executive summary of findings] ## Architecture [Relevant code paths, data flow, existing patt