speckit-taskstoissues

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually turning a tasks.md breakdown into GitHub issues is repetitive and error-prone, and re-running the process often creates duplicate issues. This Skill automates the conversion while checking existing issues first so each task maps to exactly one issue. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (stripping checkbox, [P], and [US#] markers) and creates GitHub issues titled in the canonical T001: <description> format. - Deduplication: Fetches existing open and closed issues with cursor-based pagination, matches task IDs using a word-boundary regex, and skips tasks that already have issues. - Safety Guards: Verifies the git remote is a GitHub URL before creating anything and supports pre/post extension hooks from .specify/extensions.yml. - Use Case: After generating an implementation plan with spec-kit, run this Skill to publish all 40 tasks as dependency-ordered GitHub issues for team tracking, then re-run it safely after tasks.md is regenerated without creating duplicates. ## Quick Start Ask the agent to convert the current feature's tasks.md 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 this Skill in a spec-kit project after tasks.md exists. It parses each task line, strips checkbox and priority markers, and creates GitHub issues titled in the form `T001: <description>` through the GitHub MCP server.

How does the Skill avoid creating duplicate GitHub issues?

Before creating anything, it lists existing open and closed issues with cursor-based pagination and matches titles against the task ID pattern \bT\d{3}\b. Tasks that already have a matching issue are skipped and reported.

Does this work with GitLab or Bitbucket remotes?

No. The Skill reads the git remote origin URL and only proceeds if it is a GitHub URL, since issue creation relies on the GitHub MCP server. It explicitly refuses to create issues in repositories that do not match the remote.

What prerequisites are required before running tasks-to-issues conversion?

The project must follow the spec-kit structure with a .specify directory and a generated tasks.md. The Skill runs check-prerequisites.ps1 with -RequireTasks to resolve the feature directory and available design documents.

Why are some tasks skipped when the Skill runs?

Tasks are skipped when an existing issue title already contains their task ID, such as `T001: ...` or `[T001] ...`. This happens when the Skill is re-run after tasks.md is regenerated, preventing duplicate issues.