issue-planning-workflow

To plan a GitHub issue, you need a structured workflow that gathers issue intelligence, explores the codebase, and generates an implementation plan with defined steps, testing strategies, and risk assessments. This ensures all necessary information is collected before development begins.

The best way to break down a software engineering issue is through systematic codebase exploration and intelligence gathering, which clarifies requirements and produces a structured implementation plan. This approach identifies specific code changes and testing strategies needed for resolution.

Codebase exploration in issue resolution project management involves systematically examining relevant code files to understand the current state before generating an implementation plan. It defines specific code changes, testing strategies, and risk assessments required to resolve the task.

Yes, this workflow supports GitHub issue intelligence gathering by collecting and analyzing issue details, comments, and related pull requests. This information feeds into the final implementation plan to ensure development is based on complete context.

No specific dependencies are required to generate an implementation plan for a GitHub issue. The workflow operates independently using scripts and references to facilitate intelligence gathering, codebase exploration, clarification, and plan generation.

You should use a structured issue planning workflow when assigned a new GitHub issue that requires clear communication, task breakdown, and risk assessment. It prevents starting development directly by ensuring code exploration and implementation steps are defined first.