speckit-taskstoissues

Name: speckit-taskstoissues
Availability: InStock
Author: raphaelfh

Convert design tasks into dependency-ordered GitHub issues.

10|3|Updated Apr 2, 2026

Search Tags:#automation #speckit #spec-kit #task-management #dependency-graph #github-issues

Ready to run

npx skills add https://github.com/raphaelfh/newsweep --skill speckit-taskstoissues-raphaelfh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/raphaelfh/newsweep/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/raphaelfh/newsweep --skill speckit-taskstoissues-raphaelfh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert existing tasks into actionable GitHub issues ordered by their dependencies based on design artifacts found in the .specify directory.

Core Features & Use Cases

Automatically converts tasks into GitHub issues arranged in dependency order to reflect prerequisite relationships.
Integrates with spec-kit projects via a .specify directory to map tasks to issues and maintain traceability.
Supports labeling, scope control, and reuse of design artifacts to accelerate issue creation.
Use Case: For a feature defined by several tasks with dependencies, generate a linked chain of issues that guides implementation.

Quick Start

From the repository root, run the speckit taskstoissues workflow to create GitHub issues for each task.

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 design tasks into GitHub issues ordered by dependencies?▼

Run the taskstoissues workflow from your repository root to map tasks from the .specify directory into GitHub issues. It automatically arranges the generated issues based on prerequisite relationships defined in your design artifacts.

What is the .specify directory used for in task to issue conversion?▼

The .specify directory stores design artifacts used to map tasks to issues and maintain traceability. It allows the workflow to reuse existing design data to accelerate the creation of linked GitHub issues.

Do I need a GitHub token to generate GitHub issues from spec-kit tasks?▼

Yes, you need a GitHub token to post issues to the repository. A matching Git remote URL is also required to ensure the workflow writes issues to the correct repository.

Can I control the scope and labels when generating GitHub issues from design tasks?▼

Yes, the taskstoissues workflow supports labeling and scope control. This allows you to manage which design artifacts are included and how the resulting GitHub issues are categorized.

How does the taskstoissues workflow prevent cross-repo writes when posting to GitHub?▼

The workflow includes safeguards to prevent cross-repo writes by requiring a matching Git remote URL. This ensures issues are only posted to the specific repository configured in the project.