speckit-taskstoissues

Convert spec-kit tasks into deduplicated, dependency-ordered GitHub issues.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/alkampfergit/cisharpai --skill speckit-taskstoissues-alkampfergit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/alkampfergit/cisharpai/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/alkampfergit/cisharpai --skill speckit-taskstoissues-alkampfergit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually turning a tasks.md breakdown into GitHub issues is repetitive and error-prone, often producing duplicates or issues in the wrong repository. This Skill automates the conversion while checking for existing issues and validating the Git remote. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (stripping checkboxes and [P]/[US#] markers) and creates GitHub issues titled T001: <description> via the GitHub MCP server. - Deduplication: Fetches existing issues with cursor-based pagination and matches task IDs using the pattern \bT\d{3}\b so re-runs never create duplicates. - 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 running spec-kit planning for a new feature, invoke this Skill to publish every task as a trackable GitHub issue for the team backlog. ## Quick Start Ask the assistant 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 taskstoissues skill in a spec-kit project. It runs check-prerequisites.sh to locate tasks.md, parses each checkbox line into a task ID and description, and creates one GitHub issue per task titled like `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 pagination, then matches titles against the pattern \bT\d{3}\b. Any task ID already covered by an issue is skipped and reported.

Can I create issues in a non-GitHub repository?▼

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 taskstoissues?▼

The project must follow the spec-kit layout with a .specify directory containing scripts/bash/check-prerequisites.sh and a tasks.md file for the feature. An optional .specify/extensions.yml can register pre and post hooks.

Why are some tasks skipped when running the skill again?▼

Tasks are skipped when an existing issue title already contains their task ID, which happens on re-runs after issues were created. The skill reports each skipped ID, for example `T001 already has an issue, skipping`.