speckit-taskstoissues

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

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill speckit-taskstoissues-sethdavis512
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/sethdavis512/iridium/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/sethdavis512/iridium --skill speckit-taskstoissues-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually translating 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 for spec-kit projects. ## 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 on a new feature, invoke this Skill to publish every task as a labeled, ordered GitHub issue so the team can track implementation work immediately. ## Quick Start Ask the assistant to convert the current feature's tasks into GitHub issues, optionally passing a filter or label as an argument.

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 after generating tasks with spec-kit. It runs 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 is required before running 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 Skill aborts if the remote is not a GitHub URL.

Can I filter or label the GitHub issues created from tasks?

Yes, the command accepts an optional argument used as a filter or label for the created GitHub issues. The Skill instructs the agent to consider this user input before proceeding with issue creation.

Does taskstoissues work with non-GitHub remotes like GitLab?

No, the Skill explicitly checks that the git remote origin URL is a GitHub URL and refuses to proceed otherwise. It also never creates issues in repositories that do not match the configured remote.

What are extension hooks in spec-kit taskstoissues?

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