GitHub Issue to Implementation Plan
Convert a raw issue into a scoped execution plan with risks, dependencies, and validation steps.
Use case
Converting a GitHub issue or feature request into a concrete technical implementation plan
Works best with
Input needed
The GitHub issue text, relevant codebase context (tech stack, architecture), and any constraints (timeline, backward compatibility)
Output format
Implementation plan with file-level changes, step-by-step approach, edge cases, testing strategy, and estimated complexity
Example use
Paste a GitHub issue requesting 'add dark mode support.' Provide your tech stack (Next.js + Tailwind). Get back a plan covering CSS variable setup, theme context, component changes, persistence, and migration steps.
Editor’s Note
Very effective for breaking down ambiguous issues into concrete steps. Claude Code and Claude are particularly strong here due to codebase awareness. The main limitation is that it can't see your actual codebase (unless you provide context), so the plan may not account for existing patterns.
Full Prompt
Act as a senior software engineer. Convert the issue below into an implementation plan another engineer could execute safely. Issue: [PASTE ISSUE] Relevant codebase context: [OPTIONAL NOTES, FILES, CONSTRAINTS] Output: 1. Problem Summary - What is broken or missing - What success looks like 2. Likely Touchpoints - Files, modules, services, or systems likely involved 3. Implementation Plan - Step-by-step tasks in logical order - Call out dependencies and sequencing 4. Risks / Edge Cases - List the most likely regressions or hidden complexity 5. Tests To Add - Unit - Integration - Manual verification 6. Open Questions - Anything that must be clarified before coding Rules: - Be concrete and engineering-focused - Do not jump straight to code - Prefer minimal, low-risk changes unless the issue clearly requires more
Tags