speckit-taskstoissues

Convert design-derived tasks into GitHub issues in dependency order.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert design-derived tasks into actionable GitHub issues that reflect dependencies and design requirements, streamlining issue creation from design artifacts.

Core Features & Use Cases

  • Convert design-derived tasks into GitHub issues in the correct dependency order.
  • Validate the repository remote URL to ensure issues are created only in the intended repository.
  • Integrate with an MCP server to automate issue creation across teams when the prerequisites and tasks are identified.

Quick Start

Use the speckit-taskstoissues skill to convert all identified tasks into 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 design tasks into GitHub issues in dependency order?

To validate the GitHub remote URL before creating issues, the automation process checks the repository remote configuration to ensure issues are only generated in the intended target repository. This prevents accidental issue creation in incorrect repositories.

What is the process for turning spec-kit design artifacts into actionable GitHub issues?

Turning spec-kit design artifacts into actionable GitHub issues involves extracting tasks from the design files, validating the remote repository, and using an MCP server to automate issue creation. This streamlines moving design requirements into development tracking.

Do I need an MCP server to automate GitHub issue creation from design artifacts?

To validate the GitHub remote URL before creating issues, the automation process checks the repository remote configuration to ensure issues are only generated in the intended target repository. This prevents accidental issue creation in incorrect repositories.

Can I create GitHub issues from tasks across multiple teams using spec-kit?

You can create GitHub issues from tasks across multiple teams using spec-kit by integrating with a designated MCP server to automate issue creation. The process validates prerequisites and the remote URL to ensure issues are created in the correct target repository.

What limitations exist when automating GitHub issue creation from spec-kit repositories?

Limitations when automating GitHub issue creation from spec-kit repositories include the requirement to work within a spec-kit repository structure and the need for a designated MCP server. Issue creation will fail if the GitHub remote URL validation does not match the intended target repository.