speckit-taskstoissues

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually translating 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 that conversion while verifying the Git remote and skipping tasks that already have issues. ## 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 issues with cursor-based pagination and matches task IDs using the \bT\d{3}\b pattern, skipping any task that already has an issue. - 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 30 tasks in tasks.md into tracked GitHub issues without re-creating ones from a previous run. ## 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 after tasks.md exists. It parses each task line, strips checkbox and priority 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 perPage 100 and cursor pagination, matching titles against the `\bT\d{3}\b` pattern. Any task ID already covered by an issue is skipped and reported, and pagination stops once all IDs are matched.

Does this 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 explicitly refuses to create issues in repositories that do not match the remote.

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

You need a spec-kit project structure with a .specify directory, a generated tasks.md for the feature, PowerShell for check-prerequisites.ps1, and access to the GitHub MCP server for issue operations.

What are extension hooks in the taskstoissues workflow?

Hooks are optional commands defined in .specify/extensions.yml under before_taskstoissues or after_taskstoissues. Enabled hooks without conditions are executed or suggested around the conversion, with dot names converted to hyphenated command invocations.