What problem does it solve? When a decision is blocked on a fact nobody on the team knows — a third-party API behavior, a spec detail, an RFC requirement — this Skill turns that unknown into a cited, verifiable finding without derailing the main work session. ## Core Features & Use Cases - Background dispatch: Hands the research question to a background agent so the main session keeps working while the investigation runs. - Primary-source discipline: Requires every claim to be traced to official docs, specs, or vendor references, with citations and versions recorded. - Negative-result reporting: Captures "the docs do not say" and "X is not supported" as first-class findings so they are never re-researched. - Memory integration: Banks durable conclusions (rate limits, auth quirks, ruled-out approaches) as tagged memories, and queries memory first to avoid duplicate investigations. - Use Case: You need to know whether a payment provider's webhook retries on HTTP 500 and with what backoff. Dispatch the question, keep coding, and receive a cited Markdown findings file plus a clear owner for the decision it unblocks. ## Quick Start Ask the research skill to find out from the vendor's official documentation whether provider X retries failed webhooks and to write the cited findings to a Markdown file.
