skills.rest
Pacheco95
Pacheco95COMMUNITY
Explore all skills by this author →
WebsiteGitHub

speckit-taskstoissues

Convert spec-kit tasks into dependency-ordered GitHub issues.

Updated Apr 29, 2026
Search Tags:#automation#templates#spec-kit#dependency-management#github-issues#design-artifacts#task-to-issues
One-click install
npx skills add https://github.com/Pacheco95/marketplace --skill speckit-taskstoissues-pacheco95
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/Pacheco95/marketplace/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/Pacheco95/marketplace --skill speckit-taskstoissues-pacheco95

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts existing tasks into actionable, dependency-ordered GitHub issues.

Core Features & Use Cases

  • Task-to-issue conversion based on design artifacts in the .specify directory.
  • Dependency-aware prioritization and sequencing for feature development.
  • Templates and metadata-driven content generation to ensure consistent issue quality across repositories.

Quick Start

Run speckit-taskstoissues to convert your spec-kit tasks into prioritized 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 spec-kit tasks into ordered GitHub issues?▼

To convert spec-kit tasks into ordered GitHub issues, run speckit-taskstoissues. It reads project metadata from the .specify directory, applies templates, and creates dependency-ordered issues in your target repository.

How does dependency-aware prioritization work for GitHub issues?▼

Dependency-aware prioritization sequences GitHub issues by reading design artifacts in the .specify directory. This ensures tasks are ordered correctly for feature development, preventing issues from being blocked by unmet dependencies.

Do I need a .specify directory to generate GitHub issues from tasks?▼

Yes, you need a .specify directory with existing design artifacts. The tool reads these artifacts and project metadata to shape the content and dependency ordering of the generated GitHub issues.

What is the best way to ensure consistent GitHub issue quality across repositories?▼

The best way to ensure consistent GitHub issue quality is using metadata-driven content generation. This Skill applies templates based on your design artifacts to standardize issue content across target repositories.

Can I use spec-kit task-to-issue conversion without existing design artifacts?▼

No, you cannot use this task-to-issue conversion without design artifacts. The conversion relies on existing artifacts within the .specify directory to shape the issue content and dependency ordering.

Why does task-to-issue conversion require reading project metadata?▼

Task-to-issue conversion requires reading project metadata to apply templates and generate content. This metadata ensures the created GitHub issues are properly dependency-ordered and contextually accurate for the target repository.

Related Skills

Explore More Software Engineering Skills→
PieroSierraPieroSierra
128

speckit-taskstoissues

Convert spec-kit tasks into GitHub issues with dependency ordering.

Community
Advanced
acarmonagacarmonag
2

github-project-management

Coordinate GitHub project boards and swarm task statuses bidirectionally.

Community
Advanced
AustinZ21AustinZ21
4

speckit-taskstoissues

Convert dependency-ordered spec-kit tasks into GitHub issues.

Community
Intermediate
Rubiss-ProjectsRubiss-Projects
25

speckit-taskstoissues

Convert spec-kit project tasks into dependency-ordered GitHub issues.

Official
Intermediate