researchlisted

______________________________________________________________________ ## research **Skill metrics:** Emit a start event to the activity log: ```bash echo "{\"type\":\"skill\",\"event\":\"start\",\"skill\":\"research\",\"ts\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}" >> docs/sessions/.activity-log.jsonl ``` Researching: **$ARGUMENTS** ## Phase 1: Clarification Gate Before starting research, assess whether the query is specific enough: **If the query is vague** (single word, no clear question, ambiguous scope): - Ask 1–2 focused clarifying questions using AskUserQuestion - Ask about scope: "What specific aspect of [topic] are you interested in?" - Ask about context: "Is this for a specific project/technology, or a general investigation?" **If the query is specific enough** — proceed directly. **Ask about depth** if not obvious from the query: - Use AskUserQuestion with options: "Quick scan (2-3 searches, fast answer)", "Standard (parallel research, 2-3 min)", "Deep dive (comprehensive, 5-10 min)" - If the query clearly implies depth (e.g., "comprehensive analysis of..." → deep), skip asking ## Phase 2: Check Prior Research Before doing new research, check if this topic has been investigated before: 1. Search `docs/research/` for matching topics (Grep on title/tags in frontmatter) 2. Search `docs/solutions/` for related findings 3. Search `docs/brainstorms/` for related design explorations If prior research exists: - Load it and assess: is it still current? Does it answe