speckit-taskstoissues

Convert design artifacts into dependency-ordered GitHub issues.

1|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/code-dot-org/marketing-sites --skill speckit-taskstoissues-code-dot-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/code-dot-org/marketing-sites/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/code-dot-org/marketing-sites --skill speckit-taskstoissues-code-dot-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts design tasks into a dependency-ordered backlog by transforming design artifacts into actionable GitHub issues for a feature.

Core Features & Use Cases

  • Dependency-aware mapping from design artifacts to GitHub issues, ensuring proper sequencing.
  • Automated issue creation in the repository identified by the Git remote, with correct labels and milestones.
  • Supports handling multiple tasks and generating a coherent dependency chain for development planning.

Quick Start

Convert your existing design artifacts into a queue of linked GitHub issues ready for triage.

Frequently Asked Questions about speckit-taskstoissues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn design artifacts into GitHub issues for feature development?

This Skill transforms design artifacts into a dependency-aware set of GitHub issues. It maps tasks to actionable issues, ensuring proper sequencing and automated creation in the correct repository to drive feature development.

How does dependency-aware issue creation work for design tasks?

Dependency-aware issue creation works by analyzing design artifacts to generate a coherent dependency chain for development planning. It ensures issues are created in the correct repository, ordered by dependencies, and validated against the remote URL to sequence feature work properly.

Do I need a .specify directory to convert design tasks into GitHub issues?

Yes, a .specify directory is required. This automation applies to Speckit or spec-kit style repositories that contain a .specify directory and have a Git remote URL configured for validating and creating the dependency-ordered issues.

Can I generate multiple GitHub issues from design artifacts at once?

Yes, you can generate multiple GitHub issues at once. The automation supports handling multiple tasks and generates a coherent dependency chain, creating the ordered issues in the repository identified by the Git remote with correct labels and milestones.

How are GitHub issues validated against the remote repository during generation?

GitHub issues are validated against the remote repository by checking the Git remote URL. This ensures that the dependency-aware issues are created in the correct repository, preventing misalignment between your local design artifacts and the remote project backlog.

What is the best way to automate issue creation from spec-kit repositories?

The best way to automate issue creation from spec-kit repositories is to use a dependency-aware mapping tool. It transforms design artifacts into prioritized GitHub issues, applying correct labels and milestones while ordering them by dependency chains for development planning.