create-issues

Convert markdown implementation plans into linked issues with dependencies.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/charly-vibes/wai --skill create-issues-charly-vibes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issues
Source: https://github.com/charly-vibes/wai/tree/main/.agents/skills/create-issues
Command: npx skills add https://github.com/charly-vibes/wai --skill create-issues-charly-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of issues and their dependencies in issue tracking systems, directly from an implementation plan, saving significant project management overhead.

Core Features & Use Cases

  • Automated Issue Generation: Creates issues with detailed descriptions, file references, and acceptance criteria based on a provided plan.
  • Dependency Management: Automatically links issues to establish a clear workflow and track progress dependencies.
  • Use Case: Convert a feature development plan into a series of linked GitHub Issues, ensuring each task is tracked and its prerequisites are met.

Quick Start

Use the create-issues skill to convert the plan in 'implementation_plan.md' into GitHub issues.

Frequently Asked Questions about create-issues

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

FAQPage Schema
How do I convert an implementation plan into GitHub issues with dependencies?

To convert an implementation plan into GitHub issues with dependencies, you can use the create-issues skill to parse markdown plans and generate precise, runnable commands for issue creation and dependency linking.

What is the best way to automate task tracking from a markdown plan?

Automating task tracking from a markdown plan involves parsing the document to define issue titles, bodies, file references, and acceptance criteria, then automatically generating linked issues to establish a clear workflow.

Can I use this to create issues in Beads or only GitHub Issues?

You can create tracked issues in both Beads and GitHub Issues, as the skill generates precise, runnable commands for issue creation and dependency linking across supported issue trackers.

Do I need to manually define issue dependencies when converting a plan?

You do not need to manually define issue dependencies when converting a plan, because the skill automatically links issues to establish a clear workflow and track progress prerequisites.

What markdown plan structure is required to generate issues with acceptance criteria?

The markdown plan structure must contain information that can be parsed to define issue titles, bodies, file references, and acceptance criteria, enabling the generation of detailed tracked issues.