speckit-taskstoissues

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-taskstoissues-wu-mao-chia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/WU-MAO-CHIA/AI_tset_platfrom/tree/main/.opencode/skills/speckit-taskstoissues
Command: npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-taskstoissues-wu-mao-chia

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. This Skill automates that conversion directly from spec-kit design artifacts. ## Core Features & Use Cases - Automated Issue Creation: Reads the feature's tasks file and creates one GitHub issue per task using the GitHub MCP server. - Remote Safety Guard: Verifies the git remote is a GitHub URL and refuses to create issues in any repository that does not match the remote. - Extension Hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml for customizable workflow steps. - Use Case: After running spec-kit planning for a new feature, invoke this Skill to instantly populate the GitHub repository with actionable, ordered issues ready for the team to pick up. ## 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?▼

Invoke the taskstoissues command in a spec-kit project. It runs the check-prerequisites script to locate the tasks file, verifies the git remote is a GitHub URL, then creates one issue per task through the GitHub MCP server.

What is required before converting tasks to GitHub issues?▼

You need a spec-kit project with a .specify directory, an existing tasks file for the feature, and a git remote origin pointing to a GitHub repository. The GitHub MCP server must also be available to create the issues.

Does taskstoissues 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 will never create issues in repositories that do not match the configured remote.

Can I run custom hooks before or after issue creation?▼

Yes. Define hooks under hooks.before_taskstoissues or hooks.after_taskstoissues in .specify/extensions.yml. Hooks can be optional or mandatory, and disabled hooks are skipped automatically.

Why does taskstoissues skip creating issues for my repository?▼

The most common cause is a remote origin that is not a GitHub URL, since the skill refuses to proceed in that case. Also confirm the prerequisites script found a valid tasks file for the current feature.