speckit-taskstoissues

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually translating a tasks.md file 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 running spec-kit planning for a new feature, invoke this Skill to turn all 25 generated tasks into tracked GitHub issues without re-creating ones from a previous run. ## 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 the taskstoissues command in a spec-kit project after tasks.md has been generated. The Skill parses each checkbox line, strips markers like [P] or [US#], and creates issues titled `T001: <description>` through the GitHub MCP server.

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

You need a spec-kit project structure with a .specify directory, a generated tasks.md for the current feature, a GitHub remote origin, and access to the GitHub MCP server. The check-prerequisites.ps1 script validates the feature directory and available docs.

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 conversion continues.