When you're stuck on a technical decision that's blocking development, this generates structured spike documents to research your way out. It creates markdown files with research questions, investigation checklists, and decision frameworks for things like API integrations, architecture choices, or performance constraints. The templates force you to define success criteria upfront and timebox your research, which prevents endless rabbit holes. I've seen too many teams debate implementation approaches for weeks when a two-day focused spike would have given them concrete answers. The structured format also makes it easy to hand off research between team members.
npx skills add https://github.com/github/awesome-copilot --skill create-technical-spike