speckit-taskstoissues

Convert design tasks into dependency-ordered GitHub issues for spec-kit projects.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/anishakode/Boring_AI --skill speckit-taskstoissues-anishakode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/anishakode/Boring_AI/tree/main/.cursor/skills/speckit-taskstoissues
Command: npx skills add https://github.com/anishakode/Boring_AI --skill speckit-taskstoissues-anishakode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Core Features & Use Cases

  • Transform design tasks into a structured set of issues that respect task dependencies.
  • Preserve traceability by mapping issues to design artifacts and acceptance criteria.
  • Enable predictable delivery by ordering issues according to dependencies and feature plan.

Quick Start

Create issues from your spec-kit tasks by running the speckit-taskstoissues workflow against a repository that contains a .specify/ directory.

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?

You can convert spec-kit tasks into GitHub issues by running the conversion workflow against a repository containing a .specify/ directory, which transforms design artifacts into structured, dependency-ordered issues for feature work.

Does the task-to-issues conversion respect dependency order?

Yes, task-to-issues conversion respects dependency order by prioritizing and structuring the generated GitHub issues according to the task dependencies and feature plan.

Can I map generated GitHub issues back to my design artifacts?

Yes, converting tasks into GitHub issues preserves traceability by mapping the generated issues directly to your existing design artifacts and acceptance criteria.

What is needed to generate dependency-ordered issues from design tasks?

To generate dependency-ordered issues from design tasks, you need a spec-kit project repository containing a .specify/ directory along with your existing design artifacts and task definitions.

Can I run custom hooks before or after converting tasks to GitHub issues?

Yes, the task-to-issues conversion validates and executes extension hooks for both pre-task and post-task-to-issues steps, allowing you to run custom automation during the workflow.

Does creating GitHub issues from spec-kit tasks affect my repository remotes?

No, converting spec-kit tasks into GitHub issues respects your repository remotes configuration and outputs properly structured issue data without altering your remote settings.