speckit-taskstoissues

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

1|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/pieberrykinnie/hapa --skill speckit-taskstoissues-pieberrykinnie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/pieberrykinnie/hapa/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/pieberrykinnie/hapa --skill speckit-taskstoissues-pieberrykinnie

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, skipping 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 trackable GitHub issue without re-checking which ones already exist. ## 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 spec-kit tasks into GitHub issues?

Run this Skill in a spec-kit project after generating tasks.md. It parses each checkbox task line, 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 using the GitHub MCP list_issues tool with cursor-based pagination, then matches titles against the task ID pattern `\bT\d{3}\b`. Tasks already covered by an issue are skipped and reported.

Does this work with non-GitHub remotes like GitLab?

No. The Skill reads the Git remote URL and only proceeds if it is a GitHub URL. It explicitly refuses to create issues in repositories that do not match the remote, so GitLab or Bitbucket remotes are unsupported.

What prerequisites are required before running tasks-to-issues conversion?

The project must follow the spec-kit structure with a .specify directory containing tasks.md and the check-prerequisites.sh script. A configured GitHub MCP server and a GitHub remote origin are also required.

What are extension hooks in spec-kit taskstoissues?

Hooks are commands defined in .specify/extensions.yml under hooks.before_taskstoissues or hooks.after_taskstoissues. Optional hooks are suggested to the user, while mandatory hooks are executed automatically before the workflow continues.