speckit-taskstoissues

Name: speckit-taskstoissues
Availability: InStock
Author: xige169

Convert .specify/ design artifacts into dependency-ordered GitHub issues.

Updated Apr 12, 2026

Search Tags:#automation #github #dependencies #issues #tasks #spec-kit #convert

Ready to run

npx skills add https://github.com/xige169/OnCall --skill speckit-taskstoissues-xige169

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/xige169/OnCall/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/xige169/OnCall --skill speckit-taskstoissues-xige169

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

Automatically transform design artifacts in the .specify/ directory into GitHub issues, preserving task dependencies and intended order.
Ensure issues reference the correct repository remote and avoid cross-repo mis-edits.
Enable automation of issue creation and tracking from design artifacts to implementation tasks.

Quick Start

Instruct the AI to generate GitHub issues from the tasks found in the .specify/ directory, ordering them by dependencies for 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 spec-kit tasks into GitHub issues automatically?▼

To convert spec-kit tasks into GitHub issues, the Skill maps design artifacts from the .specify/ directory into the target repository, preserving task dependencies and intended order. It requires access to the GitHub MCP server to automate issue creation.

How are task dependencies preserved when generating GitHub issues?▼

Task dependencies are preserved by mapping the existing dependency order from the .specify/ directory design artifacts directly into the newly created GitHub issues, ensuring the implementation sequence remains intact during automated issue creation.

Do I need the GitHub MCP server to create issues from .specify/ directory artifacts?▼

Yes, you need the GitHub MCP server to create issues from .specify/ directory artifacts. The Skill requires this server access to verify the GitHub remote URL and scope the automated issue creation to the correct target repository.

Can I use this to generate GitHub issues across multiple repositories?▼

No, you cannot generate GitHub issues across multiple repositories. The Skill enforces GitHub remote verification and uses the repository's remote URL to scope issue creation, preventing cross-repo mis-edits and restricting automated creation to the target repository.

What is the best way to automate issue creation from spec-kit projects?▼

The best way to automate issue creation from spec-kit projects is instructing the AI to read the .specify/ directory, map the design artifacts, and generate dependency-ordered GitHub issues in the target repository using the GitHub MCP server.