speckit-taskstoissues

Convert tasks into dependency-ordered GitHub issues linked to design artifacts.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT --skill speckit-taskstoissues-zaineldeen-ashraf-ibrahim-ibrahim-samak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT --skill speckit-taskstoissues-zaineldeen-ashraf-ibrahim-ibrahim-samak

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

  • Generate GitHub issues from design artifacts and associated tasks with maintained dependency order.
  • Link issues to design documents, artifacts, and prerequisites to ensure traceability.
  • Use cases include transforming feature handoffs into a structured backlog and preparing sprint-ready work items.

Quick Start

Provide your tasks and design artifacts to generate GitHub issues in the correct 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 automatically?

Yes, you can generate GitHub issues from design artifacts while maintaining correct dependency order. The workflow links each issue to its prerequisite tasks and design documents to ensure full traceability across the project backlog.

Do I need a .specify/ directory to map tasks to GitHub issues?

Yes, a .specify/ directory is required. This folder defines the task relationships and design artifacts needed to automatically map dependencies and create properly linked GitHub issues for your feature.

How does automated task-to-issue creation handle dependencies?

Automated task-to-issue creation handles dependencies by ordering the generated GitHub issues according to the relationships defined in your design artifacts. This ensures prerequisite work is identified and linked before downstream issues are created.

What is the best way to prepare sprint-ready work items from feature handoffs?

The best way to prepare sprint-ready items from feature handoffs is to use automated issue creation from design artifacts. This generates a structured backlog of GitHub issues with maintained dependency order and full document traceability.

Can I link generated GitHub issues back to prerequisite design documents?

Yes, generated GitHub issues are linked directly to design documents, artifacts, and prerequisites. This ensures traceability back to the original feature specifications and task definitions throughout the project lifecycle.