speckit-taskstoissues

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

5|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/theonlytruebigmac/n-central-rest-api-mcp --skill speckit-taskstoissues-theonlytruebigmac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/theonlytruebigmac/n-central-rest-api-mcp/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/theonlytruebigmac/n-central-rest-api-mcp --skill speckit-taskstoissues-theonlytruebigmac

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 deduplicating against existing issues. ## 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 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 a tasks.md breakdown for a new feature with spec-kit, run this Skill to publish every task as a tracked GitHub issue without duplicates. ## Quick Start Convert the tasks in my current spec-kit feature's tasks.md file into GitHub issues, skipping any that already exist.

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 task line, strips checkbox and priority markers, and creates a GitHub issue titled with the task ID and description through the GitHub MCP server.

How does the skill avoid creating duplicate GitHub issues?▼

It fetches existing issues with the GitHub MCP list_issues tool using cursor-based pagination, matches titles against the task ID pattern \bT\d{3}\b, and skips any task ID that already has an issue. Pagination stops once all task IDs are matched.

Does this work with GitLab or Bitbucket remotes?▼

No. The Skill checks the git remote origin URL and only proceeds if it is a GitHub URL, since issue creation relies on the GitHub MCP server. It will not create issues in non-GitHub repositories.

What project structure is required to run 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 Skill runs check-prerequisites.sh to locate the tasks file and available design documents.

What are extension hooks in .specify/extensions.yml?▼

They are optional or mandatory commands registered under hooks.before_taskstoissues or hooks.after_taskstoissues that run before or after conversion. Hooks with enabled set to false are skipped, and non-empty condition fields are left to the HookExecutor.