speckit-taskstoissues

Convert existing tasks into dependency-ordered GitHub issues via a GitHub MCP server.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/fly-eng/yzh --skill speckit-taskstoissues-fly-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/fly-eng/yzh/tree/main/.kimi/skills/speckit-taskstoissues
Command: npx skills add https://github.com/fly-eng/yzh --skill speckit-taskstoissues-fly-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-taskstoissues converts scattered backlog items and design artifacts into actionable, dependency-ordered GitHub issues, ensuring teams can start work with clear priorities and sequence.

Core Features & Use Cases

  • Automated transformation of existing tasks into issues with explicit dependencies.
  • Dependency-aware issue generation aligned to available design artifacts and project structure.
  • Use Case: In a feature sprint, convert all tracked tasks into a coherent set of linked issues to guide developers and prevent rework.

Quick Start

Run the speckit-taskstoissues workflow to generate and create GitHub issues from the current tasks.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert backlog tasks into GitHub issues with dependency ordering?▼

To convert tasks into GitHub issues, the workflow parses existing tasks from your workspace, maps their dependencies, and creates ordered issues via a GitHub MCP server to guide sprint planning.

Does automated GitHub issue generation work with design artifacts and spec-kit project structures?▼

Yes, automated GitHub issue generation applies directly to feature development projects that use design artifacts and a spec-kit structure to produce dependency-aware issue sets.

What is needed to generate dependency-ordered GitHub issues for sprint planning?▼

Generating dependency-ordered issues requires a valid GitHub remote URL and tasks tracked in the local workspace, which are then parsed and published through a GitHub MCP server.

How does this workflow prevent accidental cross-repo writes when creating GitHub issues?▼

The workflow prevents cross-repo writes by enforcing safeguards that restrict issue creation to the repository specified by the valid GitHub remote URL provided in the workspace.

Can I use task-management automation to link scattered backlog items into a coherent sprint set?▼

Yes, task-management automation transforms scattered backlog items into a coherent set of linked GitHub issues with explicit dependencies to prevent developer rework.