speckit-taskstoissues

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

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/Sergiotsk/Interstellar --skill speckit-taskstoissues-sergiotsk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/Sergiotsk/Interstellar/tree/main/interstellar/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/Sergiotsk/Interstellar --skill speckit-taskstoissues-sergiotsk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually translating a tasks.md file 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 properly titled GitHub issues while skipping tasks that already have issues. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (e.g., - [ ] T001 Create project structure) and creates GitHub issues with canonical titles like T001: Create project structure via the GitHub MCP server. - Deduplication: Fetches existing issues with cursor-based pagination and matches task IDs using the pattern \bT\d{3}\b, skipping any task that already has an issue. - Extension Hooks: Supports optional and mandatory pre/post hooks defined in .specify/extensions.yml for workflow customization. - Use Case: After generating a tasks.md file for a new feature with spec-kit, invoke this Skill to publish every task as a trackable GitHub issue in the repository matching the git remote, 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 a tasks.md file into GitHub issues?▼

Run this Skill in a spec-kit project and it parses each checkbox line in tasks.md, strips markers like [P] and [US#], and creates issues titled `T001: <description>` using the GitHub MCP server. Tasks that already have matching issues are skipped.

How does the Skill avoid creating duplicate GitHub issues?▼

It fetches existing open and closed issues with perPage 100 and cursor-based pagination, matching titles against the pattern \bT\d{3}\b. Pagination stops once all task IDs are matched, and any matched task is reported as skipped.

Does this work with non-GitHub remotes like GitLab or Bitbucket?▼

No. The Skill checks `git config --get remote.origin.url` and only proceeds if the remote is a GitHub URL. It explicitly refuses to create issues in repositories that do not match the remote URL.

What project structure is required to run this Skill?▼

It requires a spec-kit project with a .specify/ directory containing the check-prerequisites.ps1 script and a tasks.md file for the current feature. It optionally loads .specify/memory/constitution.md and .specify/extensions.yml hooks.

Why are four-digit task IDs like T1000 supported?▼

The matching regex uses \d{3} rather than \d{3}, so IDs longer than three digits are recognized for both deduplication and creation. Word boundaries prevent false matches like ST001 or partial matches inside longer IDs.