speckit-taskstoissues

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

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/dperussina/function2agent --skill speckit-taskstoissues-dperussina
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/dperussina/function2agent/tree/main/.cursor/skills/speckit-taskstoissues
Command: npx skills add https://github.com/dperussina/function2agent --skill speckit-taskstoissues-dperussina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually transcribing a 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 to prevent duplicates. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (e.g., - [ ] T001 Create project structure) and creates GitHub issues titled T001: <description> via the GitHub MCP server. - Deduplication: Fetches existing open and closed 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 supports pre/post extension hooks from .specify/extensions.yml. - Use Case: After generating a tasks.md breakdown for a feature with spec-kit, run this Skill to publish every task as a tracked GitHub issue in one pass, then re-run it safely after tasks.md is regenerated. ## Quick Start Convert the tasks in my current spec-kit feature's tasks.md 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 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 a GitHub issue titled `T001: <description>` for every task using the GitHub MCP server.

How does the skill avoid creating duplicate GitHub issues?▼

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

Can I use this with a GitLab or Bitbucket repository?▼

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 project structure is required for this skill to work?▼

It requires a spec-kit project with a .specify directory, including the check-prerequisites.sh script that returns the feature's tasks path. A constitution.md file is loaded if present, and extension hooks are read from .specify/extensions.yml.

Why are some tasks skipped when the skill runs?▼

Tasks are skipped when an existing issue title already contains their task ID, such as `T001: ...` or `[T001] ...`. The Skill reports each skip, for example `T001 already has an issue, skipping`, so re-runs stay idempotent.