speckit-taskstoissues

Name: speckit-taskstoissues
Availability: InStock
Author: Numu

Convert Spec-Kit tasks into dependency-ordered GitHub issues.

2|Updated Jan 6, 2026

Search Tags:#task management #github #project planning #backlog #issues #spec-kit #dependency ordering

Ready to run

npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-taskstoissues-numu-io

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-taskstoissues-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns existing feature tasks into a clear, dependency-ordered GitHub issue backlog so teams can move from planning artifacts to executable work without manual issue drafting.

Core Features & Use Cases

Task-to-Issue Conversion: Reads task lists and transforms each task into a separate issue that reflects implementation intent.
Dependency Ordering: Preserves task relationships so issues are created in a sequence that supports incremental delivery.
Repository Safety Checks: Verifies the project structure and Git remote before creating issues, reducing the risk of posting to the wrong repository.
Use Case: A team has a Spec-Kit feature plan with multiple tasks and wants a clean issue backlog ready for sprint planning and assignment.

Quick Start

Ask this skill to convert the current Spec-Kit tasks into GitHub issues for the matching 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 for project planning?▼

To convert Spec-Kit tasks into GitHub issues, this skill reads existing task artifacts from the .specify directory and creates dependency-ordered issues in the matching GitHub repository. It verifies the Git remote before posting to ensure repository safety.

What is dependency ordering when creating a GitHub issue backlog?▼

Dependency ordering preserves task relationships so GitHub issues are created in a sequence that supports incremental delivery. This allows teams to execute the backlog step-by-step, ensuring foundational tasks are completed before dependent work begins.

Does this task-to-issue conversion work with repositories outside of Spec-Kit?▼

No, this conversion applies specifically to Spec-Kit repositories that already contain task artifacts in a .specify structure. It requires task discovery from project scripts and will not function without this existing planning format.

How do I create an actionable GitHub backlog from feature planning tasks?▼

You can create an actionable GitHub backlog by asking this skill to transform your existing feature tasks into separate issues. It reads the task lists and reflects the implementation intent directly into the GitHub repository's issue tracker.

Why does GitHub issue creation require verifying the Git remote?▼

Verifying the Git remote is a repository safety check that confirms the project is connected to the matching GitHub repository. This reduces the risk of posting the generated task issues to the wrong repository.

Can I use GitHub issues for sprint planning if my tasks have complex dependencies?▼

Yes, the skill reads task lists and transforms each task into a separate issue while preserving dependency ordering. This provides a clean backlog ready for sprint planning and assignment, even with complex task relationships.