speckit-taskstoissues

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

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-taskstoissues-acarmonag
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/acarmonag/fullstack-devops-agent-aws-terraform/tree/main/codebase/rdicidr-0.1.0/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-taskstoissues-acarmonag

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 when re-run. This Skill automates the conversion while checking existing issues so each task maps to exactly one issue. ## Core Features & Use Cases - Automated Issue Creation: Parses tasks.md entries (stripping checkboxes and [P]/[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 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 supports pre/post extension hooks from .specify/extensions.yml. - Use Case: After running spec-kit planning for a feature, invoke this Skill to publish all 40 tasks as GitHub issues for team assignment, 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 the speckit-taskstoissues skill in a spec-kit project. It reads tasks.md, strips checkbox and priority markers, and creates one GitHub issue per task titled with the task ID and description, such as "T001: Create project structure".

How does the skill avoid creating duplicate GitHub issues?▼

It fetches existing open and closed 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, reporting each skip.

Does this work with non-GitHub git remotes?▼

No. The skill reads the 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, so GitLab or Bitbucket remotes are unsupported.

What prerequisites are needed before running tasks-to-issues conversion?▼

You need a spec-kit project structure with a .specify directory, a generated tasks.md file, and a GitHub remote. The skill runs check-prerequisites.sh with --require-tasks to resolve the feature directory and available design documents.

Why are some tasks skipped when re-running the conversion?▼

Tasks are skipped when an existing issue title already contains their task ID. This deduplication is intentional so the skill can be safely re-run after tasks.md is regenerated without creating duplicate issues.