create-issues

Translate worktree development plans into structured GitHub issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/LPdsgn/claude-toolkit --skill create-issues-lpdsgn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issues
Source: https://github.com/LPdsgn/claude-toolkit/tree/main/plugins/dev-tools/skills/create_issues
Command: npx skills add https://github.com/LPdsgn/claude-toolkit --skill create-issues-lpdsgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates a worktree development plan into a set of well-structured GitHub issues, enabling clear coordination, dependency tracking, and progress visibility across teams.

Core Features & Use Cases

  • Epic, feature, task, and integration templates are generated from the plan to mirror the work breakdown.
  • Supports multiple worktrees and dependencies to orchestrate parallel vs sequential work.
  • Use Case: After finalizing a worktree plan, feed it to this Skill to auto-create a hierarchy of issues and a coordination roadmap.

Quick Start

  • Provide a path to a worktree plan file to generate the full issue hierarchy.
  • Provide a comma-separated list of features to generate feature-level issues and a coordinating epic.
  • Provide an epic name to create issues scoped to that epic.

Frequently Asked Questions about create-issues

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

FAQPage Schema
How do I generate GitHub issues from a worktree development plan?

To generate GitHub issues from a worktree plan, provide the plan file path to automatically create a structured hierarchy of Epics, Features, Tasks, and Integration issues with defined dependencies and acceptance criteria.

Can I create GitHub issues for multiple worktrees to coordinate parallel work?

Yes, you can create GitHub issues for multiple worktrees. The generated issue hierarchy maps dependencies across worktrees to orchestrate parallel versus sequential development work effectively.

What is the best way to break down an epic into structured GitHub issues?

The best way to decompose an epic into structured GitHub issues is providing the epic name or a comma-separated feature list to auto-generate task-level issues with work requirements and coordinating epics.

How do dependency mapping and acceptance criteria work when generating issues?

Dependency mapping and acceptance criteria are automatically defined within the generated GitHub issue templates, linking Features and Tasks across multiple worktrees to ensure clear coordination and progress visibility.

Do I need a pre-existing plan file to generate feature-level GitHub issues?

No, you do not need a pre-existing plan file to generate feature-level GitHub issues. You can provide a comma-separated list of features directly to generate feature issues alongside a coordinating epic.