speckit-taskstoissues

Convert spec-kit tasks into dependency-ordered GitHub issues with deduplication.

2|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/guestgraph/engine --skill speckit-taskstoissues-guestgraph
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/guestgraph/engine/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/guestgraph/engine --skill speckit-taskstoissues-guestgraph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually turning a tasks.md file into GitHub issues is repetitive and error-prone, and re-running the process risks creating duplicate issues. This Skill automates the conversion while checking existing issues so each task gets exactly one canonical issue. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks from tasks.md, strips checkbox and marker prefixes, and creates GitHub issues titled T001: <description> via the GitHub MCP server. - Deduplication: Fetches existing open and closed issues with cursor-based pagination and matches task IDs using the pattern \bT\d{3}\b, skipping 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 every task as a trackable GitHub issue for your team without duplicates. ## Quick Start Ask the AI 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 the taskstoissues command in a spec-kit project. It reads tasks.md via the check-prerequisites script, verifies the GitHub remote, then creates one issue per task titled with the task ID and description.

How does the skill avoid creating duplicate GitHub issues?▼

It fetches existing open and closed issues using the GitHub MCP list_issues tool with pagination, matches titles against the pattern \bT\d{3}\b, and skips any task ID that already has an issue, reporting each skip.

Does taskstoissues work with non-GitHub remotes like GitLab?▼

No. The skill checks the git remote origin URL and only proceeds if it is a GitHub URL. It explicitly refuses to create issues in repositories that do not match the remote.

What happens when tasks have four-digit IDs like T1000?▼

The deduplication regex uses \d{3} rather than \d{3}, so IDs with four or more digits still match correctly. Word boundaries prevent partial matches such as T100 inside T1000 or tokens like ST001.

What are the prerequisites for running taskstoissues?▼

You need a spec-kit project structure with a .specify directory, an existing tasks.md for the feature, a GitHub remote origin, and access to the GitHub MCP server. Extension hooks in .specify/extensions.yml are optional.