speckit-taskstoissues

Name: speckit-taskstoissues
Availability: InStock
Author: ab0umar

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

Updated Sep 19, 2026

Search Tags:#github issues #project tracking #spec-driven development #spec-kit #GitHub MCP #issue automation #task conversion

Ready to run

npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill speckit-taskstoissues-ab0umar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill speckit-taskstoissues-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually translating a feature's task list into trackable GitHub issues is repetitive and error-prone, especially when tasks must respect dependency order and match 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 Validation: Verifies that the git remote origin is a GitHub URL and refuses to create issues in repositories that do not match the remote. - Extension Hook Support: Runs optional or mandatory pre/post hooks declared in .specify/extensions.yml before and after conversion. - Use Case: After generating tasks.md for a new feature with spec-kit, invoke this Skill to publish every task as a labeled, ordered GitHub issue in the matching repository for team tracking. ## Quick Start Ask the AI 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 after generating tasks.md with spec-kit. It executes check-prerequisites.ps1 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 is required before creating GitHub issues from tasks?▼

You need a spec-kit project with a .specify directory, an existing tasks.md 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 filter or label the GitHub issues created from tasks?▼

Yes. The command accepts an optional argument hint for a filter or label, which is passed as user input and considered before the conversion proceeds.

What are extension hooks in spec-kit taskstoissues?▼

Hooks are commands declared under hooks.before_taskstoissues or hooks.after_taskstoissues in .specify/extensions.yml. Enabled hooks run before or after conversion, with optional hooks prompting the user and mandatory hooks executing automatically.