speckit-taskstoissues

Convert tasks from a .specify/ directory into GitHub issues.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/gherrerz/deepwiki --skill speckit-taskstoissues-gherrerz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/gherrerz/deepwiki/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/gherrerz/deepwiki --skill speckit-taskstoissues-gherrerz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-spec-kit, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of converting existing tasks into GitHub issues, reducing manual effort and ensuring a structured project workflow.

Core Features & Use Cases

  • Task Conversion: Converts tasks from a .specify/ directory into GitHub issues.
  • Dependency Ordering: Creates issues in a dependency-ordered manner based on design artifacts.
  • Integration: Requires a spec-kit project structure with a .specify/ directory.
  • Use Case: Ideal for teams that want to track and manage tasks directly in GitHub, leveraging design artifacts for issue creation.

Quick Start

Run the skill with the command: /speckit-taskstoissues

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?

You can automate task conversion by running a skill that reads tasks from the `.specify/` directory and utilizes the GitHub Issue Creation API to generate structured project management issues automatically.

What is the best way to create GitHub issues from spec-kit design artifacts?

The best way to create GitHub issues from spec-kit design artifacts is to automate task conversion in a dependency-ordered manner, ensuring structured project management directly from your existing design files.

Do I need a spec-kit project structure to automate GitHub issue creation?

Yes, you need a spec-kit project structure containing a `.specify/` directory to automate GitHub issue creation, as the process relies on reading design artifacts from that specific location.

How does dependency ordering work when converting tasks to GitHub issues?

Dependency ordering during task conversion creates GitHub issues based on relationships defined in spec-kit design artifacts, ensuring prerequisite tasks are structured correctly within your project management workflow.

Can I use this task conversion skill without the github-spec-kit dependency?

No, you cannot use this task conversion without the github-spec-kit dependency, as the skill requires the spec-kit project structure and its associated design artifacts to function properly.