speckit-taskstoissues

Name: speckit-taskstoissues
Availability: InStock
Author: yarelicamacho

Convert feature tasks into dependency-ordered GitHub issues.

Updated May 22, 2026

Search Tags:#github #project planning #backlog #issues #tasks #spec-kit

Ready to run

npx skills add https://github.com/yareliCamacho/AppCalendario --skill speckit-taskstoissues-yarelicamacho

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/yareliCamacho/AppCalendario/tree/main/.cursor/skills/speckit-taskstoissues
Command: npx skills add https://github.com/yareliCamacho/AppCalendario --skill speckit-taskstoissues-yarelicamacho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an existing feature task list into a clear set of actionable GitHub issues, so teams can move from planning artifacts to execution without manually rewriting work items.

Core Features & Use Cases

Dependency-Aware Breakdown: Converts tasks into issues in a practical execution order that reflects task dependencies.
Feature Delivery Planning: Useful when a spec, plan, or task list already exists and needs to become a trackable backlog.
GitHub Issue Preparation: Helps product and engineering teams create repository issues that are ready for assignment, sequencing, and implementation.

Quick Start

Use the speckit-taskstoissues skill to convert the current feature task list into dependency-ordered GitHub issues for the 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 a feature task list into GitHub issues with dependencies?▼

To convert feature tasks into GitHub issues with dependencies, the Skill parses an existing spec-kit task list and generates repository issues ordered by their execution dependencies. It requires a validated spec-kit project structure and matching repository remote before creating the issues.

Can I use spec-kit project planning to create an execution-ready GitHub backlog?▼

Yes, spec-kit project planning creates an execution-ready GitHub backlog by transforming existing feature task lists into trackable repository issues. This allows product and engineering teams to move from planning artifacts directly to implementation without manually rewriting work items.

Do I need a specific repository structure to generate GitHub issues from tasks?▼

Yes, you need a validated spec-kit project structure and a matching GitHub repository remote to generate issues from tasks. The Skill performs spec-kit project structure validation and repository remote matching before creating any dependency-ordered issues.

What is the best way to sequence GitHub issues based on task dependencies?▼

The best way to sequence GitHub issues based on task dependencies is to apply dependency-aware breakdown during issue creation. The Skill converts existing feature tasks into GitHub issues in a practical execution order that reflects their underlying dependencies.

Why are my spec-kit tasks not converting into GitHub issues?▼

Spec-kit tasks may not convert into GitHub issues if the project structure validation fails or the repository remote does not match. The Skill requires both a valid spec-kit project structure and a confirmed repository remote before it can create issues.

When should I use automated issue creation for spec-driven project planning?▼

You should use automated issue creation for spec-driven project planning when a spec, plan, or task list already exists and needs to become a trackable backlog. It is specifically designed for backlog creation and execution tracking within GitHub repositories.