speckit-taskstoissues

Convert design artifacts into dependency-ordered GitHub issue backlogs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert design artifacts into a clear, prioritized backlog of GitHub issues, ready for implementation.

Core Features & Use Cases

  • Converts design artifacts into actionable GitHub issues.
  • Produces a dependency-ordered backlog aligned with the project design artifacts.
  • Integrates with a spec-kit workflow using a .specify/ directory.

Quick Start

Provide the project tasks and design artifacts, and run Speckit to generate a dependency-ordered set of 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 design artifacts into GitHub issues?

To convert design artifacts into GitHub issues, you provide your project tasks and design files to the tool, which parses them and formats dependency-ordered backlogs with titles, descriptions, and artifact links.

How do I generate a dependency-ordered backlog for GitHub features?

You can generate a dependency-ordered backlog by parsing your design artifacts, resolving task dependencies, and formatting the results into GitHub-ready issues with artifact linking.

Do I need a .specify/ directory to create GitHub issues from design artifacts?

Yes, you need a .specify/ directory because the tool integrates with a spec-kit workflow to parse your design artifacts and resolve task dependencies for prioritized issues.

What is the best way to automate creating prioritized GitHub issues from project tasks?

The best way to automate creating prioritized GitHub issues is using a tool that parses design artifacts and resolves task dependencies to format a structured, ready-to-implement backlog.

Can I link design artifacts directly when converting tasks to GitHub issues?

Yes, you can link design artifacts directly because the tool formats GitHub-ready issues with titles, descriptions, and explicit linking to your parsed project artifacts.