speckit-taskstoissues

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

9|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-taskstoissues-opsmill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/opsmill/infrahub-solution-ai-dc/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-taskstoissues-opsmill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually turning a tasks.md breakdown into GitHub issues is repetitive and error-prone, often producing duplicates or issues in the wrong repository. This Skill automates the conversion while checking for existing issues and validating the Git remote. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (e.g., - [ ] T001 Create project structure) and creates GitHub issues titled T001: Create project structure via the GitHub MCP server. - Deduplication: Fetches existing 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 and supports pre/post extension hooks from .specify/extensions.yml. - Use Case: After running spec-kit planning on a feature, invoke this Skill to publish all 25 tasks as GitHub issues in seconds, then re-run it later after regenerating tasks.md 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?▼

Invoke the taskstoissues skill in a spec-kit project. It runs check-prerequisites.sh to locate tasks.md, parses each checkbox line for its task ID and description, and creates one GitHub issue per task using the GitHub MCP server.

How does the skill avoid creating duplicate GitHub issues?▼

Before creating issues, it lists existing issues with the GitHub MCP list_issues tool and matches titles against the pattern \bT\d{3}\b. Any task ID already covered by an issue is skipped and reported, so re-running after regenerating tasks.md is safe.

Does taskstoissues work with GitLab or Bitbucket remotes?▼

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, so GitLab and Bitbucket are unsupported.

What project structure is required for taskstoissues?▼

The project must follow the spec-kit layout with a .specify directory containing scripts/bash/check-prerequisites.sh and a tasks.md file for the feature. Optionally, .specify/extensions.yml can define pre and post hooks.

Why are some tasks skipped when running taskstoissues?▼

Tasks are skipped when an existing issue title already contains their task ID, matched with word boundaries so tokens like ST001 or T0010 do not cause false matches. The skill reports each skipped ID, such as 'T001 already has an issue, skipping'.