speckit.taskstoissues

Convert tasks.md into dependency-ordered GitHub issues via GitHub MCP.

2|Updated Jan 21, 2026

Search Tags:#automation #github #speckit #tasks.md #issue-automation #task-to-issues #dependency-ordering

Ready to run

npx skills add https://github.com/lofidonut3/oh-my-speckit --skill speckit-taskstoissues

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts existing project tasks into actionable, dependency-ordered GitHub issues aligned with available design artifacts, enabling faster start-to-delivery.

Core Features & Use Cases

Automated Task-to-Issue Transformation: maps tasks.md into GitHub issues with proper dependency ordering.
Design-Artifact Driven Prioritization: uses available design artifacts to define scope and sequencing.
Traceability & Automation: creates issues via the MCP server after validating the repository's GitHub remote.

Quick Start

Load .opencode/commands/speckit.taskstoissues.md, process the command file, and automatically create GitHub issues for each task in the configured repository.

Frequently Asked Questions about speckit.taskstoissues

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

FAQPage Schema

How do I convert a tasks.md file into GitHub issues with dependency ordering?▼

To convert tasks.md into GitHub issues with dependency ordering, load the speckit taskstoissues command file. It processes your task list syntax and automatically creates ordered issues via the GitHub MCP server.

What is dependency-ordered issue creation from a project task list?▼

Dependency-ordered issue creation maps tasks from tasks.md into GitHub issues sequenced by their dependencies. It ensures issues are prioritized based on available design artifacts for traceable start-to-delivery.

Do I need a Git remote configured to create GitHub issues from tasks.md?▼

Yes, a valid Git remote is required. The task-to-issues automation verifies the repository's GitHub remote before creating issues through the GitHub MCP server to ensure proper traceability.

Can I use design artifacts to prioritize and scope GitHub issue creation?▼

Yes, the task-to-issues process uses available design artifacts to define scope and sequencing. This design-artifact driven prioritization ensures GitHub issues map accurately to your project tasks.

What's the best way to automate issue creation from a markdown task list?▼

The best way to automate issue creation from a markdown task list is loading the speckit taskstoissues command. It processes special syntax in tasks.md and creates dependency-ordered issues via GitHub MCP.

Why are my GitHub issues not reflecting the correct task dependencies from tasks.md?▼

GitHub issues may not reflect correct dependencies if the task-to-issues process fails to verify the Git remote or properly process special syntax in tasks.md. Ensure your design artifacts define the correct scope.