plan-regenerate-issues

Regenerate GitHub issue files from updated plan.md documents using Python scripts.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/mvillmow/ml-odyssey --skill plan-regenerate-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-regenerate-issues
Source: https://github.com/mvillmow/ml-odyssey/tree/main/.claude/skills/plan-regenerate-issues
Command: npx skills add https://github.com/mvillmow/ml-odyssey --skill plan-regenerate-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? This Skill automates the regeneration of github_issue.md files from plan.md documents, ensuring that GitHub issue descriptions are always up-to-date with the latest planning changes. It streamlines issue creation, saving time and ensuring consistency.

Core Features & Use Cases:

  • Automated Issue Update: Regenerates issue files after plan modifications, preserving existing issue numbers for continuity.
  • Plan-to-Issue Sync: Ensures consistency between planning documents and GitHub issues, reducing manual data entry.
  • Use Case: After refining a project plan in plan.md, use this skill to automatically regenerate the corresponding github_issue.md file. This ensures that when you create the actual GitHub issue, its description accurately reflects the latest plan.

Quick Start: Use the plan-regenerate-issues skill to regenerate the GitHub issue file for 'notes/plan/01-foundation/plan.md'.

Frequently Asked Questions about plan-regenerate-issues

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

FAQPage Schema
How do I keep GitHub issues synchronized with my plan.md file changes?

Regenerate GitHub issues automatically from your plan.md documents to sync issue descriptions with the latest planning updates. This Skill extracts titles, formats sections, preserves issue numbers, and updates labels based on phase, ensuring GitHub issues always reflect your current plan without manual data entry.

Can I automate updating issue descriptions after editing my project plan?

Yes. After modifying plan.md files, use this Skill to regenerate github_issue.md files automatically. It maintains existing issue numbers for continuity, updates labels and hierarchy links, and validates the output format so your GitHub issues stay consistent with plan changes.

What happens to existing issue numbers when I regenerate issues from a plan?

Existing issue numbers are preserved during regeneration. The Skill extracts and maintains these identifiers so you avoid creating duplicate issues in GitHub while ensuring descriptions and metadata reflect your updated plan structure.

How does plan-to-issue conversion work with GitHub labels and issue hierarchy?

The Skill updates labels based on the phase defined in your plan.md, maintains hierarchy links between related issues, and formats sections for GitHub compatibility. This ensures generated issues reflect both your planning structure and organizational taxonomy.

Do I need to manually create issues in GitHub after regenerating the files?

The Skill regenerates the github_issue.md file with up-to-date descriptions and metadata. You then create the actual GitHub issues from these regenerated files, which ensures your issue descriptions accurately reflect the latest plan without manual rewrites.