speckit-taskstoissues

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually translating a tasks.md breakdown into GitHub issues is repetitive and error-prone, often producing duplicates when re-run. This Skill automates the conversion of spec-kit task lists into GitHub issues while checking existing issues to prevent duplicates. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (stripping checkbox, [P], and [US#] markers) 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 extension hooks via .specify/extensions.yml for pre/post execution. - Use Case: After generating a tasks.md file for a new feature with spec-kit, invoke this Skill to publish every task as a tracked GitHub issue in the matching repository without creating duplicates on re-runs. ## Quick Start Ask the AI 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 GitHub 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 via the GitHub MCP list_issues tool with pagination, matches titles against the task ID pattern `\bT\d{3}\b`, and skips any task ID that already has an issue.

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

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

Can I use extension hooks with the taskstoissues command?▼

Yes, if .specify/extensions.yml exists, hooks under hooks.before_taskstoissues and hooks.after_taskstoissues are processed. Mandatory hooks execute automatically, while optional hooks are suggested for manual execution.

Why does issue creation fail or get skipped for some tasks?▼

Issues are skipped when the task ID already exists in the repository's issues, or creation never starts if the git remote is not a GitHub URL. Invalid extensions.yml files are reported but do not block execution.