speckit-taskstoissues

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

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-taskstoissues-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-taskstoissues-narenkarthikbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually turning a generated 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 first so each task maps to exactly one issue. ## 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 form T001: <description> via the GitHub MCP server. - Deduplication: Fetches existing issues with cursor-based pagination, matches task IDs using the \bT\d{3}\b pattern, and skips tasks that already have issues. - Safety guards: Verifies the git remote is a GitHub URL before creating anything and never creates issues in repositories that do not match the remote. - Extension hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml. - Use Case: After running the spec-kit tasks phase for a new feature, invoke this Skill to publish every task as a trackable GitHub issue for the team board without duplicates. ## 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 the taskstoissues skill after generating tasks.md. It parses each checkbox line, strips markers like [P] and [US#], and creates a GitHub issue titled `T001: <description>` for every task using the GitHub MCP server.

How does the skill avoid creating duplicate GitHub issues?

Before creating anything, it lists existing issues with cursor-based pagination and matches titles against the `\bT\d{3}\b` pattern. Any task ID already covered by an issue is skipped and reported, so re-running the skill is safe.

Does taskstoissues work with non-GitHub remotes like GitLab?

No. The skill reads the git remote origin URL and only proceeds if it is a GitHub URL, since issue creation relies on the GitHub MCP server. It explicitly refuses to create issues in repositories that do not match the remote.

What prerequisites are required before running taskstoissues?

The project must be initialized with spec-kit (a .specify directory must exist) and contain a tasks.md file. The skill runs check-prerequisites.sh with --require-tasks to resolve the feature directory and available design artifacts.

Why are some tasks skipped when creating GitHub issues?

Tasks are skipped when an existing issue title already contains their task ID, matched with word boundaries so tokens like ST001 or T0010 do not cause false matches. The skill reports each skipped ID, for example 'T001 already has an issue, skipping'.