speckit-taskstoissues

Convert design tasks into dependency-ordered GitHub issues.

Updated Apr 13, 2026

Search Tags:#automation #workflow #github #issues #tasks #convert #project-management

Ready to run

npx skills add https://github.com/GarethJB/workflow-plugin --skill speckit-taskstoissues-garethjb

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert existing tasks into actionable, dependency-ordered GitHub issues that map to a feature based on available design artifacts, enabling structured execution and traceability.

Core Features & Use Cases

Task-to-issue mapping: Transforms a task list into linked GitHub issues with proper dependencies and ordering.
Design-driven workflow: Leverages design artifacts in the project (.specify/) to inform issue scopes and relationships.
Use Case: When planning a feature, convert planning tasks into an issue board with a clear dependency graph for implementation teams.

Quick Start

Convert current design tasks into a dependency-ordered set of GitHub issues for the active feature.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema

How do I convert project tasks into GitHub issues with dependencies?▼

This skill converts existing tasks into a dependency-ordered set of GitHub issues by mapping task relationships from design artifacts. It automatically generates linked issues with proper ordering to create a structured implementation graph for teams.

Can I generate GitHub issues from design artifacts in my repository?▼

Yes, you can generate GitHub issues from design artifacts stored in the .specify/ directory. The skill leverages these specification kit artifacts to inform issue scopes and dependency relationships for the active feature.

Does this task-to-issue conversion work with non-GitHub Git remotes?▼

No, the skill validates the Git remote to ensure it is a GitHub URL before creating any issues. It restricts issue creation to the matching repository and prevents cross-repo operations on non-GitHub remotes.

What is the best way to create an ordered issue board for a feature?▼

The best way to create an ordered issue board is to convert planning tasks into linked GitHub issues with a defined dependency graph. This approach provides structured execution and traceability directly from your project's design artifacts.

Why does my task-to-issue generation fail on a different repository?▼

Task-to-issue generation fails across different repositories because the skill validates the Git remote and creates issues only in the matching repository. This restriction prevents unintended cross-repo operations and ensures issues map correctly.