speckit-taskstoissues

Parse tasks.md and create GitHub issues via MCP server.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/igoorstraviinsky-dev/produtos --skill speckit-taskstoissues-igoorstraviinsky-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/igoorstraviinsky-dev/produtos/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/igoorstraviinsky-dev/produtos --skill speckit-taskstoissues-igoorstraviinsky-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a breakdown of work tasks (from tasks.md) into GitHub issues to manage work items in a project.

Core Features & Use Cases

  • Parse the tasks.md to extract tasks with metadata.
  • Verify the Git remote is a GitHub URL and only create issues in the matching repository.
  • Create issues on GitHub for each task via the MCP server, linking them to the originating tasks list.
  • Use case: After a task breakdown, automatically generate issues for tracking progress in a GitHub project.

Quick Start

Run the speckit-taskstoissues script from the repo root after completing your tasks.md breakdown to generate GitHub issues for each task.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I automatically create GitHub issues from a markdown task list?

To create GitHub issues from a markdown task list, this Skill parses the tasks.md file and uses the MCP server to programmatically instantiate issues for each task. It links the generated issues back to the originating project tracking list.

How does issue generation verify the correct GitHub remote repository?

Issue generation verifies the correct repository by checking that the Git remote is a valid GitHub URL. It ensures issues are created only in the repository that matches the remote URL, preventing accidental pushes to the wrong project.

Can I use this task automation in a non-spec-kit style project?

No, this task automation is designed specifically for spec-kit style projects. It requires a valid Git remote and a completed tasks.md file breakdown to properly extract metadata and generate the corresponding GitHub issues.

What is the best way to turn project management tasks into tracked GitHub issues?

The best way to turn project management tasks into tracked GitHub issues is running this script from the repo root after completing your tasks.md breakdown. It automatically extracts the work items and instantiates them via the MCP server.

Why does my GitHub issue generation fail when using the MCP server?

GitHub issue generation fails if the project lacks a valid Git remote or if the remote URL does not match a GitHub repository. The script requires a valid GitHub origin to programmatically instantiate issues and link them correctly.

Do I need to manually link tasks.md entries to individual GitHub issues?

No, you do not need to manually link tasks.md entries to GitHub issues. The script parses the task breakdown, extracts the metadata, and uses the MCP server to programmatically create and link each issue automatically.