researchlisted

Spin up a **background agent** to do the research, so you keep working while it reads. Its job: 1. Investigate the question against **primary sources** — official docs, source code, specs, first-party APIs — not a secondary write-up of them. Follow every claim back to the source that owns it. 2. Always use the `/microsoft-docs` skill for anything related to Microsoft technologies such as Azure, Copilot Studio, etc. 3. Write the findings to a single Markdown file, citing each claim's source. 4. Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where. ## Owning the transition, or not Most research is **nested**: another skill — `/wayfinder`, `/triage`, `/grill-with-docs` — needed a fact before it could decide. Nested research records nothing of its own; it hands its durable pointers back to the skill that asked: the findings file's path, the commit SHA that carries it, and the branch it lives on. That skill records once, for the transition it owns. Research owns this record **only** when it was invoked directly on its own tracker ticket — a `wayfinder:research` ticket, say — and durably resolves it. Then, and only then: 1. Commit the findings file. 2. Post the answer as a resolution comment on the ticket and **close the ticket**. That comment is the durable record of what this transition changed. ### When the question survives the session Not every directly-owned ticket gets answer