speckit-taskstoissues

Convert spec-kit tasks into deduplicated GitHub issues via the GitHub MCP server.

32|9|Updated Feb 2, 2024
One-click install
npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-taskstoissues-esri
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/Esri/arcgis-gitops/tree/main/.github/skills/speckit-taskstoissues
Command: npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-taskstoissues-esri

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 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 with canonical titles like T001: Create project structure. - Deduplication: Fetches existing open and closed issues via the GitHub MCP server, matches task IDs with the pattern \bT\d{3}\b, 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 a task breakdown with spec-kit, run this Skill to publish every task as a trackable GitHub issue in the matching repository without duplicates. ## Quick Start Ask the agent to convert the tasks in tasks.md into GitHub issues for the current 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, strips checkbox and marker prefixes, 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?▼

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

The project must follow the spec-kit structure with a .specify directory containing tasks.md, and the git remote origin must be a GitHub URL. The skill refuses to create issues in repositories that do not match the remote.

Does the skill support task IDs with more than three digits?▼

Yes. The matching pattern `\bT\d{3}\b` accepts four-digit and longer IDs such as T1000, so repositories with more than 999 tasks are still deduplicated and created correctly.

What are extension hooks in the tasks-to-issues workflow?▼

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