speckit-taskstoissues

Convert spec-kit tasks into deduplicated GitHub issues in dependency order.

Updated Aug 19, 2026

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

Ready to run

npx skills add https://github.com/Base-Analitica/mouse-hub --skill speckit-taskstoissues-base-analitica

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/Base-Analitica/mouse-hub/tree/main/.jcode/skills/speckit-taskstoissues
Command: npx skills add https://github.com/Base-Analitica/mouse-hub --skill speckit-taskstoissues-base-analitica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually turning a 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 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: <description>` 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 publish every task as a trackable GitHub issue for your team without manual copy-pasting. ## 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 with a tasks.md file. It parses each checkbox task, strips markers like [P] and [US#], and creates issues titled `T001: <description>` through the GitHub MCP server.

How does the Skill avoid creating duplicate GitHub issues?▼

It fetches existing open and closed issues with perPage 100 and cursor pagination, matching titles against the pattern \bT\d{3}\b. Tasks whose IDs already appear in an issue title are skipped and reported.

What are the requirements for running tasks-to-issues conversion?▼

You need a spec-kit project structure with a .specify directory, a tasks.md file, and a git remote pointing to GitHub. The Skill refuses to create issues if the remote is not a GitHub URL.

Does it support task IDs with more than three digits?▼

Yes. The matching pattern \bT\d{3}\b accepts four-digit and longer IDs such as T1000, which matters once a project exceeds 999 tasks. Shorter patterns would silently miss those tasks.

What are extension hooks in the tasks-to-issues workflow?▼

Hooks are commands defined under hooks.before_taskstoissues or hooks.after_taskstoissues in .specify/extensions.yml. Optional hooks are suggested to the user, while mandatory hooks are executed automatically before the workflow continues.