speckit-taskstoissues

Convert design tasks into dependency-ordered GitHub issues linked to design artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert scattered design tasks into a structured backlog of GitHub issues, organized by dependencies and available design artifacts.

Core Features & Use Cases

  • Dependency-ordered task conversion: transforms existing tasks into GitHub issues aligned with design dependencies.
  • GitHub integration: creates issues in the target repository based on detected remote URL.
  • Compatibility: requires spec-kit project structure with a .specify/ directory.

Quick Start

Run the prereq script from the repository root to extract tasks and prepare issues for GitHub.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert design tasks into GitHub issues automatically?

The tool converts scattered design tasks into prioritized GitHub issues by applying dependency-ordering to your backlog. It links generated issues directly to available design artifacts within your feature development workflow.

Do I need a spec-kit directory structure to create GitHub issues from tasks?

Yes, a spec-kit project structure with a .specify directory is required. This compatibility requirement allows the tool to accurately extract scattered tasks and align them with design dependencies before issue creation.

How does dependency ordering work when generating GitHub issues from a backlog?

Dependency ordering transforms existing tasks into GitHub issues aligned with design dependencies. This mechanism structures your backlog by linking issues to available design artifacts in the correct sequence for feature development.

How does the tool authenticate GitHub issue creation for repository tasks?

The tool authenticates GitHub issue creation by depending on the repository's remote URL. It detects the Git remote URL to identify the target repository and creates issues directly within that repository.

What are the limitations of converting tasks to GitHub issues with this approach?

The approach is limited by its strict requirement for a spec-kit .specify directory and a valid repository remote URL. Without these environmental prerequisites, the tool cannot extract tasks or authenticate GitHub issue creation.