speckit-taskstoissues

Converts tasks from a tasks.md file into GitHub issues in a spec-kit project.

13|2|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/NebulaMao/nanoiflow --skill speckit-taskstoissues-nebulamao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/NebulaMao/nanoiflow/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/NebulaMao/nanoiflow --skill speckit-taskstoissues-nebulamao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of converting tasks defined in a tasks.md file into trackable GitHub issues, streamlining project management workflows.

Core Features & Use Cases

  • Task Conversion: Transforms individual tasks into GitHub issues.
  • Project Tracking: Facilitates better work item management within GitHub projects.
  • Use Case: After breaking down a feature into a list of actionable tasks in tasks.md, use this Skill to automatically create corresponding issues in your GitHub repository for team assignment and progress tracking.

Quick Start

Use the speckit-taskstoissues skill to convert tasks from tasks.md into 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 a list of tasks from markdown into GitHub issues automatically?

You can create GitHub issues from a `tasks.md` file using this Skill, which requires a spec-kit project structure with a `.specify/` directory. It automatically transforms your documented actionable tasks into trackable GitHub issues for team assignment and progress tracking.

Do I need a specific project structure to convert tasks.md into GitHub issues?

Yes, converting `tasks.md` into GitHub issues requires a spec-kit project structure containing a `.specify/` directory. Additionally, your project must have a configured GitHub remote URL to enable issue creation within the associated repository.

What is the best way to track actionable feature tasks on GitHub after writing them in markdown?

The best way to track markdown feature tasks on GitHub is to convert them directly into repository issues. This Skill takes individual tasks defined in `tasks.md` and generates corresponding GitHub issues, facilitating better work item management and team assignment.

Why does converting tasks to GitHub issues fail without a GitHub remote URL?

Converting tasks to GitHub issues fails without a remote URL because the Skill needs a target repository endpoint to push the created issues to. Issue creation explicitly requires a configured GitHub remote URL within your spec-kit project to function correctly.

Can I use this task conversion for project management workflows requiring task breakdown?

Yes, this task conversion applies directly to project management workflows requiring task breakdown and issue tracking on GitHub. After breaking down a feature into actionable tasks in `tasks.md`, it automatically creates corresponding issues for progress tracking.