speckit-taskstoissues

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

1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/stefaniuk/loadout --skill speckit-taskstoissues-stefaniuk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/stefaniuk/loadout/tree/main/.github/skills/speckit-taskstoissues
Command: npx skills add https://github.com/stefaniuk/loadout --skill speckit-taskstoissues-stefaniuk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using spec-kit workflows end up with long tasks.md files that must be manually turned into GitHub issues, which is repetitive and risks creating duplicates when the command is re-run. This Skill automates that conversion while checking existing issues first. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (stripping checkbox, [P], and [US#] markers) 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 \bT\d{3}\b pattern, skipping tasks that already have issues. - Safety Guards: Verifies the git remote is a GitHub URL before creating anything, enforces the speckit workflow mode, and supports pre/post extension hooks from .specify/extensions.yml. - Use Case: After running speckit task generation for a feature, invoke this Skill to publish every task as a trackable GitHub issue without manually copying titles or worrying about re-run 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 a GitHub issue titled with the task ID and description, such as `T001: Create project structure`.

How does the skill avoid creating duplicate GitHub issues?▼

Before creating anything, it lists existing open and closed issues via the GitHub MCP server and matches titles against the task ID pattern `\bT\d{3}\b`. Any task ID already present in an issue title is skipped and reported.

Does this work with repositories not hosted on GitHub?▼

No. The skill reads 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 prerequisites are needed before running tasks-to-issues conversion?▼

You need a spec-kit project with a .specify directory, an existing tasks.md file, a GitHub remote origin, and access to the GitHub MCP server. The skill runs check_prerequisites.py to resolve feature paths before proceeding.

Why are some tasks skipped when the skill runs again?▼

Tasks are skipped when an issue with a matching task ID already exists, which happens on re-runs after tasks.md is regenerated. The skill reports each skipped ID, for example `T001 already has an issue, skipping`.