speckit-taskstoissues

Convert design tasks into dependency-ordered GitHub issues in the target repository.

Updated Apr 2, 2026

Search Tags:#automation #workflow #integration #task-management #project-management #github-issues

Ready to run

npx skills add https://github.com/programmingworld1/AISpecKit --skill speckit-taskstoissues-programmingworld1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/programmingworld1/AISpecKit/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/programmingworld1/AISpecKit --skill speckit-taskstoissues-programmingworld1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates turning scattered design tasks into actionable, dependency-ordered GitHub issues, reducing manual coordination and ensuring traceability from design artifacts to implementation work.

Core Features & Use Cases

Automated transformation of design tasks into GitHub issues in the correct repository
Enforces repository matching to prevent cross-repo issue creation
Supports dependency-ordered prioritization to reflect task sequences and design constraints
Use Case: Given a feature with design docs in the .specify workspace, convert each task into labeled issues in the target repo and maintain their dependencies for sprint planning.

Quick Start

Provide the list of tasks and the target repository, and run this skill to generate corresponding GitHub issues.

Frequently Asked Questions about speckit-taskstoissues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn design tasks into GitHub issues automatically?▼

To turn design tasks into GitHub issues automatically, provide the task list and target repository to generate ordered issue entries with dependency tracking.

What is dependency-ordered issue creation for project management?▼

Dependency-ordered issue creation is the process of generating GitHub issues in sequential task order to reflect design constraints and trace implementation steps from design artifacts.

Do I need a Git remote URL to automate GitHub issue creation?▼

Yes, you need a Git remote URL to automate GitHub issue creation, as the process requires repository access and enforces repository matching to prevent cross-repo issues.

What is the best way to prevent cross-repo issues when converting tasks?▼

The best way to prevent cross-repo issues when converting tasks is to enforce repository matching against the known Git remote URL before generating any GitHub issue entries.

Why does task to issue automation enforce repository matching?▼

Task to issue automation enforces repository matching to prevent cross-repo issue creation and ensure design tasks are traced correctly to their target implementation repository.