plan-from-issue

Read GitHub issues, create a PLANS.md file, and sync it to the issue comment.

8|Updated Oct 26, 2025
One-click install
npx skills add https://github.com/sasamuku/dotfiles --skill plan-from-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-from-issue
Source: https://github.com/sasamuku/dotfiles/tree/main/.claude/skills/plan-from-issue
Command: npx skills add https://github.com/sasamuku/dotfiles --skill plan-from-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually updating GitHub issues with plans can be time-consuming. This skill automates the process of reading an issue, creating a PLANS.md file, and syncing it back to the issue comment.

Core Features & Use Cases

  • Automated Planning: Reads GitHub issues and generates a PLANS.md file with a single command.
  • Efficient Workflow: Combines reading, planning, and syncing into one step, reducing manual work.
  • Use Case: Quickly create and sync a plan for a GitHub issue, saving time and ensuring consistency.

Quick Start

Run the following command to create a plan for an issue:

plan-from-issue #123

Frequently Asked Questions about plan-from-issue

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

FAQPage Schema
How do I automate GitHub issue planning and sync plans back to comments?

Automating GitHub issue planning involves reading issue content, generating a PLANS.md file, and syncing it back to the issue comment automatically. This workflow reduces manual work by combining reading, planning, and syncing into a single command execution.

What is the best way to generate a PLANS.md file from GitHub issues?

Generating a PLANS.md file from GitHub issues is best handled by automating the extraction of issue details into a structured markdown format. This ensures consistent documentation of issue progress and eliminates the need to manually copy and format issue descriptions.

Do I need any specific GitHub permissions to sync a plan back to an issue comment?

Syncing a plan back to a GitHub issue comment requires write access to the repository to modify issue comments. The automation reads the issue, creates a local PLANS.md file, and then uses GitHub issue management APIs to update the issue thread.

Can I use workflow automation to document issue progress for multiple GitHub issues?

Workflow automation for documenting issue progress is designed to process GitHub issues individually by creating a specific PLANS.md file for each issue. You trigger the planning process by specifying the issue number, ensuring focused and accurate documentation.

Why does manual issue planning take so much time in GitHub issue management?

Manual issue planning in GitHub issue management takes time because it requires reading the issue, drafting a plan, and manually pasting it back as a comment. Automating this workflow eliminates repetitive copy-pasting and ensures consistent plan formatting.