speckit-taskstoissues

Convert Spec Kit project tasks into GitHub issues via MCP.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nShieldSolo/ArcticFactory.Preset --skill speckit-taskstoissues-nshieldsolo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/nShieldSolo/ArcticFactory.Preset/tree/main/.agent/skills/speckit-taskstoissues
Command: npx skills add https://github.com/nShieldSolo/ArcticFactory.Preset --skill speckit-taskstoissues-nshieldsolo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the conversion of project tasks defined in a Spec Kit repository into tracked, executable GitHub issues, eliminating manual issue creation and ensuring task dependencies and ordering are preserved.

Core Features & Use Cases

  • Task discovery: Runs the repository prerequisite script to locate and parse task manifests produced by the Spec Kit project structure.
  • Safety checks: Verifies the repository remote is a GitHub URL before any networked changes and enforces repository-matching safeguards.
  • Issue creation and ordering: Uses the GitHub MCP server to create issues that reflect each task and preserves dependency order so work can be executed in sequence.
  • Use Case: A developer or release manager prepares a new feature blueprint locally and wants all tasks exported as monitored GitHub issues for sprint planning.

Quick Start

Run the speckit-taskstoissues skill from the project root to create GitHub issues from the repository's current tasks, ensuring the repo has a configured GitHub remote.

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?

To convert Spec Kit tasks into GitHub issues, a skill runs the .specify prerequisite script to parse local task manifests and uses the GitHub MCP server to generate issues. It preserves task dependencies and ordering for sequential execution.

What prerequisites do I need to create GitHub issues from a Spec Kit repository?

Creating GitHub issues from a Spec Kit project requires running the .specify prerequisite script to discover task paths, a valid GitHub remote URL, and permission to create issues via the repository's GitHub MCP service.

Does the Spec Kit to GitHub issues conversion preserve task dependencies?

Yes, converting Spec Kit tasks to GitHub issues preserves task dependencies. The process creates issues that reflect each task while maintaining dependency order so work can be executed in sequence during sprint planning.

Can I use this task conversion if my repository remote is not a GitHub URL?

No, you cannot use this task conversion without a GitHub URL remote. The skill enforces safety checks verifying the git remote is a GitHub URL before executing any networked changes or creating issues via the MCP service.

Why does converting local tasks to GitHub issues require a prerequisite script?

Converting local tasks to GitHub issues requires a prerequisite script to locate and parse task manifests produced by the Spec Kit project structure. The script exposes absolute task paths needed to map local definitions to executable GitHub issues accurately.