speckit-taskstoissues

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

9|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/timcsy/semorphe --skill speckit-taskstoissues-timcsy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/timcsy/semorphe/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/timcsy/semorphe --skill speckit-taskstoissues-timcsy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually turning 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: Create project structure 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 supports pre/post extension hooks from .specify/extensions.yml. - Use Case: After generating an implementation plan with spec-kit, run this Skill to publish every task as a trackable GitHub issue for your team, then re-run it safely after tasks.md is regenerated. ## 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?▼

Run this Skill in a spec-kit project with a .specify directory. It reads tasks.md, strips checkbox and priority markers, and creates one GitHub issue per task with a title like `T001: Create project structure` using the GitHub MCP server.

How does the skill avoid creating duplicate GitHub issues?▼

Before creating anything, it lists existing issues (open and closed) with paginated requests 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 is safe.

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

No. The Skill checks 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 prerequisites does the taskstoissues workflow require?▼

You need a spec-kit project structure with a .specify directory, a generated tasks.md file, a GitHub remote configured, and access to the GitHub MCP server. It runs check-prerequisites.sh to resolve feature paths first.

What are extension hooks in spec-kit commands?▼

Hooks are optional or mandatory commands defined in .specify/extensions.yml under before_taskstoissues or after_taskstoissues keys. Enabled hooks run before or after the conversion; hooks with conditions are skipped and left to the HookExecutor.