speckit-taskstoissues

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

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Powerworks/Underwriting --skill speckit-taskstoissues-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/Powerworks/Underwriting/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/Powerworks/Underwriting --skill speckit-taskstoissues-powerworks

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 when re-run. 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) and creates GitHub issues titled T001: <description> via the GitHub MCP server. - Deduplication: Fetches existing issues with cursor-based pagination and skips tasks that already have matching issues. - Extension Hooks: Supports optional and mandatory pre/post hooks defined in .specify/extensions.yml. - Use Case: After generating a tasks.md breakdown for a new feature, run this Skill to populate the GitHub repository with one issue per task, safely re-runnable 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 task line, strips checkbox and marker prefixes, and creates one GitHub issue per task using the GitHub MCP server with titles like `T001: Create project structure`.

How does the skill avoid creating duplicate GitHub issues?▼

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

Can I use this with a non-GitHub git remote?▼

No. The Skill checks the git remote origin URL and only proceeds if it is a GitHub URL. It explicitly refuses to create issues in repositories that do not match the remote.

What prerequisites does the taskstoissues skill require?▼

It requires a spec-kit project structure with a .specify directory, an existing tasks.md file, a GitHub remote origin, and access to the GitHub MCP server. It runs check-prerequisites.sh to resolve feature paths before converting tasks.

What are extension hooks in spec-kit taskstoissues?▼

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 or after the conversion.