speckit-taskstoissues

Convert design-artifact tasks into dependency-ordered GitHub issues in matching repositories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert existing tasks into actionable, dependency-ordered GitHub issues for a feature based on available design artifacts, streamlining planning and tracking.

Core Features & Use Cases

  • Automated task-to-issue mapping: Transforms tasks into clearly scoped GitHub issues aligned with project design artifacts.
  • Dependency-aware scheduling: Orders issues by logical dependencies to preserve execution order.
  • Safeguarded remote publishing: Creates issues only in repositories that match the detected Git remote, preventing misrouted deployments.

Quick Start

Run the prerequisites check, enumerate tasks, and create GitHub issues for each task in the repository that matches the remote URL.

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 tasks into dependency-ordered GitHub issues?

To convert design tasks into ordered GitHub issues, the Skill maps each task to a repository matching the Git remote and uses MCP to safely create dependency-ordered issues for feature delivery.

Can I automatically create GitHub issues across multiple repositories?

Yes, you can create GitHub issues across multi-repo environments. The Skill maps each task to the repository matching the detected Git remote and uses MCP to create issues in the target repository.

How does repository compatibility verification work when publishing GitHub issues?

Repository compatibility verification checks Git remote URLs before publishing GitHub issues, ensuring the MCP only creates issues in the target repository matching the detected remote to prevent misrouted deployments.

What do I need to start generating GitHub issues from design artifacts?

To generate GitHub issues from design artifacts, you need available design artifacts, mapped tasks, and a Git remote configured in your environment, followed by running a prerequisites check before issue creation.

Why are my GitHub issues not being created in the correct target repository?

GitHub issues may not be created in the correct target repository if the Git remote URL verification fails, which safeguards remote publishing by preventing issue creation in repositories that do not match the detected remote.