Analyze Issue

Turns a GitHub issue number into a full technical specification with problem statement, implementation plan, test scenarios, and file change lists. It checks if you've already fetched the issue, grabs it from GitHub if needed, then walks through your codebase to understand context before writing the spec. Saves everything to a standardized markdown file in your specs folder following a strict naming convention. The template enforces TDD principles and a 300 line file limit, which tells you this is aimed at teams who want structured planning before touching code. Useful if you're tired of issues turning into sprawling PRs because nobody documented what they were actually supposed to build.