researchlisted

# Research If running interactively (human present), output "Read Research skill." to acknowledge. If running with --dangerously-skip-permissions (AFK/unattended), skip acknowledgement and proceed directly. Cache expensive exploration into a persistent `working/research/<topic>.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 `working/research/<topic>.md` already exists: - 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 `working/research/<topic>.md` with this structure: ```markdown # Research: [Topic] Generated: [date] Topic: [one-