speckit-taskstoissues

Convert project tasks into dependency-ordered GitHub issues.

34|2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/DengNaichen/Stet --skill speckit-taskstoissues-dengnaichen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/DengNaichen/Stet --skill speckit-taskstoissues-dengnaichen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill bridges the gap between project planning and execution by automating the creation of GitHub issues from defined task lists, ensuring that project requirements are tracked and actionable.

Core Features & Use Cases

  • Automated Issue Creation: Transforms task lists into structured GitHub issues with dependency ordering.
  • Context-Aware Integration: Validates repository context and project structure before creating issues to prevent misconfiguration.
  • Use Case: When a feature specification is finalized, use this skill to instantly generate a set of GitHub issues for each task, ensuring the development team has a clear, tracked roadmap.

Quick Start

Use the speckit-taskstoissues skill to convert all pending tasks in the current repository into 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 convert project tasks into GitHub issues automatically?

To convert project tasks into GitHub issues, this skill parses repository-specific task files and automates the creation of structured, dependency-ordered issues for development tracking.

What is the best way to synchronize design artifacts with issue tracking systems?

Synchronizing design artifacts with issue tracking systems is achieved by parsing the spec-kit project directory structure to generate tracked GitHub issues from finalized feature specifications.

Do I need a specific project directory structure to create GitHub issues from task files?

Yes, creating GitHub issues from task files requires adherence to the spec-kit project directory structure and a valid GitHub remote URL to ensure proper context validation.

How does dependency ordering work when generating GitHub issues from a task list?

Dependency ordering when generating GitHub issues works by parsing the task list to establish execution sequences, ensuring the development team receives a clear, tracked roadmap.

Can I use this skill to generate GitHub issues for any repository context?

No, you cannot use this skill for any repository context; it validates repository context and project structure before creating issues to prevent misconfiguration.

When should I not use automated GitHub issue creation from task lists?

You should not use automated GitHub issue creation when your project lacks a valid GitHub remote URL or does not follow the required spec-kit project directory structure.