speckit-taskstoissues

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/zhangliuliuzhang/memcached-rvv-v2 --skill speckit-taskstoissues-zhangliuliuzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/zhangliuliuzhang/memcached-rvv-v2/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/zhangliuliuzhang/memcached-rvv-v2 --skill speckit-taskstoissues-zhangliuliuzhang

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 (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 and matches task IDs using the \bT\d{3}\b pattern to skip 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 task breakdown with spec-kit, run this Skill to publish every task as a tracked GitHub issue without re-checking which ones already exist. ## 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 the check-prerequisites script to locate tasks.md, parses each task line, and creates one GitHub issue per task using the GitHub MCP server with titles like `T001: Create project structure`.

How does the skill avoid creating duplicate GitHub issues?

It fetches existing issues with the GitHub MCP list_issues tool using cursor-based pagination and matches titles against the `\bT\d{3}\b` pattern. Tasks whose IDs already appear in an issue title are skipped and reported.

Does taskstoissues work with non-GitHub remotes?

No. The skill reads the Git remote via `git config --get remote.origin.url` and only proceeds if it is a GitHub URL. It never creates 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, including the PowerShell check-prerequisites script and a generated tasks.md file. A `.specify/memory/constitution.md` is loaded if present.

What are extension hooks in taskstoissues?

Hooks are commands defined in `.specify/extensions.yml` under `hooks.before_taskstoissues` or `hooks.after_taskstoissues`. Enabled hooks run before or after conversion; optional hooks are suggested, while mandatory hooks are executed automatically.