speckit-taskstoissues

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

Updated Jul 16, 2026

Search Tags:#project management #github issues #deduplication #spec-kit #issue automation #task conversion #github mcp

Ready to run

npx skills add https://github.com/Carl-Fabri/TestAngularSpecDriven --skill speckit-taskstoissues-carl-fabri

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/Carl-Fabri/TestAngularSpecDriven/tree/main/test-angular/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/Carl-Fabri/TestAngularSpecDriven --skill speckit-taskstoissues-carl-fabri

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 generating a task breakdown with spec-kit, run this Skill to publish every task as a trackable GitHub issue without re-checking which ones already exist. ## Quick Start Ask the assistant 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 tasks.md into GitHub issues automatically?▼

Run this Skill in a spec-kit project and it parses each checkbox line in tasks.md, strips markers like [P] or [US#], 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?▼

It fetches existing open and closed issues with the GitHub MCP list_issues tool, matches titles against the `\bT\d{3}\b` pattern, and skips any task ID that already has an issue. Pagination stops once all task IDs are accounted for.

What project setup is required to use this Skill?▼

The project must follow the spec-kit structure with a .specify directory containing scripts and a tasks.md file for the feature. The Git remote origin must also be a GitHub URL, otherwise the Skill stops before creating issues.

Can I use this Skill with a non-GitHub remote repository?▼

No. The Skill explicitly checks `git config --get remote.origin.url` and only proceeds if the remote is a GitHub URL, since it creates issues through the GitHub MCP server.

What are extension hooks in the taskstoissues workflow?▼

Hooks are optional or mandatory commands defined in .specify/extensions.yml under hooks.before_taskstoissues or hooks.after_taskstoissues. Enabled hooks run before or after issue creation, with mandatory hooks blocking until they finish.