speckit-taskstoissues

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

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

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 checking for existing issues and verifying the Git remote. ## 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, 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 generating an implementation plan with spec-kit, run this Skill to publish every task as a trackable GitHub issue for your team without re-checking for duplicates. ## Quick Start Convert the tasks in my current spec-kit feature 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 generating tasks.md. It parses each checkbox task line, strips markers like [P] and [US#], and creates a GitHub issue titled with the task ID and description via the GitHub MCP server.

How does the skill avoid creating duplicate GitHub issues?▼

It fetches existing issues using the GitHub MCP list_issues tool with pagination and matches titles against the task ID pattern \bT\d{3}\b. Any task ID already present in an issue title is skipped and reported.

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

The project must follow the spec-kit structure with a .specify directory containing scripts and a tasks.md file for the feature. The Skill runs check-prerequisites.sh to resolve feature paths before proceeding.

Can I create issues in a non-GitHub repository?▼

No. The Skill reads 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 are extension hooks in spec-kit taskstoissues?▼

Hooks are commands defined in .specify/extensions.yml under hooks.before_taskstoissues or hooks.after_taskstoissues. Mandatory hooks execute automatically before or after conversion, while optional hooks are suggested for manual execution.