speckit-taskstoissues

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

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/misadecastro/imperial-soccer --skill speckit-taskstoissues-misadecastro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/misadecastro/imperial-soccer/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/misadecastro/imperial-soccer --skill speckit-taskstoissues-misadecastro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the conversion of informal task lists into actionable, dependency-ordered GitHub issues so teams can track and implement features reliably without manual issue authoring.

Core Features & Use Cases

  • Automated Issue Creation: Parses tasks produced by the spec-kit tooling and creates representative GitHub issues.
  • Dependency Ordering: Retains task dependency information to create a logical issue order for implementation planning.
  • Safety Checks: Verifies the git remote is a GitHub URL and refuses to create issues in mismatched repositories.
  • Use Case: When a design artifact generates a task list for a new feature, use this Skill to quickly produce a cleaned, ordered set of GitHub issues that match your repository and workflow.

Quick Start

Run the skill to locate the .specify task list, verify your git remote is a GitHub URL, and create dependency-ordered issues in the matching 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 automatically?

This Skill creates dependency-ordered GitHub issues by parsing task files generated in the .specify directory during feature development. It ensures absolute path resolution for task files and uses the GitHub MCP server to automate issue creation within the matching repository.

Does the GitHub issue automation work with repositories outside of spec-kit?

This Skill specifically processes tasks from repositories using the spec-kit project structure with a .specify directory. It will refuse to create issues in repositories that do not match the verified GitHub git remote URL.

Why does GitHub issue creation fail in mismatched repositories?

The Skill performs a safety check by validating the git remote is a GitHub URL before creating issues. It intentionally prevents issue creation in mismatched repositories to avoid populating the wrong project with automated tasks.

How are task dependencies handled when creating GitHub issues?

The Skill retains task dependency information from the spec-kit task files to create a logical issue order. This dependency ordering helps teams track and implement features reliably by following a structured implementation plan.

What do I need to generate GitHub issues from a spec-kit task list?

You need a repository using the spec-kit project structure with a .specify directory and tasks generated by the check-prerequisites script. The Skill also requires a valid GitHub git remote URL and access to the GitHub MCP server to create the issues.

Can I use this to create issues from tasks without the .specify directory?

No, the .specify directory is required because the Skill uses it to locate and parse task files generated by spec-kit tooling. It ensures absolute path resolution for task files before converting them into dependency-ordered GitHub issues.