speckit-taskstoissues

Convert .specify feature tasks into dependency-ordered GitHub issues.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Mohsen3-5/Trader --skill speckit-taskstoissues-mohsen3-5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/Mohsen3-5/Trader/tree/main/Trader/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/Mohsen3-5/Trader --skill speckit-taskstoissues-mohsen3-5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-to-issues converts pre-existing feature tasks into actionable GitHub issues that reflect the available design artifacts and can be processed in dependency order, reducing manual planning and tracking work.

Core Features & Use Cases

  • Dependency-ordered issue creation: Creates GitHub issues representing tasks in a sequence that respects task dependencies.
  • Design-artifact aware conversion: Tailors the created issues based on what design artifacts are present in the repo.
  • GitHub-safe operation: Refuses to proceed unless the repository remote is a GitHub URL to prevent accidental issue creation elsewhere.

Quick Start

Run speckit-taskstoissues from the repo to convert existing tasks into GitHub issues for the current feature set.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert feature tasks into GitHub issues in dependency order?

To convert feature tasks into dependency-ordered GitHub issues, this skill reads existing tasks from .specify scripts and applies argument-based filtering. It then creates representative issues via the GitHub MCP server, ensuring they are sequenced according to task dependencies.

What design artifacts are needed for spec-kit task conversion?

Spec-kit task conversion requires available design artifacts within the project structure to tailor the created GitHub issues. The process specifically checks .specify/extensions.yml for before/after hooks and runs check-prerequisites.ps1 with RequireTasks and IncludeTasks arguments.

Does this task conversion tool work with non-GitHub repositories?

No, task conversion is GitHub-safe and explicitly refuses to proceed if the repository remote is not a GitHub URL. This prevents accidental issue creation on incorrect platforms and ensures operations target GitHub exclusively.

How do I run speckit-taskstoissues from my repository?

Run speckit-taskstoissues directly from the repository root to convert existing tasks into GitHub issues for the current feature set. The execution validates git remotes, checks prerequisites, and processes hooks before creating issues.

Why does my spec-kit to issues conversion fail with a remote URL error?

Spec-kit to issues conversion fails with a remote URL error if the git remote is not a valid GitHub URL. The skill validates the remote origin beforehand and stops execution to prevent creating issues on unsupported platforms.