speckit-taskstoissues

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the manual and error-prone process of turning task lists found in a spec-kit project into actionable, dependency-ordered GitHub issues, ensuring tasks are tracked and assigned within the correct repository.

Core Features & Use Cases

  • Preflight validation: Runs the .specify preflight script to discover the FEATURE_DIR and an AVAILABLE_DOCS list and extracts the absolute path to tasks.
  • Safe issue creation: Verifies the Git remote is a GitHub URL and uses a GitHub MCP server to create an issue per task while preserving dependency ordering and labels.
  • Use Case: Convert design and implementation tasks for a new feature into individual issues so engineering teams can triage, assign, and schedule work without manual transcription.

Quick Start

Convert the feature tasks discovered by the repository's .specify preflight script into dependency-ordered GitHub issues for the remote 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?

To convert spec-kit tasks into GitHub issues, this Skill runs the .specify preflight script to locate task paths, verifies the Git remote is a GitHub URL, and uses an MCP server to create issues. It preserves dependency ordering and labels for each task during the migration.

Can I migrate dependency-ordered tasks to GitHub issues from a spec-kit project?

Yes, you can migrate dependency-ordered tasks from a spec-kit project. The Skill extracts task absolute paths via the preflight script and creates GitHub issues that maintain the original dependency sequence and labels for accurate development planning.

Does creating GitHub issues from spec-kit tasks require a specific project structure?

Creating GitHub issues from spec-kit tasks requires the repository to use the spec-kit .specify project structure. The Skill relies on this structure to discover the FEATURE_DIR, locate available docs, and extract absolute paths to the tasks.

What happens if my Git remote is not a GitHub URL when migrating tasks to issues?

If your Git remote is not a GitHub URL, the Skill will fail to create issues. Safe issue creation requires verifying the remote repository is hosted on GitHub before using the MCP server to generate the dependency-ordered issues.

How does the spec-kit preflight script locate tasks for GitHub issue creation?

The spec-kit preflight script locates tasks by discovering the FEATURE_DIR and an AVAILABLE_DOCS list within the .specify project structure. It extracts the absolute path to the tasks file, which is then used to generate dependency-ordered GitHub issues.

Why use a task-to-issue automation Skill for spec-kit feature development?

Using task-to-issue automation for spec-kit development eliminates manual transcription errors. It automatically turns design and implementation task lists into tracked GitHub issues, allowing engineering teams to triage, assign, and schedule work efficiently.