speckit-taskstoissues

Convert tasks.md entries into deduplicated GitHub issues via the GitHub MCP server.

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-taskstoissues-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.grok/skills/speckit-taskstoissues
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-taskstoissues-tjsasakifln

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually turning a spec-kit 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 with built-in deduplication and remote-URL safety checks. ## Core Features & Use Cases - Automated issue creation: Parses each task line in tasks.md, strips checkbox and marker prefixes, and creates GitHub issues titled T001: <description> through 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 refuses to create issues in repositories that do not match the remote. - Extension hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml. - Use Case: After running speckit task generation for a new feature, invoke this Skill to publish all 25 tasks as GitHub issues in one pass, skipping the 5 that were already created in 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 this Skill in a spec-kit project after generating tasks.md. It parses each task line, strips checkbox and [P]/[US#] markers, and creates issues titled `T001: <description>` through the GitHub MCP server.

How does the Skill avoid creating duplicate GitHub issues?▼

It lists existing issues with 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, and pagination stops once all task IDs are matched.

Does it work with GitLab or non-GitHub remotes?▼

No. The Skill reads `git config --get remote.origin.url` and only proceeds if the remote is a GitHub URL. It never creates issues in repositories that do not match the remote.

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

You need a spec-kit project with a .specify directory, a generated tasks.md file, and a GitHub remote. The Skill runs check-prerequisites.sh with --require-tasks to resolve feature paths before creating issues.

What are extension hooks in spec-kit commands?▼

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