speckit-taskstoissues

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

Updated Jan 28, 2024
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/KrockSide --skill speckit-taskstoissues-thiago-cruz-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/Thiago-Cruz-eng/KrockSide/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/Thiago-Cruz-eng/KrockSide --skill speckit-taskstoissues-thiago-cruz-eng

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. This Skill automates that conversion inside a spec-kit workflow. ## Core Features & Use Cases - Automated Issue Creation: Reads the feature's tasks file and creates one GitHub issue per task using the GitHub MCP server. - Remote Safety Guard: Verifies the git remote is a GitHub URL and refuses to create issues in any repository that does not match the remote. - Extension Hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml around the conversion step. - Use Case: After running the spec-kit tasks command for a new feature, invoke this Skill to publish every task as a labeled, ordered GitHub issue in the matching repository for team tracking. ## Quick Start Ask the assistant to convert the current feature's tasks into GitHub issues, optionally passing a filter or label 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 convert spec-kit tasks into GitHub issues?▼

Invoke the taskstoissues command after generating tasks with spec-kit. It runs check-prerequisites.ps1 to locate the tasks file, verifies the git remote is a GitHub URL, then creates one issue per task via the GitHub MCP server.

What is required before running tasks to issues conversion?▼

You need a spec-kit project structure with a .specify directory, an existing tasks file for the feature, and a git remote pointing to GitHub. The Skill parses FEATURE_DIR and AVAILABLE_DOCS from the prerequisites script.

Does this work with non-GitHub git remotes like GitLab?▼

No. The Skill explicitly checks that the remote origin URL is a GitHub URL and stops if it is not. It never creates issues in repositories that do not match the configured remote.

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

Yes, the command accepts an optional argument described as a filter or label for the GitHub issues. The Skill instructs that user input must be considered before proceeding with the conversion.

What are extension hooks in the taskstoissues workflow?▼

Hooks are commands declared under hooks.before_taskstoissues or hooks.after_taskstoissues in .specify/extensions.yml. Enabled hooks run before or after conversion; mandatory hooks execute automatically while optional ones are only suggested.