speckit-taskstoissues

Converts spec-kit tasks into GitHub issues with dependencies and labels via the GitHub MCP server.

1|1|Updated May 31, 2026
One-click install
npx skills add https://github.com/WayneSHC/polaris-desk --skill speckit-taskstoissues-wayneshc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/WayneSHC/polaris-desk/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/WayneSHC/polaris-desk --skill speckit-taskstoissues-wayneshc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the conversion of tasks into GitHub issues, ensuring a structured workflow for project management.

Core Features & Use Cases

  • Task Conversion: Converts tasks into GitHub issues with dependencies and labels.
  • Design Artifacts: Utilizes design artifacts to ensure issues are actionable.
  • Project Structure: Requires a spec-kit project structure with a .specify/ directory.

Quick Start

Run the 'speckit-taskstoissues' command to convert tasks 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 convert spec-kit tasks into GitHub issues automatically?

To automate GitHub issue creation from spec-kit tasks, run the conversion command to parse the .specify directory and generate issues with dependencies and labels via the GitHub API.

What project structure is required to map spec-kit tasks to GitHub issues?

You need a spec-kit project structure containing a .specify directory. This structure ensures tasks and design artifacts are properly parsed before being mapped to structured GitHub issues.

Do I need GitHub API access to create issues from spec-kit tasks?

Yes, GitHub API access is required. The Skill utilizes the GitHub MCP server to authenticate and create structured issues, ensuring dependencies and labels are applied correctly.

How are task dependencies and labels handled during GitHub issue creation?

Task dependencies and labels are extracted from the spec-kit design artifacts and automatically applied to the generated GitHub issues, ensuring an actionable and structured project workflow.

What is the best way to structure spec-kit tasks for GitHub issue conversion?

The best way is to maintain a valid spec-kit project with a .specify directory and clear design artifacts. This ensures tasks are actionable and accurately converted into GitHub issues.

Why are my spec-kit tasks not converting into GitHub issues?

Conversion fails if the required .specify directory is missing from your spec-kit project, or if GitHub API access via the MCP server is not properly configured for issue creation.