speckit-taskstoissues

Convert spec-kit tasks into dependency-ordered GitHub issues from design artifacts.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/smile95137a/kuji-admin-web --skill speckit-taskstoissues-smile95137a
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/smile95137a/kuji-admin-web/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/smile95137a/kuji-admin-web --skill speckit-taskstoissues-smile95137a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Dependency-ordered issue creation: generates issues in the correct sequence reflecting task dependencies.
  • Artifact-driven mapping: uses design artifacts to populate issue descriptions and links.
  • Use Case: when starting a new feature from a spec-kit project with a .specify/ directory, convert tasks into tracked issues for engineering work.

Quick Start

Feed the spec-kit project with design artifacts and run the speckit-taskstoissues workflow to generate dependency-ordered issues.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert tasks into GitHub issues from design artifacts?

You can convert tasks into GitHub issues by feeding a spec-kit project with design artifacts into the workflow, which uses templates to generate dependency-ordered issues automatically.

Can I create dependency-ordered GitHub issues for feature development?

Yes, dependency-ordered GitHub issues can be created by mapping task dependencies from your design artifacts, ensuring issues are generated in the correct sequence for engineering work.

Do I need a spec-kit project structure to generate ordered GitHub issues?

Yes, you need a spec-kit project with a .specify directory and related design artifacts. The workflow uses this structure and templates from taskstoissues.md to drive issue creation.

How does artifact-driven mapping work for GitHub issue creation?

Artifact-driven mapping extracts information from your design artifacts to populate issue descriptions and links, ensuring that generated GitHub issues contain the necessary context and dependencies.

What's the best way to track feature development tasks as GitHub issues?

The best way to track feature tasks is using a spec-kit project workflow that converts tasks into dependency-ordered GitHub issues, applying pre- and post-execution hooks via the runtime.

Why are my generated GitHub issues not reflecting task dependencies?

Generated GitHub issues reflect task dependencies only when the spec-kit project design artifacts are properly structured, allowing the workflow to map and order them correctly.