speckit-taskstoissues

Convert spec-kit tasks into deduplicated, dependency-ordered GitHub issues.

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

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 to prevent duplicates. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (e.g., - [ ] T001 Create project structure) 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 pattern \bT\d{3}\b, skipping tasks that already have issues. - Safety Guards: Verifies the git remote is a GitHub URL before creating anything and never creates issues in repositories that do not match the remote. - Use Case: After running spec-kit task generation for a feature, invoke this Skill to publish every task as a trackable GitHub issue without re-checking which ones already exist. ## Quick Start Ask the agent to convert the current feature's tasks into GitHub issues, optionally providing a filter or label as an argument.

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

Invoke the taskstoissues skill in a spec-kit project with a .specify directory. It runs the prerequisites script to locate tasks.md, verifies the git remote is a GitHub URL, then creates one issue per task using the GitHub MCP server.

How does the skill avoid creating duplicate GitHub issues?▼

It fetches existing open and closed issues with perPage 100 and cursor-based pagination, matching titles against the pattern \bT\d{3}\b. Tasks whose IDs already appear in an issue title are skipped and reported.

What happens if the git remote is not a GitHub URL?▼

The skill stops before creating anything. It explicitly refuses to proceed unless the remote origin URL is a GitHub repository, and never creates issues in repositories that do not match the remote.

Can I rerun the skill after tasks.md is regenerated?▼

Yes. Deduplication is based on task IDs found in existing issue titles, so rerunning only creates issues for new tasks. Pagination stops early once all current task IDs are accounted for.

What are the limitations of the task ID matching?▼

Task IDs must be a T followed by at least three digits, such as T001 or T1000. Tokens like ST001 do not match, and titles must contain the ID as a standalone token for deduplication to work.