speckit.taskstoissues

Convert feature tasks into dependency-ordered GitHub issues via the GitHub MCP server.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/hduoc2003/leviathan-guardian --skill speckit-taskstoissues-hduoc2003
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit.taskstoissues
Source: https://github.com/hduoc2003/leviathan-guardian/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/hduoc2003/leviathan-guardian --skill speckit-taskstoissues-hduoc2003

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually transcribing a feature's task list into GitHub issues is repetitive and error-prone, especially when tasks must stay dependency-ordered and tied to the correct repository. ## Core Features & Use Cases - Automated Issue Creation: Reads the tasks file produced by the spec-driven workflow and creates one GitHub issue per task using the GitHub MCP server. - Repository Safety Checks: Verifies the git remote is a GitHub URL and refuses to create issues in any repository that does not match the remote origin. - Use Case: After finalizing a feature's tasks.md in a spec-driven project, run this Skill to instantly file every task as a trackable GitHub issue in the matching repository. ## Quick Start Ask the assistant to convert the current feature's tasks into GitHub issues for this 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 a tasks.md file into GitHub issues?▼

Run the taskstoissues workflow, which parses the feature's tasks file via the check-prerequisites script and creates one GitHub issue per task using the GitHub MCP server. Issues are created in dependency order in the repository matching your git remote.

What tool creates GitHub issues from spec-driven tasks?▼

This Skill uses the GitHub MCP server's issue_write tool to create issues. It first resolves the feature directory and tasks path with the check-prerequisites bash script, then files each task as an issue.

Does it work with non-GitHub git remotes like GitLab?▼

No. The Skill explicitly checks that the git remote origin URL is a GitHub URL and stops if it is not. It will never create issues in repositories that do not match the remote URL.

Why does the task-to-issue conversion stop before creating issues?▼

The most common cause is a non-GitHub remote URL, which triggers a hard stop by design. It can also halt if the check-prerequisites script cannot locate the tasks file for the current feature.

Can I create issues in a different repository than my git remote?▼

No. The Skill enforces a strict rule that issues are only created in the repository matching the git remote origin URL, preventing accidental issue creation in unrelated repositories.