speckit-taskstoissues

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

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill speckit-taskstoissues-inspedralbes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW/tree/main/prj-entrades-nou/.cursor/skills/speckit-taskstoissues
Command: npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill speckit-taskstoissues-inspedralbes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts scattered tasks and design artifacts into actionable, dependency-ordered GitHub issues to streamline feature delivery.

Core Features & Use Cases

  • Generate issue lists from design artifacts and existing tasks.
  • Maintain dependency order to ensure logical, incremental progress.
  • Use for feature planning, sprint scoping, and cross-team coordination.

Quick Start

Create a set of GitHub issues ordered by dependencies from existing tasks and any available design artifacts.

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 artifacts into GitHub issues ordered by dependencies?

To convert design artifacts into GitHub issues ordered by dependencies, use a spec-kit project structure. The skill processes available design artifacts and existing tasks to generate issues ordered by dependencies, ensuring logical, incremental progress for feature delivery.

What is the best way to generate GitHub issues from scattered tasks for sprint planning?

The best way to generate GitHub issues from scattered tasks for sprint planning is to use a spec-kit project structure. It reads available design artifacts and existing tasks to automatically produce a dependency-ordered issue list for feature development and cross-team coordination.

Do I need a specific project structure to generate dependency-ordered GitHub issues?

Yes, you need a valid spec-kit project structure with a valid SKILL.md file containing name and description. The skill optionally interacts with .specify extensions and outlines for pre and post processing to accurately generate the ordered GitHub issues.

Can I use existing design artifacts to scope cross-team feature development in GitHub?

Yes, you can use existing design artifacts to scope cross-team feature development. The skill maintains dependency order to ensure logical, incremental progress, making it suitable for feature planning, sprint scoping, and coordinating work across multiple teams.

Why does the GitHub issue generation rely on dependencies?

GitHub issue generation relies on dependencies to maintain logical, incremental progress during feature delivery. Ordering issues by dependencies ensures that prerequisite tasks are completed first, streamlining the overall development workflow and preventing blockers.