speckit-taskstoissues

Convert .specify design artifacts into dependency-ordered GitHub issues.

Updated May 20, 2026
One-click install
npx skills add https://github.com/igmo71/Myrmex --skill speckit-taskstoissues-igmo71
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/igmo71/Myrmex/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/igmo71/Myrmex --skill speckit-taskstoissues-igmo71

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert scattered design tasks and artifacts into actionable, dependency-ordered GitHub issues to drive feature development efficiently.

Core Features & Use Cases

  • Dependency-aware issue creation: generates an ordered list of GitHub issues based on design artifacts and dependencies.
  • Design-driven scoping: uses available design documents to infer task relationships and priorities.
  • Use Case: for a new feature, converts tasks from .specify templates into issues with proper linking and sequencing.

Quick Start

Provide your design artifacts and run the speckit-taskstoissues workflow to automatically create linked, dependency-ordered 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 design tasks into ordered GitHub issues?

To convert design tasks into ordered GitHub issues, this workflow reads scattered design artifacts from spec-kit projects and automatically generates sequenced, dependency-linked issues in the matching remote repository.

What is dependency-aware issue creation in spec-kit projects?

Dependency-aware issue creation is a process that uses design artifacts within .specify directories to infer task relationships, ensuring GitHub issues are generated and linked in the correct sequential execution order.

Can I use pre-execution and post-execution hooks to tailor GitHub issue creation?

Yes, you can use optional and automatic pre-execution and post-execution hooks to tailor GitHub issue creation, allowing you to customize the workflow when converting .specify design artifacts into issues.

Does the workflow create GitHub issues only in the matching remote repository?

Yes, the workflow leverages the project structure to ensure issues are created only in the matching remote repository, enforcing dependency order and respecting extensions within the spec-kit environment.

How do I start generating linked GitHub issues from .specify templates?

To start generating linked GitHub issues, provide your design artifacts in the .specify directory and run the workflow to automatically create dependency-ordered issues based on the available design documents.