speckit-taskstoissues

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

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/chuanyue98/prompt-gallery --skill speckit-taskstoissues-chuanyue98
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/chuanyue98/prompt-gallery/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/chuanyue98/prompt-gallery --skill speckit-taskstoissues-chuanyue98

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts existing spec-kit tasks into actionable GitHub issues that are created in a clear dependency-ordered sequence.

Core Features & Use Cases

  • Dependency-ordered issue creation: Creates one GitHub issue per task while preserving the dependency structure for the feature represented by available design artifacts.
  • Spec-kit aware execution: Uses the repo’s .specify scripts to discover tasks and the feature context from the expected directory layout.
  • Safety guardrails for target repo: Refuses to proceed unless the Git remote resolves to a GitHub URL, preventing accidental issue creation in non-matching or non-GitHub repositories.
  • Extensible pre/post hooks: Supports optional and mandatory extension hooks via .specify/extensions.yml before and after the conversion step.

Quick Start

Run the speckit-taskstoissues Skill in the repository and provide any required arguments to generate GitHub issues for the discovered tasks in dependency order.

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 uses the repository's .specify scripts to discover task definitions and creates one issue per task while preserving their dependency sequence.

How are task dependencies handled when generating GitHub issues from spec-kit?

Task dependencies are resolved during GitHub issue creation by ordering the generated issues according to the dependency structure defined in the spec-kit task sources.

Do I need a specific Git remote configuration to sync spec-kit tasks to GitHub issues?

Yes, the Git remote must resolve to a GitHub URL. The Skill includes safety guardrails that refuse to proceed with issue creation if the repository is non-GitHub or non-matching to prevent accidental commits.

Can I run custom scripts before or after creating GitHub issues from spec-kit tasks?

Yes, you can run custom scripts by configuring optional and mandatory extension hooks in the .specify/extensions.yml file, which execute before and after the task conversion process.

What happens if my repository does not use the expected spec-kit directory layout?

The Skill relies on the expected .specify directory layout to discover tasks and feature context. If the layout is missing, the prerequisite task discovery script will fail to execute properly.

How do I automate repository sync for spec-kit features to GitHub?

You can automate repository sync by running this Skill in the repository to derive feature context from available design artifacts and safely create ordered GitHub issues for each discovered task.