speckit-taskstoissues

Converts spec-kit tasks and design artifacts into dependency-ordered GitHub issues.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/vZulin/overlay-clock-timer --skill speckit-taskstoissues-vzulin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/vZulin/overlay-clock-timer/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/vZulin/overlay-clock-timer --skill speckit-taskstoissues-vzulin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts scattered tasks and design artifacts into structured, dependency-aware GitHub issues to streamline feature work and improve traceability.

Core Features & Use Cases

  • Task-to-issue mapping: automatically generated GitHub issues from design notes and task lists, preserving relationships and priorities.
  • Dependency-aware sequencing: creates and links issues in an order that respects task dependencies.
  • Context propagation: includes design references and notes to aid triage and implementation.

Quick Start

Run the speckit tool against your project to generate dependency-ordered GitHub issues from design artifacts and task lists.

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 automatically?

You can convert design artifacts into GitHub issues by using a spec-kit structure to map tasks, preserve dependencies, and generate executable instructions for repository creation.

How do I create dependency-ordered GitHub issues for feature planning?

Dependency-ordered GitHub issues are created by analyzing task relationships within design artifacts and sequencing the issues to respect task dependencies during generation.

Does this task-to-issue conversion require a specific project structure?

Yes, task-to-issue conversion requires a project with a spec-kit structure containing a .specify directory to properly read metadata and check for optional extension hooks.

What is the best way to link task dependencies in GitHub issues?

The best way to link task dependencies in GitHub issues is to use a spec-kit tool that analyzes design artifacts and automatically sequences and links the generated issues.

Can I include design references and notes when generating GitHub issues from tasks?

Yes, context propagation includes design references and notes within the generated GitHub issues to aid triage and implementation during feature planning.