speckit-taskstoissues

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

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-taskstoissues-omkar-code-mur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/Omkar-code-mur/Job-Radar/tree/main/Spec-it_job-Radar/.github/skills/speckit-taskstoissues
Command: npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-taskstoissues-omkar-code-mur

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 existing issues and validating the Git remote before creating anything. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (stripping checkbox, [P], and [US#] markers) and creates GitHub issues titled T001: <description> via the GitHub MCP server. - Deduplication: Fetches existing open and closed 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 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 spec-kit planning for a feature, invoke this Skill to publish every task in tasks.md as a tracked GitHub issue without re-checking which ones already exist. ## Quick Start Convert the tasks in my current spec-kit feature's tasks.md into GitHub issues, skipping any that already exist.

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 with a .specify directory. It executes check-prerequisites.ps1 to locate tasks.md, parses each task line, and creates GitHub issues titled like `T001: <description>` through the GitHub MCP server.

How does the skill avoid creating duplicate GitHub issues?

It lists existing open and closed issues with perPage 100 and cursor pagination, matching titles against the pattern \bT\d{3}\b. Any task ID already present in an issue title is skipped and reported instead of recreated.

Does it work with task IDs longer than three digits?

Yes. The matching pattern uses \d{3} so IDs like T1000 are recognized. The word boundary handling also prevents false matches such as ST001 or partial matches inside longer IDs.

What happens if the Git remote is not a GitHub URL?

The Skill stops before creating anything. It reads the remote via git config --get remote.origin.url and only proceeds when the remote is a GitHub URL, never creating issues in repositories that do not match the remote.

Can I run custom hooks before or after issue creation?

Yes. If .specify/extensions.yml defines hooks under before_taskstoissues or after_taskstoissues, the Skill executes mandatory hooks and suggests optional ones. Hooks with enabled set to false or with non-empty conditions are skipped.