speckit-taskstoissues

Convert tasks.md entries into GitHub issues via the GitHub MCP server.

60|12|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/ahmedemad3/super-ai-agency-framework --skill speckit-taskstoissues-ahmedemad3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/ahmedemad3/super-ai-agency-framework/tree/main/.agent/skills/speckit-taskstoissues
Command: npx skills add https://github.com/ahmedemad3/super-ai-agency-framework --skill speckit-taskstoissues-ahmedemad3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts tasks defined in tasks.md into GitHub issues to track work items automatically, bridging planning to execution.

Core Features & Use Cases

  • Automated Issue Creation: Reads tasks from tasks.md and creates a GitHub issue for each task in the target repository.
  • Repository Gatekeeping: Validates that the Git remote is a GitHub URL before creating issues.
  • Use Case: After breaking down work in spec-driven workflows, automatically surface tasks as issues to drive progress tracking.

Quick Start

After you break down tasks into tasks.md, run this skill to automatically create corresponding 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 tasks.md into GitHub issues automatically?

To convert tasks.md into GitHub issues automatically, you need a valid GitHub remote configured. The Skill reads your tasks.md file, resolves each task, and posts them as issues to the GitHub repository via the MCP server.

What is the best way to track spec-driven workflow tasks in GitHub project management?

Tracking spec-driven workflow tasks in GitHub project management is best achieved by converting tasks.md entries directly into GitHub issues. This bridges planning to execution by routing work items through GitHub's native tracking system.

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

Yes, you need a valid GitHub remote to create issues from tasks.md. The Skill validates that your Git remote is a GitHub URL before proceeding, ensuring issues are posted to the correct repository.

Can I use this Skill to break down work in spec-driven workflows?

Yes, you can use this Skill to break down work in spec-driven workflows. After breaking down work into tasks.md, the Skill automatically surfaces those tasks as GitHub issues to drive progress tracking.

Why does converting tasks.md to GitHub issues require validation of my Git remote?

Converting tasks.md to GitHub issues requires Git remote validation to ensure the repository is hosted on GitHub. This gatekeeping step prevents errors by confirming the remote URL is a valid GitHub endpoint before posting issues via the MCP server.