speckit-taskstoissues

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

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dantasgut/clayflow --skill speckit-taskstoissues-dantasgut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/dantasgut/clayflow/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/dantasgut/clayflow --skill speckit-taskstoissues-dantasgut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert scattered product design tasks into a structured, actionable backlog by generating GitHub issues organized by dependencies and design artifacts.

Core Features & Use Cases

  • Maps tasks to issue templates with clear titles, labels, and milestones based on design artifacts.
  • Orders issues according to a dependency graph to support sprint planning and milestone tracking.
  • Use Case: A feature team transitions a design backlog into a ready-to-work issue set for developers.

Quick Start

Create a set of GitHub issues from current tasks using available design artifacts.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert product design tasks into GitHub issues?

To convert product design tasks into GitHub issues, you parse task lists and design artifacts to generate structured issue metadata. This process maps tasks to issue templates with clear titles, labels, and milestones based on dependencies.

How do I map dependencies when generating GitHub issues from a task list?

Mapping dependencies when generating GitHub issues involves ordering issues according to a dependency graph. This supports sprint planning and milestone tracking by ensuring feature delivery tasks are properly sequenced across repositories.

Can I use design artifacts to create ordered GitHub issues for sprint planning?

Yes, you can create ordered GitHub issues from design artifacts for sprint planning. The process parses design artifacts and maps them to issue templates, organizing the generated issues by dependencies to support milestone tracking.

Does this approach support dependency-aware issue creation across multiple repositories?

Yes, dependency-aware issue creation supports multiple repositories. It is designed for product teams managing complex features, allowing them to generate ordered GitHub issues that map dependencies across different repositories.

What is the best way to streamline feature delivery from a design backlog?

Streamlining feature delivery from a design backlog is best achieved by converting scattered tasks into a structured, actionable backlog. This generates GitHub issues organized by dependencies and design artifacts, creating a ready-to-work set for developers.