speckit-taskstoissues

Convert design tasks into dependency-ordered GitHub issues.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ins-enco/ctm__affiliate_backend --skill speckit-taskstoissues-ins-enco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/ins-enco/ctm__affiliate_backend/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/ins-enco/ctm__affiliate_backend --skill speckit-taskstoissues-ins-enco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts scattered design tasks into organized, dependency-ordered GitHub issues so engineering teams can plan, track, and deliver features without missing steps.

Core Features & Use Cases

  • Automatic mapping of tasks to GitHub issues with dependency ordering
  • Enforces safe repository targeting by validating remote URLs before issue creation
  • Supports prereq checks and a guided, repeatable workflow for large feature work
  • Use Case: When a set of design artifacts describes a feature, run this skill to automatically create issues that reflect the required work and dependencies

Quick Start

Provide your tasks and optional filters, and the system will create dependency-ordered GitHub issues in the matched 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 design tasks into GitHub issues with dependency ordering?

To convert design tasks into GitHub issues with dependency ordering, provide your task set and filters. The system validates your Git remote URL and uses a guided GitHub MCP-based flow to create organized, traceable issues in the correct repository.

What is the best way to map design artifacts to executable GitHub issues for feature development?

Mapping design artifacts to executable GitHub issues is best handled by an automated translation into concrete work items. This approach organizes the resulting issues by their dependencies to ensure reliable feature development without missing steps.

Do I need a valid Git remote URL to automatically create GitHub issues from tasks?

Yes, you need a valid Git remote URL to create GitHub issues from tasks. The workflow enforces safe repository targeting by validating the remote URL and running prerequisite checks before initiating the issue creation flow.

How does dependency mapping work when generating GitHub issues from a task list?

Dependency mapping works by analyzing your provided design tasks and automatically ordering the generated GitHub issues based on their relationships. This ensures that engineering teams can plan and track features sequentially without missing required prerequisite steps.

Can I apply filters when mapping tasks to GitHub issues?

Yes, you can apply optional filters when mapping tasks to GitHub issues. By providing your tasks and specific filters, the system generates the dependency-ordered GitHub issues in the matched repository according to your specified constraints.

Why does automated issue creation require prerequirements checks before opening GitHub issues?

Automated issue creation requires prerequisite checks to ensure a guided, repeatable workflow for large feature work. This validation guarantees that issues are safely targeted and created in the correct repository before the GitHub MCP flow executes.