speckit-taskstoissues

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

Updated Sep 12, 2026
One-click install
npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-taskstoissues-andyrace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/AndyRace/heart-rate-graph/tree/main/.github/skills/speckit-taskstoissues
Command: npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-taskstoissues-andyrace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually creating GitHub issues from a spec-kit tasks.md file is repetitive and error-prone, and re-running the process can create 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 and creates one GitHub issue per task with a canonical title format like "T001: Create project structure". - Deduplication: Fetches existing open and closed issues via the GitHub MCP server and skips tasks that already have matching issues. - Extension Hooks: Supports optional and mandatory pre/post hooks defined in .specify/extensions.yml for customizable workflow integration. - Use Case: After generating a tasks.md file with /speckit-tasks, run this Skill to publish every task as a trackable GitHub issue in the repository matching your git remote. ## 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 speckit-taskstoissues skill in a spec-kit project. It reads tasks.md via the check-prerequisites script, verifies the git remote is a GitHub URL, and creates one issue per task using the GitHub MCP server.

How does the skill avoid creating duplicate GitHub issues?

It fetches existing open and closed issues with the list_issues tool, matches titles against the task ID pattern \bT\d{3}\b, and skips any task ID that already has an issue. Pagination stops once all task IDs are accounted for.

What are the requirements for running tasks-to-issues conversion?

You need a spec-kit project with a .specify directory, a tasks.md file for the current feature, and a git remote pointing to a GitHub repository. The skill refuses to create issues in repositories that do not match the remote URL.

Can I run custom hooks before or after issue creation?

Yes, define hooks under hooks.before_taskstoissues or hooks.after_taskstoissues in .specify/extensions.yml. Hooks can be optional or mandatory; mandatory hooks are executed automatically before the workflow continues.

Why are some tasks skipped when creating GitHub issues?

Tasks are skipped when an existing issue title already contains their task ID, such as T001. The skill reports each skipped task, for example "T001 already has an issue, skipping", to keep you informed.