Issue to PR Planner

Convert GitHub issues into step-by-step implementation plans with file changes.

9|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Notysoty/openagentskills --skill issue-to-pr-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Issue to PR Planner
Source: https://github.com/Notysoty/openagentskills/tree/main/skills/issue-to-pr-planner
Command: npx skills add https://github.com/Notysoty/openagentskills --skill issue-to-pr-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts GitHub issues into concrete, step-by-step implementation plans that specify file changes and execution order.

Core Features & Use Cases

  • Analyzes a given issue to determine type, goal, acceptance criteria, and scope.
  • Generates a detailed implementation plan including affected files, dependencies, and a recommended sequence of changes.
  • Outputs an actionable prompt-ready plan with optional questions for design decisions.

Quick Start

Provide the full issue text including title, description, and acceptance criteria to generate a detailed implementation plan.

Frequently Asked Questions about Issue to PR Planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a GitHub issue into an actionable implementation plan?

To turn a GitHub issue into an implementation plan, provide the full issue text including title, description, and acceptance criteria. The Skill analyzes the issue type and goal to generate a structured step-by-step plan with proposed file changes and execution order.

What is the best way to plan pull requests for new features and bug fixes?

The best way to plan pull requests for bug fixes and new features is to analyze the repository structure against the issue scope. This generates a detailed execution sequence specifying affected files, dependencies, and clear rationale for each required change.

Does the implementation planner work with any GitHub repository structure?

Yes, the implementation planner works across codebases by using the repository structure to propose file changes. It scopes bug fixes, new features, and enhancements to generate an actionable execution order tailored to the specific repository.

How do I generate a step-by-step file change sequence from an issue description?

You can generate a step-by-step file change sequence by inputting the issue description and acceptance criteria. The planner identifies the goal and outputs a structured plan detailing changed files, execution steps, and open design questions.

Will the generated PR plan include open questions for unresolved design decisions?

Yes, the generated PR plan includes optional open questions for design decisions. Alongside the proposed file changes and execution order, it provides clear rationale and justification to guide the implementation of the issue.