speckit-taskstoissues

Convert design artifact tasks into dependency-ordered GitHub issues.

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

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 directly from a set of tasks referenced in design artifacts, preserving task dependencies and relationships.
  • Align issue creation with design artifacts to ensure traceability from design to implementation.
  • Use case: When planning a feature, convert a list of tasks and linked design specs into a sequence of issues, each with clear dependencies and acceptance criteria.

Quick Start

Provide the task list and design artifacts, then trigger automatic creation of GitHub issues in 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 with dependencies?

To convert design artifacts into GitHub issues, provide the task list and design specs to the Skill. It identifies tasks, determines the remote GitHub URL, and creates dependency-ordered issues via a GitHub MCP server while validating the remote origin.

Can I create multiple GitHub issues in dependency order from a single feature task list?

Yes, you can create multiple GitHub issues in dependency order from a feature task list. The Skill generates issues directly from referenced design artifacts, preserving task dependencies and relationships for sequential implementation.

Do I need a GitHub MCP server to automatically create issues from tasks?

Yes, a GitHub MCP server is required to automatically create issues from tasks. The Skill uses the MCP server to validate the remote origin, determine the GitHub URL, and create the issues in the repository.

What is the best way to align GitHub issue creation with design artifacts?

The best way to align GitHub issue creation with design artifacts is to use a conversion tool that maps tasks to issues. This Skill aligns issue creation with design specs to ensure traceability from design to implementation with clear dependencies and acceptance criteria.

How does validating the remote GitHub origin work when generating issues?

Validating the remote GitHub origin works by verifying the repository's remote URL before issue creation. The Skill determines the remote GitHub URL, validates the origin, and then proceeds to create issues via the GitHub MCP server.

Why are my task dependencies not preserved when creating GitHub issues?

Task dependencies may not be preserved if the conversion process does not parse design artifacts correctly. This Skill specifically generates GitHub issues while preserving task dependencies and relationships referenced in the design documents.