speckit-taskstoissues

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

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/alidotcom2000/RSSFeedReader --skill speckit-taskstoissues-alidotcom2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/alidotcom2000/RSSFeedReader/tree/main/.github/skills/speckit-taskstoissues
Command: npx skills add https://github.com/alidotcom2000/RSSFeedReader --skill speckit-taskstoissues-alidotcom2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually creating GitHub issues from a spec-kit tasks.md file is repetitive and error-prone, and re-running the process can create duplicate issues. This Skill automates the conversion while checking existing issues to prevent duplicates. ## 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 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 turn every task in tasks.md into a tracked GitHub issue without worrying about duplicates on re-runs. ## Quick Start Ask the agent to convert the tasks in 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, strips checkbox and priority markers, and creates one GitHub issue per task with a title like `T001: Create project structure` using the GitHub MCP server.

How does the skill avoid creating duplicate GitHub issues?

It fetches existing open and closed issues with paginated list_issues calls and matches titles against the pattern `\bT\d{3}\b`. Any task ID already present in an issue title is skipped and reported instead of recreated.

Can I use this with a non-GitHub git remote?

No. The skill reads the remote.origin.url and stops if it is not a GitHub URL. It will never create issues in repositories that do not match the configured remote.

What prerequisites does taskstoissues need before running?

It requires a spec-kit project structure with a .specify directory, an existing tasks.md file, and the check-prerequisites PowerShell script. It also loads .specify/memory/constitution.md if present and checks extension hooks in .specify/extensions.yml.

Why are four-digit task IDs like T1000 supported?

The matching regex uses `\d{3}` rather than exactly three digits, so IDs beyond T999 still match issue titles. This ensures deduplication and creation keep working when a feature grows past 999 tasks.