speckit-taskstoissues

Convert spec-kit tasks into dependency-ordered GitHub issues via prerequisite scripts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts existing feature tasks into actionable GitHub issues in a dependency-ordered way, using the available design artifacts and repository context.

Core Features & Use Cases

  • Extension hook support (pre and post): Reads .specify/extensions.yml to optionally run registered before/after hooks, printing the correct slash commands and enforcing hook execution ordering for mandatory hooks.
  • Prerequisite-driven task discovery: Runs the repository prerequisite script to obtain FEATURE_DIR and an AVAILABLE_DOCS list, extracts the tasks path, and requires tasks to proceed.
  • Safety-guarded issue creation: Retrieves the Git remote URL, verifies it is a GitHub URL, and only then creates issues via the GitHub MCP server for the representative repository.
  • Operational alignment to spec-kit structure: Works with spec-kit project structure by using the .specify directory layout as expected by the skill.

Quick Start

Run the skill with an optional filter or label argument to generate dependency-ordered GitHub issues from the tasks discovered in your spec-kit project.

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 convert spec-kit tasks into GitHub issues, the skill discovers tasks via prerequisite scripts and maps them to a GitHub repository, creating issues in a dependency-ordered sequence using the GitHub MCP server.

What is the process for creating GitHub issues from existing spec-kit design artifacts?

Creating GitHub issues from spec-kit design artifacts involves reading optional .specify/extensions.yml hooks, validating the origin remote is a GitHub URL, and generating trackable work items from the discovered task list.

Can I use custom hooks when generating GitHub issues from a spec-kit project?

Yes, you can use custom hooks when generating GitHub issues by reading the .specify/extensions.yml file to run registered pre and post hooks, which enforces execution ordering for mandatory hooks during issue creation.

Does this task conversion method require a specific Git remote configuration?

Yes, this task conversion method requires a specific Git remote configuration because it retrieves the Git remote URL and strictly verifies it is a GitHub URL before attempting to create issues via the GitHub MCP server.

What happens if the prerequisite script does not find available tasks in the spec-kit directory?

If the prerequisite script does not find available tasks in the spec-kit directory, the process requires tasks to proceed and will halt issue creation because it extracts the tasks path from the AVAILABLE_DOCS list.

How do I filter which feature tasks are turned into GitHub issues?

You can filter which feature tasks are turned into GitHub issues by running the skill with an optional filter or label argument, which generates dependency-ordered GitHub issues from the tasks discovered in your spec-kit project.