speckit-taskstoissues

Convert spec-kit tasks into dependency-ordered GitHub issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jacobbweber/Zerto-PS-Admin-SDD --skill speckit-taskstoissues-jacobbweber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/jacobbweber/Zerto-PS-Admin-SDD/tree/main/.agent/skills/speckit-taskstoissues
Command: npx skills add https://github.com/jacobbweber/Zerto-PS-Admin-SDD --skill speckit-taskstoissues-jacobbweber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts scattered design and task artifacts into tracked, dependency-ordered GitHub issues to eliminate manual issue creation and ensure feature work is captured in the repository's issue tracker.

Core Features & Use Cases

  • Automated discovery: Executes the spec-kit prerequisite script to locate the FEATURE_DIR and the available design documents and task lists.
  • Safe issue creation: Verifies the git remote is a GitHub URL before creating issues and ensures issues are created only in the matching repository.
  • Dependency ordering: Translates task lists into actionable issues while preserving or inferring task dependencies for proper sequencing.
  • Use Case: When a feature design is delivered with a .specify directory of tasks, use this Skill to programmatically create corresponding GitHub issues so triage and implementation can begin immediately.

Quick Start

Use the speckit-taskstoissues skill to convert the feature tasks found in the repository's .specify directory into dependency-ordered GitHub issues in the repository with a valid GitHub remote.

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, this skill runs the prerequisite check script to locate the feature directory, verifies the git remote is a GitHub URL, and uses the GitHub MCP API to create dependency-ordered issues in the matching repository.

What is the best way to create dependency-ordered GitHub issues from a .specify directory?

Creating dependency-ordered GitHub issues from a .specify directory involves executing the spec-kit prerequisite script to discover available task lists and design artifacts, then translating those tasks into tracked issues while preserving or inferring their task dependencies.

Does this automated issue creation tool work with any Git repository?

Automated issue creation only works with repositories that have a valid GitHub remote URL. The skill verifies the git remote before creating issues and ensures they are created only in the matching GitHub repository via the GitHub MCP API.

What is the .specify prerequisite script used for when generating GitHub issues?

The .specify prerequisite script is used for automated discovery of the FEATURE_DIR, locating the available design documents and task lists needed to programmatically generate corresponding GitHub issues for triage and implementation.

Why are my spec-kit tasks not converting into GitHub repository issues?

Spec-kit tasks may not convert into GitHub repository issues if the git remote is not a valid GitHub URL. The skill requires running the prerequisite script to locate tasks and validates the remote before creating issues via the GitHub MCP API.