plan:issue-analyzer

To create a TDD planning workflow from a GitHub issue, the analyzer processes the issue through Investigation, Learning, Approach Comparison, and TDD planning phases, outputting a structured implementation plan saved to the .claude/plans directory.

Analyzing OSS bug reports before contributing code is best handled by applying a phased investigation framework that guides users through structured learning and approach comparison without making code changes, ensuring thorough root cause analysis.

Yes, you can use this issue-analyzer for GitHub Discussions and feature requests. It accepts descriptive problem statements and converts them into structured, phase-driven investigation and TDD planning outputs.

Phase management during issue analysis works by enforcing completion gates after each stage. The analyzer requires explicit user confirmation to proceed, delivering phase summaries and learning prompts throughout the workflow.

No, the analyzer does not modify repository code when generating an implementation plan. It strictly performs investigation, analysis, and planning tasks, outputting only TDD-based planning artifacts to the .claude/plans directory.