speckit-taskstoissues

Convert tasks into dependency-ordered GitHub issues with design artifact traceability.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/nalthoff/spec-kit-prep-specify --skill speckit-taskstoissues-nalthoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/nalthoff/spec-kit-prep-specify/tree/main/.cursor/skills/speckit-taskstoissues
Command: npx skills add https://github.com/nalthoff/spec-kit-prep-specify --skill speckit-taskstoissues-nalthoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Automatically derive GitHub issues from a backlog of tasks while preserving dependencies.
  • Align issues with available design artifacts to ensure traceability from design to implementation.
  • Use case: When a feature spans multiple tasks and design inputs, generate a coherent chain of issues with clear prerequisites.

Quick Start

Run the speckit-taskstoissues workflow on your feature backlog to generate a dependency-ordered set of 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 convert project tasks into dependency-ordered GitHub issues?

Yes, GitHub issues generated from tasks are automatically linked to available design artifacts. This ensures full traceability from design to implementation by validating issue metadata and connecting related inputs directly within the generated issues.

What happens to incomplete design inputs when generating GitHub issues from a task backlog?

When generating GitHub issues from a task backlog with incomplete design inputs, the workflow gracefully handles edge cases by validating available metadata, preserving existing dependencies, and ensuring correct task sequencing across typical project scenarios without failing.

Can I automatically sequence feature prerequisites when creating GitHub issues from a backlog?

You can automatically sequence feature prerequisites when creating GitHub issues by running this workflow on your task backlog. It derives a coherent chain of issues from design artifacts, ensuring clear dependency ordering and correct task sequencing.

What is the best way to align a feature backlog with design artifacts before creating GitHub issues?

The best way to align a feature backlog with design artifacts before creating GitHub issues is to use a conversion workflow that validates issue metadata, applies dependency ordering across project scenarios, and links related artifacts directly to the generated issues.