taskstoissues

Convert user stories from tasks.md into GitHub issues via the gh CLI.

96|5|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/ArvorCo/Relentless --skill taskstoissues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taskstoissues
Source: https://github.com/ArvorCo/Relentless/tree/main/.claude/skills/taskstoissues
Command: npx skills add https://github.com/ArvorCo/Relentless --skill taskstoissues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of GitHub issues from user stories described in a tasks.md file, eliminating manual drafting and ensuring consistent formatting and labeling across issues.

Core Features & Use Cases

  • Automatic conversion of tasks.md user stories into GitHub issues via the gh CLI.
  • Dependency linking and labeling to reflect relationships and priorities across a repository.
  • Use Case: A product team maintains a backlog in tasks.md and uses this Skill to seed GitHub issues for sprint planning, ensuring traceability from backlog to implementation.

Quick Start

Use this Skill to generate issues from tasks.md by running the appropriate commands with gh CLI against your repository.

Frequently Asked Questions about 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?

You can generate GitHub issues from a tasks.md file by running this Skill, which parses user stories and executes gh CLI commands to automatically create issues with linked dependencies and applied labels.

Do I need the GitHub CLI installed to generate issues from user stories?

Yes, you need the GitHub CLI (gh) installed and authenticated, a Git repository with a configured remote, and a tasks.md file containing your user stories to successfully generate issues.

Can I link dependencies and apply labels when creating GitHub issues in bulk?

Yes, when generating GitHub issues from tasks.md, the Skill automatically links dependencies and applies labels to organize the newly created issues by priority and domain across your repository.

What is the best way to automate sprint planning from a markdown backlog?

Automating sprint planning from a markdown backlog involves parsing user stories in tasks.md and using the gh CLI to seed GitHub issues, ensuring direct traceability from backlog documentation to implementation.

Why does generating GitHub issues from tasks.md require a Git remote?

A Git remote is required because the Skill uses the gh CLI to push the generated GitHub issues directly to the repository hosted on GitHub, relying on the existing remote configuration for authentication and targeting.