speckit-taskstoissues

Convert spec-kit tasks into deduplicated GitHub issues via the GitHub MCP server.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-taskstoissues-eovipmak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/eovipmak/unattended-iso/tree/main/.commandcode/skills/speckit-taskstoissues
Command: npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-taskstoissues-eovipmak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually turning a spec-kit tasks.md file into GitHub issues is repetitive and error-prone, and re-running the process often creates 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.md entries (stripping checkboxes and [P]/[US#] markers) and creates GitHub issues titled T001: <description> through 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 the team without worrying about duplicates on re-runs. ## 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 generating tasks.md. It parses each task line, strips checkbox and priority markers, and creates one GitHub issue per task titled with the task ID and description via the GitHub MCP server.

Does it create duplicate issues when run twice?

No. Before creating anything, it fetches existing open and closed issues with paginated list_issues calls and matches titles against the task ID pattern \bT\d{3}\b. Tasks that already have an issue are skipped and reported.

What project structure is required for this Skill?

It requires a spec-kit project with a .specify directory containing scripts and a tasks.md file for the current feature. The repository's git remote origin must also be a GitHub URL, otherwise the Skill stops before creating issues.

Why does the Skill refuse to create issues in my repository?

It checks the output of git config --get remote.origin.url and only proceeds when the remote is a GitHub URL. This guard prevents accidentally creating issues in repositories that do not match the remote.

Can I run custom hooks before or after issue creation?

Yes. If .specify/extensions.yml defines entries under hooks.before_taskstoissues or hooks.after_taskstoissues, the Skill executes mandatory hooks and offers optional ones, skipping hooks with unresolvable conditions.