skills.rest
torikhayes
torikhayesCOMMUNITY
Explore all skills by this author →
GitHub

speckit-taskstoissues

Convert spec-kit tasks into dependency-ordered GitHub issues via the GitHub MCP server.

Updated Jul 13, 2026
Search Tags:#github issues#spec-driven development#spec-kit#issue automation#task conversion#github mcp
One-click install
npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill speckit-taskstoissues-torikhayes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/torikhayes/aeai-dotnet-brownfield/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill speckit-taskstoissues-torikhayes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually translating a feature's task list into GitHub issues is repetitive and error-prone, especially when tasks must stay dependency-ordered and tied to the correct repository remote. ## Core Features & Use Cases - Automated Issue Creation: Reads the tasks file produced by spec-kit and creates one GitHub issue per task using the GitHub MCP server. - Remote Safety Validation: Verifies the git remote origin URL is a GitHub repository and refuses to create issues in any repository that does not match the remote. - Extension Hook Support: Runs optional or mandatory pre/post hooks declared in .specify/extensions.yml before and after conversion. - Use Case: After generating a tasks.md breakdown for a new feature in a spec-kit project, invoke this Skill to publish every task as a labeled, ordered GitHub issue in the matching repository. ## Quick Start Ask the assistant to convert the current feature's tasks into GitHub issues for this 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 spec-kit tasks into GitHub issues?▼

Run the taskstoissues command in a spec-kit project. It executes check-prerequisites.sh to locate the tasks file, confirms the git remote is a GitHub URL, then creates one issue per task through the GitHub MCP server.

What is required before converting tasks to GitHub issues?▼

You need a spec-kit project with a .specify directory, an existing tasks file for the feature, and a git remote origin pointing to a GitHub repository. The GitHub MCP server must also be available.

Can I create GitHub issues in a different repository than the remote?▼

No. The Skill explicitly refuses to create issues in any repository that does not match the git remote origin URL, preventing accidental issue creation in unrelated repositories.

What happens if the git remote is not a GitHub URL?▼

The workflow stops before creating any issues. The instructions state to only proceed when the remote origin URL is a GitHub URL, so non-GitHub remotes halt the conversion.

How do extension hooks work with tasks-to-issues conversion?▼

If .specify/extensions.yml defines hooks under before_taskstoissues or after_taskstoissues, enabled hooks run as slash commands around the conversion. Optional hooks are suggested, while mandatory hooks execute automatically.

Related Skills

Explore More Software Engineering Skills→
KamiJeongKamiJeong

speckit-tasks

Generate a dependency-ordered tasks.md from Spec Kit project artifacts.

Community
Advanced
EmasoftEmasoft

eia-github-project-workflow

Create GitHub Project boards and issues with acceptance criteria for multi-developer workflows.

Community
Advanced
brittbritt
5

issue-decomposition

Decompose project descriptions into structured GitHub issues with user stories and estimates.

Community
Intermediate
russosalvrussosalv
5

spec-to-workitem

Translate NONoise sprint manifest macro tasks into external issue tracker work items.

Community
Advanced