speckit-taskstoissues

Convert spec-kit project tasks into GitHub issues with dependency order.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the conversion of project tasks into GitHub issues, reducing manual effort and streamlining issue tracking.

Core Features & Use Cases

  • Task to Issue Conversion: Converts project tasks into structured GitHub issues with dependency order.
  • Compatibility: Designed for spec-kit project structures with .specify/ directories.
  • Use Case: Ideal for teams using GitHub to manage project tasks, allowing for efficient tracking and collaboration.

Quick Start

Run the command to convert tasks to issues: /speckit-taskstoissues

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

To convert project tasks into GitHub issues automatically, you can use a task automation script that parses your project structure and creates structured issues with dependency order via the GitHub API.

Do I need a specific project structure to automate GitHub issue creation?

Yes, automated GitHub issue creation from project tasks requires a spec-kit project structure containing a .specify directory to parse task definitions accurately.

How does task to issue conversion handle dependencies in GitHub?

Task to issue conversion handles dependencies by parsing project tasks and creating structured GitHub issues that respect and map the original dependency order.

Can I use this task automation without GitHub API access?

No, task automation for converting project tasks to GitHub issues requires GitHub API access to authenticate and create issues in your repositories.

What is the best way to track spec-kit project tasks in GitHub repositories?

The best way to track spec-kit project tasks in GitHub repositories is by automating task to issue conversion, which streamlines issue tracking and team collaboration.

Are there limitations when converting spec-kit tasks to GitHub issues?

A key limitation of converting spec-kit tasks to GitHub issues is the strict requirement for a .specify directory and valid GitHub API access, restricting use outside this structure.