speckit-taskstoissues

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

Updated Aug 23, 2025
One-click install
npx skills add https://github.com/engakhattab/DEPI_Angular_project --skill speckit-taskstoissues-engakhattab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/engakhattab/DEPI_Angular_project/tree/main/Backend/HR/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/engakhattab/DEPI_Angular_project --skill speckit-taskstoissues-engakhattab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents messy, unordered issue creation by converting existing tasks into actionable GitHub issues with a dependency-ordered sequence based on available design artifacts.

Core Features & Use Cases

  • Automated issue generation: Creates new GitHub issues for each task derived from available task definitions.
  • Dependency-ordered planning: Ensures issues follow a prerequisite-aware order so implementers can work efficiently.
  • Repository safety guardrail: Only proceeds when the detected git remote is a GitHub URL to avoid creating issues in the wrong repository.

Quick Start

Run the speckit-taskstoissues Skill to generate dependency-ordered GitHub issues from the tasks found via the prerequisite check in your repo.

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 with dependency ordering?

To generate dependency-ordered GitHub issues from spec-kit tasks, the skill validates repository prerequisites, extracts task paths from design artifacts, and creates tracked issues sequentially using the GitHub MCP server.

What is the best way to automate GitHub issue creation from design artifacts?

Automating GitHub issue creation from design artifacts involves extracting defined task paths and using the GitHub MCP server to publish them as tracked issues, ensuring a prerequisite-aware sequence for efficient implementation.

Does this task-to-issue conversion require a specific git remote configuration?

Yes, task-to-issue conversion requires the detected git remote to be a valid GitHub URL, acting as a safety guardrail to prevent creating tracked execution issues in the wrong repository.

How do I validate repository prerequisites before generating GitHub issues?

Validating repository prerequisites before generating GitHub issues requires running a powershell check to extract task paths and verify the git remote configuration for safe, automated issue creation.

Why are my generated GitHub issues ordered by dependencies?

Generated GitHub issues are ordered by dependencies to ensure a prerequisite-aware sequence, preventing messy creation and allowing implementers to work efficiently through the tracked execution plan.

Can I use this automated issue generation with non-GitHub repositories?

No, automated issue generation only proceeds when the detected git remote is a GitHub URL, ensuring issues are safely created in the correct repository environment through the GitHub MCP server.