speckit-taskstoissues

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

44|10|Updated Mar 28, 2024
One-click install
npx skills add https://github.com/sensein/senselab --skill speckit-taskstoissues-sensein
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/sensein/senselab/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/sensein/senselab --skill speckit-taskstoissues-sensein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually translating a feature's task list into trackable GitHub issues is repetitive and error-prone, especially when tasks must respect dependency ordering and stay tied to the correct repository. ## Core Features & Use Cases - Automated Issue Creation: Reads the tasks file produced by a spec-kit workflow and creates one GitHub issue per task using the GitHub MCP server. - Repository Safety Checks: Verifies the Git remote is a GitHub URL and refuses to create issues in any repository that does not match the remote origin. - Prerequisite Validation: Runs the spec-kit check-prerequisites script to resolve the feature directory and confirm tasks exist before proceeding. - 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 for team assignment. ## Quick Start Ask the assistant to convert the current feature's tasks into GitHub issues, optionally providing a label or filter as an argument.

Frequently Asked Questions about speckit-taskstoissues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn spec-kit tasks into GitHub issues?▼

Invoke the taskstoissues command in a spec-kit project after tasks have been generated. It runs check-prerequisites to locate the tasks file, then creates one GitHub issue per task through the GitHub MCP server.

What is required before converting tasks to GitHub issues?▼

The project must use the spec-kit structure with a .specify directory, contain a generated tasks file for the feature, and have a Git remote pointing to a GitHub repository. The GitHub MCP server must also be available.

Does taskstoissues work with non-GitHub remotes like GitLab?▼

No. The Skill checks the output of git config remote.origin.url and only proceeds if the remote is a GitHub URL. It explicitly refuses to create issues in repositories that do not match the remote.

Can I filter or label the GitHub issues it creates?▼

Yes. The Skill accepts an optional argument described as a filter or label for the GitHub issues, which is considered before the issues are created.

Why does taskstoissues stop before creating any issues?▼

It halts if the prerequisite script fails, if no tasks file exists for the feature, or if the Git remote is not a GitHub URL. These guards prevent issues from being created in the wrong repository or without valid task data.