speckit-taskstoissues

Convert design artifacts and tasks into dependency-ordered GitHub issues.

57|13|Updated Jul 12, 2025
One-click install
npx skills add https://github.com/heidsoft/itsm --skill speckit-taskstoissues-heidsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/heidsoft/itsm/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/heidsoft/itsm --skill speckit-taskstoissues-heidsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert design artifacts and task lists into actionable, dependency-ordered GitHub issues to streamline feature development.

Core Features & Use Cases

  • Generate GitHub issues from design artifacts and incoming tasks, preserving dependency order.
  • Maintain traceability from specs to actionable work items, with optional labels and filters.

Quick Start

Provide the Speckit project tasks and design artifacts, then run the task-to-issues workflow to generate ordered 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 generate GitHub issues from design tasks?

To generate GitHub issues from design tasks, provide your spec-kit project tasks and design artifacts to run the task-to-issues workflow. This process transforms design specs into dependency-ordered GitHub issues for streamlined feature development.

Does this task-to-issues workflow preserve task dependencies?

Yes, the task-to-issues workflow preserves task dependencies. It transforms design artifacts and tasks into prioritized GitHub issues while maintaining the required dependency order for feature development.

Do I need a specific project structure to convert design specs into GitHub issues?

Yes, converting design specs into GitHub issues requires the spec-kit project structure with a .specify/ directory. This structure allows the workflow to read tasks and apply optional filters, labels, and extension hooks.

Can I add labels and filters when generating GitHub issues from design artifacts?

Yes, you can add labels and filters when generating GitHub issues from design artifacts. The workflow supports optional filters and labels to maintain traceability from specs to actionable work items.

What is the best way to maintain traceability from design specs to GitHub issues?

The best way to maintain traceability from design specs to GitHub issues is using a task-to-issues workflow. It converts design artifacts into dependency-ordered GitHub issues, optionally applying filters and labels for actionable work items.