speckit-taskstoissues

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

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/damian-garces/spec-driven-development --skill speckit-taskstoissues-damian-garces
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/damian-garces/spec-driven-development/tree/main/spec-driven-project/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/damian-garces/spec-driven-development --skill speckit-taskstoissues-damian-garces

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually translating a spec-kit tasks.md file into GitHub issues is repetitive and error-prone, often producing duplicates or issues in the wrong repository. This Skill automates the conversion while verifying the Git remote and skipping tasks that already have issues. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (stripping checkbox, [P], and [US#] markers) and creates GitHub issues titled in the canonical T001: description format via the GitHub MCP server. - Deduplication: Fetches existing issues with cursor-based pagination and matches task IDs using the \bT\d{3}\b pattern, skipping any task that already has an issue. - Safety Guards: Verifies the Git remote is a GitHub URL before creating anything and supports pre/post extension hooks defined in .specify/extensions.yml. - Use Case: After running spec-kit planning for a feature, invoke this Skill to turn 30 generated tasks into tracked GitHub issues without re-creating ones from a previous run. ## 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?

Invoke the speckit-taskstoissues skill in a spec-kit project. It runs check-prerequisites.sh to locate tasks.md, parses each task line, and creates GitHub issues titled `T001: 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, reporting each skip.

Does speckit-taskstoissues work with non-GitHub remotes?

No. The skill reads the Git remote via `git config --get remote.origin.url` and only proceeds if it is a GitHub URL. It never creates issues in repositories that do not match the remote URL.

What task ID formats are supported when matching issues?

Task IDs are a T followed by at least three digits, such as T001 or T1000. The regex \bT\d{3}\b handles four-digit and longer IDs and recognizes titles written as `T001 ...`, `T001: ...`, or `[T001] ...`.

What are extension hooks in spec-kit taskstoissues?

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.