---

name: plan-regenerate-issues description: "DEPRECATED: The notes/plan/ directory has been removed. Planning is now done directly through GitHub issues. See gh-read-issue-context and gh-post-issue-update skills instead." mcp_fallback: none category: plan deprecated: true user-invocable: false

Regenerate GitHub Issues Skill (DEPRECATED)

DEPRECATED: This skill is no longer used. The notes/plan/ directory has been removed. Planning is now done directly through GitHub issues.

See .claude/shared/github-issue-workflow.md for the new workflow.

Replacement Skills

• gh-read-issue-context - Read context from GitHub issues
• gh-post-issue-update - Post structured updates to GitHub issues

To Update Issues

Use the GitHub CLI directly:

Copy# Update issue title
gh issue edit <number> --title "New title"

# Update issue body
gh issue edit <number> --body "New body content"

# Add comment
gh issue comment <number> --body "Update message"

---

Legacy Documentation (for reference only)

Regenerate issue descriptions from updated plans.

When to Use

• After editing plan.md files
• Plan structure changes
• Need to update issue descriptions
• Before creating new issues

Quick Reference

Copy# Regenerate all issues
python3 scripts/regenerate_github_issues.py

# Regenerate specific section
python3 scripts/regenerate_github_issues.py --section 01-foundation

# Regenerate single component
./scripts/regenerate_single_issue.sh notes/plan/01-foundation/plan.md

Workflow

Copy# 1. Edit plan.md
vim notes/plan/01-foundation/plan.md

# 2. Regenerate github_issue.md
python3 scripts/regenerate_github_issues.py --section 01-foundation

# 3. Review changes
git diff notes/plan/01-foundation/github_issue.md

# 4. Commit both files
git add notes/plan/01-foundation/plan.md
git add notes/plan/01-foundation/github_issue.md
git commit -m "docs: update foundation plan"

Important Rules

Never edit github_issue.md manually

• Source of truth is plan.md
• Always regenerate after plan changes
• Regeneration preserves issue numbers

Script Behavior

The script:

• Extracts title from plan.md
• Formats sections for GitHub
• Preserves issue numbers if already created
• Updates labels based on phase
• Maintains hierarchy links
• Validates output format

Regeneration Options

All Issues

Copypython3 scripts/regenerate_github_issues.py
# Processes all plans in notes/plan/
# Updates all github_issue.md files

Section Only

Copypython3 scripts/regenerate_github_issues.py --section 02-shared-library
# Only processes plans in that section

Single Component

Copy./scripts/regenerate_single_issue.sh notes/plan/01-foundation/02-structure/plan.md
# Regenerates single github_issue.md

Validation After Regeneration

Copy# Validate format
./scripts/validate_issue_format.sh notes/plan/01-foundation/github_issue.md

# Test issue creation (dry-run)
./scripts/create_single_component_issues.py notes/plan/01-foundation/github_issue.md --dry-run

# Check for errors
./scripts/check_issue_format.sh

Error Handling

Scripts Available

• scripts/regenerate_github_issues.py - Regenerate all issues
• scripts/regenerate_single_issue.sh - Regenerate one issue
• scripts/validate_issue_format.sh - Validate format
• scripts/check_issue_format.sh - Check all issues

References

• Plan format: CLAUDE.md
• Related skill: plan-validate-structure for validation
• Related skill: plan-create-component for creating plans
• Script docs: scripts/README.md