speckit-taskstoissues

Create GitHub issues from tasks.md using the current git remote.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-taskstoissues-leonardomoraisf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/leonardomoraisf/commonplace-pinboard-extension/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-taskstoissues-leonardomoraisf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts structured task breakdowns into actionable GitHub issues, eliminating manual issue creation and ensuring traceability from planning to execution.

Core Features & Use Cases

  • Automated Issue Creation: Generate GitHub issues from tasks.md, preserving task details and context.
  • Repository-Scoped Tracking: Creates issues in the repository corresponding to the current git remote, aligning work items with the correct project.
  • Use Case: After breaking down product work in tasks.md, run this skill to auto-create issues for development, QA, and documentation tasks, preserving the original task order and metadata.

Quick Start

Run the skill on your repository to convert 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 create GitHub issues from a markdown task list?

To create GitHub issues from a markdown task list, this skill reads a tasks.md file and uses a GitHub MCP server to instantiate issues in the repository identified by your current git remote. It eliminates manual issue creation by converting structured task breakdowns directly into actionable tracking items.

What is the best way to convert tasks.md into GitHub issues for project management?

The best way to convert tasks.md into GitHub issues for project management is running this skill, which preserves task metadata and original order while scoping issue creation to the matching GitHub repository. It ensures traceability from planning to execution without manual data entry.

Does this issue conversion skill work with any git remote?

This issue conversion skill only works if your git remote points to a GitHub URL, validating the remote address before using the GitHub MCP server to create issues. It requires a tasks.md file containing the structured breakdown of work items to function correctly.

How are task details and context preserved when generating GitHub issues?

Task details and context are preserved when generating GitHub issues by reading the tasks.md file structure and passing the metadata directly to the GitHub MCP server. This ensures development, QA, and documentation tasks retain their original descriptions and context during automated issue creation.

Can I use this skill to automate issue creation for multiple repositories?

You cannot use this skill to automate issue creation for multiple repositories simultaneously, as it is repository-scoped and creates issues only in the repository corresponding to the current git remote. You must run the skill individually within each target repository environment.