speckit.taskstoissues

Convert design-derived tasks into dependency-ordered GitHub issues.

63|13|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/compnew2006/Spec-Kit-Antigravity-Skills --skill speckit-taskstoissues-compnew2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.taskstoissues
Source: https://github.com/compnew2006/Spec-Kit-Antigravity-Skills/tree/main/skills/speckit.taskstoissues
Command: npx skills add https://github.com/compnew2006/Spec-Kit-Antigravity-Skills --skill speckit-taskstoissues-compnew2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert scattered design-derived tasks into actionable, dependency-ordered GitHub issues to enable precise tracking and collaboration.

Core Features & Use Cases

  • Task-to-issue mapping: Transform each task into a linked GitHub issue with defined dependencies.
  • Artifact-aware: Base issue content on available design artifacts to preserve context.
  • Repository guardrails: Only create issues in the repository matching the remote URL; validates before action.

Quick Start

Convert the given task list into a set of GitHub issues in the target repository.

Frequently Asked Questions about speckit.taskstoissues

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

FAQPage Schema
How do I convert tasks into GitHub issues with dependencies?

To convert tasks into GitHub issues, this Skill maps each task into a linked issue with defined dependencies. It uses available design artifacts to preserve context and sets an execution order for precise project tracking.

Can I automatically create GitHub issues from a list of design tasks?

Yes, you can create GitHub issues from design tasks by mapping the list into the repository. The Skill is artifact-aware, meaning it bases the generated issue content on available design artifacts to maintain full project context.

Do I need a GitHub MCP server to convert tasks into traceable issues?

Yes, you need access to the GitHub MCP server to convert tasks into traceable issues. The process also requires a repository remote that matches the target repository where the issues will be created.

What are the limitations when generating GitHub issues from task lists?

A key limitation is that GitHub issues can only be created in the repository matching the remote URL. The Skill validates the target repository before taking action and will not create issues across multiple different repositories.

What is the best way to track project dependencies using GitHub issues?

The best way to track project dependencies is by converting scattered tasks into dependency-ordered GitHub issues. This enables precise tracking and collaboration by linking related issues based on their required execution sequence.