speckit-taskstoissues

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

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

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 the conversion while verifying the Git remote and skipping tasks that already have issues. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (e.g., - [ ] T001 Create project structure) and creates GitHub issues titled T001: Create project structure via the GitHub MCP server. - Deduplication: Fetches existing issues with cursor-based pagination and matches task IDs using the \bT\d{3}\b pattern to skip 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 running spec-kit planning for a new feature, invoke this Skill to publish all 30 tasks as GitHub issues in one pass, then re-run it later after regenerating tasks.md without creating duplicates. ## 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 checkbox task line, extracts the task ID and description, and creates a GitHub issue titled like `T001: Create project structure` through the GitHub MCP server.

How does the Skill avoid creating duplicate GitHub issues?

It lists existing issues with the GitHub MCP list_issues tool using cursor-based pagination, matches titles against the `\bT\d{3}\b` pattern, and skips any task ID that already has an issue. Pagination stops once all task IDs are accounted for.

What project structure is required for tasks-to-issues conversion?

The project must follow the spec-kit layout with a .specify directory, including the check-prerequisites PowerShell script and a tasks.md file for the feature. The Git remote origin must also be a GitHub URL, otherwise the Skill stops.

Can I use this Skill with a non-GitHub remote repository?

No. The Skill explicitly checks `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 are extension hooks in the tasks-to-issues workflow?

Hooks are commands defined 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 conversion continues.