speckit-taskstoissues

Convert spec-kit design tasks into GitHub issues with dependencies.

Updated May 11, 2026
One-click install
npx skills add https://github.com/richardnguyen0715/keep-it-real --skill speckit-taskstoissues-richardnguyen0715
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/richardnguyen0715/keep-it-real/tree/main/demo-projects/simple-agent/.github/skills/speckit-taskstoissues
Command: npx skills add https://github.com/richardnguyen0715/keep-it-real --skill speckit-taskstoissues-richardnguyen0715

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of converting tasks from spec-kit projects into structured GitHub issues, improving workflow efficiency and maintainability.

Core Features & Use Cases

  • Task Conversion: Converts tasks into GitHub issues, maintaining dependencies and structure.
  • Spec-Kit Compatibility: Designed for spec-kit project structures with .specify/ directories.
  • Use Case: Ideal for project managers who want to transform design tasks into actionable GitHub issues without manual intervention.

Quick Start

Run the speckit-taskstoissues skill in your project directory to convert tasks into GitHub issues.

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 to GitHub issues automatically?

The skill automates task conversion to GitHub issues by executing scripts that read task definitions from your spec-kit project and create corresponding issues with their dependencies and structure preserved.

What do I need to set up before converting spec-kit tasks to GitHub issues?

Converting spec-kit tasks to GitHub issues requires a spec-kit project structure containing a .specify/ directory and .specify/extensions.yml for extension hooks, plus git and python installed for running scripts.

Does converting spec-kit tasks to GitHub issues preserve task dependencies?

Task conversion maintains dependencies and structure, ensuring the generated GitHub issues reflect the original design task relationships within the spec-kit project.

Can I use this task conversion with any GitHub project structure?

No, the task conversion is designed specifically for spec-kit project structures containing .specify/ directories and requires .specify/extensions.yml for extension hooks.

What's the best way to automate issue tracking from spec-kit design tasks?

Automating issue tracking from spec-kit design tasks is best handled by running the conversion skill, which executes prerequisite check scripts and generates structured GitHub issues directly from task definitions.