speckit-taskstoissues

Converts tasks.md entries into GitHub issues with original IDs referenced.

120|25|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/dceoy/speckit-agent-skills --skill speckit-taskstoissues-dceoy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/dceoy/speckit-agent-skills/tree/main/skills/speckit-taskstoissues
Command: npx skills add https://github.com/dceoy/speckit-agent-skills --skill speckit-taskstoissues-dceoy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts tasks.md entries into actionable GitHub issues within the corresponding repository, enabling traceable task management across the Spec Kit workflow.

Core Features & Use Cases

  • Automatically translate each task listed in tasks.md into a separate GitHub issue with the task ID embedded for traceability.
  • Validate the repository's Git remote URL and ensure issues are created in the matching repository to maintain alignment with source design artifacts.
  • Supports end-to-end workflow from design artifacts to actionable work items across teams.

Quick Start

Run a dedicated speckit-tasks-to-issues workflow to generate issues from the repository's tasks.md file in the repository that matches the configured Git remote.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert tasks.md entries into GitHub issues automatically?

To convert tasks.md entries into GitHub issues, the workflow parses the markdown task catalog and creates a separate GitHub issue for each task in the repository matching the Git remote. Each generated issue embeds the original task ID for traceability.

How does converting tasks.md to GitHub issues keep track of original task IDs?

Converting tasks.md to GitHub issues maintains traceability by embedding the original task ID directly into the generated issue title and body, linking the actionable GitHub issue back to the specific feature-level task catalog entry.

Do I need a GitHub remote URL configured to generate issues from tasks.md?

Yes, generating issues from tasks.md requires a valid GitHub remote URL configured in your repository. The workflow validates the Git remote URL and ensures issues are created in the matching GitHub repository.

Can I create GitHub issues from a markdown task list across multiple feature catalogs?

Creating GitHub issues from a markdown task list supports feature-level task catalogs by iterating through the tasks.md file and generating separate issues for each task within the corresponding GitHub repository.

What happens if my Git remote URL is not hosted on GitHub when converting tasks?

If the Git remote URL is not hosted on GitHub, converting tasks to issues will fail the prerequisite validation. The workflow ensures issues are only created in a verified GitHub repository matching the remote.