speckit-taskstoissues

Convert design artifacts and tasks into dependency-ordered GitHub issues.

Updated Mar 29, 2026

Search Tags:#automation #github #speckit #issue-tracking #design-artifacts #task-to-issues #dependency-ordering

Ready to run

npx skills add https://github.com/iltan987/jetadisyon --skill speckit-taskstoissues-iltan987

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Core Features & Use Cases

Convert tasks into GitHub issues ordered by dependencies according to design artifacts.
Maintain traceability from specs to issues to support feature delivery.
Use case: given a feature with design artifacts, generate a ready-to-work backlog by creating issues with clear dependencies.

Quick Start

Execute speckit-taskstoissues on your repository to generate and organize issues from design artifacts into a dependency-aware task backlog.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema

How do I convert design artifacts into dependency-ordered GitHub issues?▼

This tool converts feature design artifacts into dependency-ordered GitHub issues by reading a .specify directory and generating an organized backlog. It aligns issue creation with the repository's remote URL to maintain traceability.

What is the best way to automate task-to-issues conversion for feature development projects?▼

The best way to automate task-to-issues conversion is using a tool that parses design artifacts and maps dependencies directly into GitHub issues. This creates a ready-to-work backlog that respects the required execution order for feature delivery.

Do I need a .specify directory to generate dependency-aware task backlogs from specs?▼

Yes, a .specify directory is required to generate dependency-aware task backlogs. The tool relies on this directory structure to locate design artifacts and correctly map task dependencies when creating GitHub issues.

Can I maintain traceability from specs to GitHub issues during feature delivery?▼

Yes, traceability from specs to GitHub issues is maintained during feature delivery. By converting design artifacts into ordered issues, the process ensures a clear link between original specifications and the generated backlog items.

How does dependency ordering work when creating GitHub issues from design artifacts?▼

Dependency ordering analyzes relationships defined in design artifacts and sequences GitHub issues so prerequisite tasks are completed first. This produces an ordered issue list with clear dependencies aligned to your repository's remote URL.