research-spikelisted

# Research Spike Runs a structured research spike: gathers real-time community signals via `/last30days`, synthesizes findings into a comparison matrix, and saves a recommendation note to the brain vault. ## Trigger phrases - `/research-spike [topic]` - "spike on [topic]" - "research [topic]" - "evaluate [X] vs [Y]" - "compare options for [topic]" - "what should we use for [topic]?" ## Input The user provides: - **Topic** (required) — what to research (e.g., "auth providers for Next.js", "Playwright vs Cypress", "vector databases") - **Context** (optional) — project constraints, must-haves, dealbreakers - **Candidates** (optional) — specific options to compare. If not provided, the skill discovers them during research. ## Step-by-step workflow ### 1. Clarify scope Before researching, confirm: 1. **What decision does this inform?** (library choice, vendor selection, architecture approach, etc.) 2. **What project is this for?** (check `projects/` for active projects — constraints differ per project) 3. **Any known candidates?** If the user already has 2-3 options in mind, start there. If not, discovery is part of the research. 4. **Dealbreakers?** (e.g., "must be open source", "needs EU hosting", "no vendor lock-in") If the user's input already covers these, skip asking and proceed. ### 2. Run /last30days research Invoke the last30days skill for the topic. This searches Reddit, X, YouTube, HN, and other sources for community signals from the past 30 days. ``` /last3