speckit-taskstoissues

Convert spec-kit tasks into deduplicated GitHub issues via the GitHub MCP server.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually turning a tasks.md breakdown 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: Create project structure. - Deduplication: Fetches existing open and closed issues via the GitHub MCP server with cursor-based pagination and skips tasks that already have matching 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 task breakdown with spec-kit, run this Skill to publish every task as a trackable GitHub issue in the correct repository without manual copy-pasting. ## 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 tasks.md into GitHub issues automatically?▼

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 with the task ID and description, such as `T001: Create project structure`.

How does the skill avoid creating duplicate GitHub issues?▼

It fetches existing open and closed issues via the GitHub MCP list_issues tool with perPage 100 and cursor pagination, matching titles against the task ID pattern \bT\d{3}\b. Tasks already covered are skipped and reported.

Can I use this with a non-GitHub repository remote?▼

No. The Skill reads the git remote origin URL and only proceeds if it is a GitHub URL. It explicitly refuses to create issues in repositories that do not match the remote.

What project structure is required for tasks-to-issues conversion?▼

The project must follow the spec-kit layout with a .specify directory, including the check-prerequisites PowerShell script and a tasks.md file. A constitution.md under .specify/memory is loaded if present.

What are extension hooks in spec-kit taskstoissues?▼

Hooks are commands defined under hooks.before_taskstoissues or hooks.after_taskstoissues in .specify/extensions.yml. Mandatory hooks execute automatically before continuing, while optional hooks are only suggested to the user.