speckit-taskstoissues

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

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/msaid1976/TSP-SmartAIRoute --skill speckit-taskstoissues-msaid1976
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/msaid1976/TSP-SmartAIRoute/tree/main/SmartRouteAI/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/msaid1976/TSP-SmartAIRoute --skill speckit-taskstoissues-msaid1976

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 remote. ## Core Features & Use Cases - Automated Issue Creation: Reads the tasks file produced by spec-kit and creates one GitHub issue per task using the GitHub MCP server. - Remote Safety Checks: Verifies the git remote is a GitHub URL and refuses to create issues in repositories that do not match the remote. - Extension Hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml for customizable workflows. - Use Case: After running spec-kit planning for a new feature, invoke this Skill to turn every task in tasks.md into a tracked 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 spec-kit tasks into GitHub issues?▼

Run the taskstoissues command in a spec-kit project after tasks have been generated. It executes check-prerequisites.sh to locate the tasks file, verifies the git remote is a GitHub URL, then creates one issue per task via the GitHub MCP server.

What are the prerequisites for tasks-to-issues conversion?▼

You need a spec-kit project structure with a .specify directory, an existing tasks file for the feature, and a git remote pointing to GitHub. The check-prerequisites script must run successfully with the --require-tasks flag.

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

No. The Skill explicitly checks that the remote origin URL is a GitHub URL and stops if it is not. It also refuses to create issues in any repository that does not match the configured remote.

What are extension hooks in spec-kit taskstoissues?▼

Hooks are commands declared in .specify/extensions.yml under hooks.before_taskstoissues or hooks.after_taskstoissues. Optional hooks are suggested to the user, while mandatory hooks are executed automatically before or after conversion.

Why does issue creation stop after checking the git remote?▼

The Skill halts when the remote is not a GitHub URL to prevent creating issues in the wrong repository. Confirm remote.origin.url points to the intended GitHub repository before retrying.