speckit-taskstoissues

Convert tasks from a markdown file into GitHub issues.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/szaher/agentspec --skill speckit-taskstoissues-szaher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/szaher/agentspec/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/szaher/agentspec --skill speckit-taskstoissues-szaher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of GitHub issues from a list of tasks, streamlining project management and ensuring work items are tracked.

Core Features & Use Cases

  • Task Conversion: Converts tasks defined in a tasks.md file into actionable GitHub issues.
  • Automated Issue Creation: Leverages the GitHub API to create issues in the correct repository.
  • Use Case: After a feature breakdown, use this skill to automatically create individual GitHub issues for each sub-task, assigning them to the appropriate team members and setting up tracking.

Quick Start

Convert tasks from the tasks.md file into GitHub issues for the current repository.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert markdown tasks into GitHub issues automatically?

Converting markdown tasks into GitHub issues is done by parsing a `tasks.md` file, identifying individual work items, and using the GitHub API to programmatically create issues in the associated repository.

What is the best way to automate GitHub issue creation from a feature breakdown?

Automating GitHub issue creation from a feature breakdown involves mapping parsed markdown tasks to the GitHub API. This Skill retrieves your GitHub remote URL and generates an actionable issue for each sub-task, enabling automatic team assignment and project tracking.

Do I need a specific project structure to convert markdown tasks to GitHub issues?

Yes, you need a spec-kit project structure to convert markdown tasks. Your repository must contain a `.specify/` directory for the task file and have a GitHub-compatible remote URL configured so the Skill can authenticate and create issues correctly.

How does automated task conversion find the correct GitHub repository?

Automated task conversion finds the correct GitHub repository by retrieving the GitHub remote URL directly from your local project configuration. It uses this URL to target the right repository when programmatically creating issues from your markdown tasks.

Can I use this markdown to GitHub issues conversion with any Git remote?

No, you cannot use this markdown to GitHub issues conversion with just any Git remote. It requires a GitHub-compatible remote URL to successfully authenticate and programmatically create issues within the target repository.