plan-generator

Generate GitHub-friendly fix plans from exploration results with root cause, scope, testing, and risk sections.

Updated Jan 16, 2026

Search Tags:#automation #template #planning #GitHub #plan #issue #generate

Ready to run

npx skills add https://github.com/JuniYadi/claude-code --skill plan-generator-juniyadi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-generator
Source: https://github.com/JuniYadi/claude-code/tree/main/issue-reviews/skills/plan-generator
Command: npx skills add https://github.com/JuniYadi/claude-code --skill plan-generator-juniyadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates structured fix plans in GitHub issue comments to standardize how bugs are diagnosed and resolved.

Core Features & Use Cases

Generate a formal fix plan from exploration results that includes root cause, scope, testing, and risk.
Produce a GitHub-friendly Markdown plan that teams can paste into issue comments.
Support templates and consistent formatting to speed up issue resolution.

Quick Start

Use the plan-generator to create a fix plan from your exploration results.

Frequently Asked Questions about plan-generator

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

FAQPage Schema

How do I generate a fix plan for a GitHub issue from exploration results?▼

To generate a fix plan for a GitHub issue, process exploration results containing rootCause, relevantFiles, confidence, and understanding through the generator. It outputs a structured Markdown plan covering scope, testing, and risk for issue comments.

What does automated plan generation for GitHub issues do?▼

Automated plan generation transforms raw exploration results into structured fix plans for GitHub issues. It applies template-based formatting via an internal library to produce comprehensive, reusable, GitHub-friendly Markdown output.

Can I use template-based formatting to standardize bug diagnosis plans in issue comments?▼

Yes, template-based formatting standardizes bug diagnosis plans in GitHub issue comments. The generator applies consistent formatting to produce reusable, GitHub-friendly Markdown plans that streamline issue resolution.

What's the best way to structure a reusable fix plan for GitHub issue resolution?▼

The best way to structure a reusable fix plan is using a template-based generator. It creates standardized, GitHub-friendly Markdown from exploration data, consistently documenting root cause, scope, testing, and risk.

Do I need specific exploration data fields to produce a comprehensive issue fix plan?▼

Yes, producing a comprehensive issue fix plan requires exploration results containing rootCause, relevantFiles, confidence, and understanding. The generator processes these specific fields to output a structured, GitHub-friendly plan.

Are there limitations when generating GitHub-friendly Markdown plans from exploration results?▼

A limitation is that plan generation strictly requires exploration results containing rootCause, relevantFiles, confidence, and understanding. Without these specific data fields, the generator cannot produce a comprehensive, structured fix plan.