speckit-taskstoissues

Convert design artifacts into dependency-ordered GitHub issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/luansilvadb/divi-app --skill speckit-taskstoissues-luansilvadb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/luansilvadb/divi-app/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/luansilvadb/divi-app --skill speckit-taskstoissues-luansilvadb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts tasks into actionable, dependency-ordered GitHub issues.

Core Features & Use Cases

  • Extracts tasks from design artifacts and maps them to GitHub issues with clear titles.
  • Orders issues by dependency to preserve feature rollout order.
  • Supports template-based descriptions and automatic linking to related artifacts.

Quick Start

Provide your design artifacts in the project, then run the speckit taskstoissues workflow to generate GitHub issues in dependency order.

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 GitHub issues for feature development?

This Skill generates dependency-ordered GitHub issues from design artifacts by extracting tasks from a .specify/ directory, mapping them to issue titles and template-based descriptions to preserve feature rollout order across repositories.

How does automated issue ordering work when generating GitHub issues from design specifications?

Dependency-ordered issue generation works by extracting tasks from design artifacts and sequencing them based on their dependencies, preserving feature rollout order across GitHub repositories.

Do I need a specific directory structure to generate GitHub issues from design tasks?

Yes, you need a .specify/ directory containing your design artifacts and project specifications, plus access to a GitHub repository and templates for issue generation to run the workflow.

Can I use template-based descriptions when creating GitHub issues from design artifacts?

Yes, this Skill supports template-based descriptions for GitHub issue generation, automatically populating templates with artifact data and linking related design artifacts to each issue.

What's the best way to manage project tasks from design specifications in GitHub?

The best way to manage design-driven software tasks in GitHub is automating the conversion of design artifacts into dependency-ordered issues, ensuring structured feature development and clear artifact linking.

Why are my GitHub issues not generating in the correct dependency order from design artifacts?

GitHub issues may generate out of order if the design artifacts in the .specify/ directory lack explicit dependency mappings, preventing the Skill from properly sequencing feature rollout.