speckit-taskstoissues

Convert design tasks from a .specify directory into dependency-ordered GitHub issues via MCP-based server.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/william-menezes/pet-volta --skill speckit-taskstoissues-william-menezes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/william-menezes/pet-volta/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/william-menezes/pet-volta --skill speckit-taskstoissues-william-menezes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert existing design-derived tasks into a structured set of GitHub issues, ordered by dependencies to drive reliable feature delivery.

Core Features & Use Cases

  • Dependency-ordered issue generation from design artifacts.
  • Automated mapping of tasks to GitHub issues ready for MCP-based creation.
  • Use-case: Convert a feature's design tasks into a linked chain of issues reflecting dependencies.

Quick Start

Run the speckit tasks-to-issues workflow to generate dependency-ordered GitHub issues from your design artifacts.

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 ordered by dependencies?

To convert design tasks into dependency-ordered GitHub issues, you run the spec-kit tasks-to-issues workflow. This process reads your design artifacts from a .specify/ directory and maps the defined tasks and dependencies into a structured chain of automated GitHub issues.

What is the best way to automate issue creation from spec-kit design artifacts?

Automating issue creation from spec-kit design artifacts requires a GitHub MCP-based server and a valid repository remote. The workflow validates that your remote URL points to GitHub, then automatically generates and creates the ordered issues.

Do I need a GitHub MCP-based server to create issues from my .specify directory?

Yes, a GitHub MCP-based server is required to create issues from your .specify directory. The workflow relies on this server connection to interact with your GitHub repository and validate the remote URL before generating the dependency-ordered issues.

Can I use this task-to-issues workflow if my repository remote is not GitHub?

No, you cannot use this workflow if your repository remote is not GitHub. The process explicitly validates that the remote URL points to GitHub before proceeding with the automated issue creation from your design tasks.

How does dependency management work when generating GitHub issues from design tasks?

Dependency management during issue generation works by reading task definitions and their relationships from the .specify/ directory. It then structures the generated GitHub issues to reflect these dependencies, creating a linked chain that enables guided feature development.